diff --git a/fortify.md b/fortify.md
index d6e271a0c72..3d5c9eaf347 100644
--- a/fortify.md
+++ b/fortify.md
@@ -261,7 +261,7 @@ class User extends Authenticatable
 {
     use Notifiable, TwoFactorAuthenticatable;
 }
- ```
+```
 
 Next, you should build a screen within your application where users can manage their two factor authentication settings. This screen should allow the user to enable and disable two factor authentication, as well as regenerate their two factor authentication recovery codes.
 
diff --git a/migrations.md b/migrations.md
index f77fbd56360..f688c5532ad 100644
--- a/migrations.md
+++ b/migrations.md
@@ -190,9 +190,9 @@ php artisan migrate:rollback --step=5
 
 You may roll back a specific "batch" of migrations by providing the `batch` option to the `rollback` command, where the `batch` option corresponds to a batch value within your application's `migrations` database table. For example, the following command will roll back all migrations in batch three:
 
- ```shell
+```shell
 php artisan migrate:rollback --batch=3
- ```
+```
 
 If you would like to see the SQL statements that will be executed by the migrations without actually running them, you may provide the `--pretend` flag to the `migrate:rollback` command: