diff --git a/artisan.md b/artisan.md
index f2b05136a08..086317268e3 100644
--- a/artisan.md
+++ b/artisan.md
@@ -44,7 +44,9 @@ The `handle` method will be called when your command is executed. You may place
 
 Note that we are able to inject any dependencies we need into the command's constructor. The Laravel [service container](/docs/{{version}}/container) will automatically inject all dependencies type-hinted in the constructor. For greater code reusability, it is good practice to keep your console commands light and let them defer to application services to accomplish their tasks.
 
-    <?php namespace App\Console\Commands;
+    <?php
+
+    namespace App\Console\Commands;
 
     use App\User;
     use App\DripEmailer;
diff --git a/authentication.md b/authentication.md
index 4b4ee74a70c..a0b06a29f03 100644
--- a/authentication.md
+++ b/authentication.md
@@ -141,7 +141,9 @@ You may access the authenticated user via the `Auth` facade:
 
 Alternatively, once a user is authenticated, you may access the authenticated user via an `Illuminate\Http\Request` instance:
 
-    <?php namespace App\Http\Controllers;
+    <?php
+
+    namespace App\Http\Controllers;
 
     use Illuminate\Http\Request;
     use Illuminate\Routing\Controller;
@@ -204,7 +206,9 @@ Of course, you are not required to use the authentication controllers included w
 
 We will access Laravel's authentication services via the `Auth` [facade](/docs/{{version}}/facades), so we'll need to make sure to import the `Auth` facade at the top of the class. Next, let's check out the `attempt` method:
 
-    <?php namespace App\Http\Controllers;
+    <?php
+
+    namespace App\Http\Controllers;
 
     use Auth;
     use Illuminate\Routing\Controller;
@@ -470,7 +474,9 @@ You will also need to add credentials for the OAuth services your application ut
 
 Next, you are ready to authenticate users! You will need two routes: one for redirecting the user to the OAuth provider, and another for receiving the callback from the provider after authentication. We will access Socialite using the `Socialite` [facade](/docs/{{version}}/facades):
 
-    <?php namespace App\Http\Controllers;
+    <?php
+
+    namespace App\Http\Controllers;
 
     use Illuminate\Routing\Controller;
 
@@ -529,7 +535,9 @@ Once you have a user instance, you can grab a few more details about the user:
 
 If you are not using a traditional relational database to store your users, you will need to extend Laravel with your own authentication driver. We will use the `extend` method on the `Auth` facade to define a custom driver. You should place this call to `extend` within a [service provider](/docs/{{version}}/providers):
 
-    <?php namespace App\Providers;
+    <?php
+
+    namespace App\Providers;
 
     use Auth;
     use App\Extensions\RiakUserProvider;
diff --git a/billing.md b/billing.md
index 9a6763c2865..763970fecac 100644
--- a/billing.md
+++ b/billing.md
@@ -251,7 +251,9 @@ Since Stripe webhooks need to bypass Laravel's [CSRF verification](/docs/{{versi
 
 If you have additional Stripe webhook events you would like to handle, simply extend the Webhook controller. Your method names should correspond to Cashier's expected convention, specifically, methods should be prefixed with `handle` and the "camel case" name of the Stripe webhook you wish to handle. For example, if you wish to handle the `invoice.payment_succeeded` webhook, you should add a `handleInvoicePaymentSucceeded` method to the controller.
 
-	<?php namespace App\Http\Controller;
+	<?php
+
+	namespace App\Http\Controller;
 
 	use Laravel\Cashier\WebhookController as BaseController;
 
diff --git a/blade.md b/blade.md
index 9c89f5c2075..9b872b177f1 100644
--- a/blade.md
+++ b/blade.md
@@ -206,7 +206,9 @@ Blade even allows you to define your own custom directives. You can use the `dir
 
 The following example creates a `@datetime($var)` directive which formats a given `$var`:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Blade;
 	use Illuminate\Support\ServiceProvider;
diff --git a/cache.md b/cache.md
index ece4122bd3f..43e29477c99 100644
--- a/cache.md
+++ b/cache.md
@@ -69,7 +69,9 @@ However, you may also use the `Cache` facade, which is what we will use througho
 
 For example, let's import the `Cache` facade into a controller:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Cache;
 	use Illuminate\Routing\Controller;
@@ -190,7 +192,9 @@ To extend the Laravel cache with a custom driver, we will use the `extend` metho
 
 For example, to register a new cache driver named "mongo":
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Cache;
 	use App\Extensions\MongoStore;
@@ -227,7 +231,9 @@ The call to `Cache::extend` could be done in the `boot` method of the default `A
 
 To create our custom cache driver, we first need to implement the `Illuminate\Contracts\Cache\Store` [contract](/docs/{{version}}/contracts) contract. So, our MongoDB cache implementation would look something like this:
 
-	<?php namespace App\Extensions;
+	<?php
+
+	namespace App\Extensions;
 
 	class MongoStore implements \Illuminate\Contracts\Cache\Store
 	{
diff --git a/container.md b/container.md
index 00c11b25d5d..f55ad38d608 100644
--- a/container.md
+++ b/container.md
@@ -15,7 +15,9 @@ The Laravel service container is a powerful tool for managing class dependencies
 
 Let's look at a simple example:
 
-	<?php namespace App\Jobs;
+	<?php
+
+	namespace App\Jobs;
 
 	use App\User;
 	use Illuminate\Contracts\Mail\Mailer;
@@ -158,7 +160,9 @@ Lastly, but most importantly, you may simply "type-hint" the dependency in the c
 
 The container will automatically inject dependencies for the classes it resolves. For example, you may type-hint a repository defined by your application in a controller's constructor. The repository will automatically be resolved and injected into the class:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Routing\Controller;
 	use App\Users\Repository as UserRepository;
diff --git a/contracts.md b/contracts.md
index 8c627116d61..e0c68ac8aa9 100644
--- a/contracts.md
+++ b/contracts.md
@@ -27,7 +27,9 @@ You may have several questions regarding contracts. Why use interfaces at all? I
 
 First, let's review some code that is tightly coupled to a cache implementation. Consider the following:
 
-	<?php namespace App\Orders;
+	<?php
+
+	namespace App\Orders;
 
 	class Repository
 	{
@@ -67,7 +69,9 @@ Likewise, if we want to replace our underlying cache technology (Memcached) with
 
 **Instead of this approach, we can improve our code by depending on a simple, vendor agnostic interface:**
 
-	<?php namespace App\Orders;
+	<?php
+
+	namespace App\Orders;
 
 	use Illuminate\Contracts\Cache\Repository as Cache;
 
@@ -143,7 +147,9 @@ Many types of classes in Laravel are resolved through the [service container](/d
 
 For example, take a look at this event listener:
 
-	<?php namespace App\Listeners;
+	<?php
+
+	namespace App\Listeners;
 
 	use App\User;
 	use App\Events\NewUserRegistered;
diff --git a/controllers.md b/controllers.md
index 53d9f8ba54a..b6ae692fa50 100644
--- a/controllers.md
+++ b/controllers.md
@@ -22,7 +22,9 @@ Instead of defining all of your request handling logic in a single `routes.php`
 
 Here is an example of a basic controller class. All Laravel controllers should extend the base controller class included with the default Laravel installation:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\Http\Controllers\Controller;
 
@@ -152,7 +154,9 @@ Sometimes you may need to define routes to a "nested" resource. For example, a p
 
 This route will register a "nested" resource that may be accessed with URLs like the following: `photos/{photos}/comments/{comments}`.
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\Http\Controllers\Controller;
 
@@ -190,7 +194,9 @@ Laravel allows you to easily define a single route to handle every action in a c
 
  Next, just add methods to your controller. The method names should begin with the HTTP verb they respond to followed by the title case version of the URI:
 
- 	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	class UserController extends Controller
 	{
@@ -244,7 +250,9 @@ If you would like to [name](/docs/{{version}}/routing#named-routes) some of the
 
 The Laravel [service container](/docs/{{version}}/container) is used to resolve all Laravel controllers. As a result, you are able to type-hint any dependencies your controller may need in its constructor. The dependencies will automatically be resolved and injected into the controller instance:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Routing\Controller;
 	use App\Repositories\UserRepository;
@@ -274,7 +282,9 @@ Of course, you may also type-hint any [Laravel contract](/docs/{{version}}/contr
 
 In addition to constructor injection, you may also type-hint dependencies on your controller's action methods. For example, let's type-hint the `Illuminate\Http\Request` instance on one of our methods:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use Illuminate\Routing\Controller;
@@ -297,7 +307,9 @@ In addition to constructor injection, you may also type-hint dependencies on you
 
 If your controller method is also expecting input from a route parameter, simply list your route arguments after your other dependencies:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use Illuminate\Routing\Controller;
diff --git a/database.md b/database.md
index 1f0e9671796..131c5a80821 100644
--- a/database.md
+++ b/database.md
@@ -59,7 +59,9 @@ Once you have configured your database connection, you may run queries using the
 
 To run a basic query, we can use the `select` method on the `DB` facade:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use DB;
 	use App\Http\Controllers\Controller;
@@ -122,7 +124,9 @@ Some database statements should not return any value. For these types of operati
 
 If you would like to receive each SQL query executed by your application, you may use the `listen` method. This method is useful for logging queries or debugging. You may register your query listener in a [service provider](/docs/{{version}}/providers):
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use DB;
 	use Illuminate\Support\ServiceProvider;
diff --git a/eloquent-collections.md b/eloquent-collections.md
index c55f424fab9..aab1f5f776c 100644
--- a/eloquent-collections.md
+++ b/eloquent-collections.md
@@ -106,7 +106,9 @@ All Eloquent collections extend the base [Laravel collection](/docs/{{version}}/
 
 If you need to use a custom `Collection` object with your own extension methods, you may override the `newCollection` method on your model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use App\CustomCollection;
 	use Illuminate\Database\Eloquent\Model;
diff --git a/eloquent-mutators.md b/eloquent-mutators.md
index 6a21d207318..4e312805a98 100644
--- a/eloquent-mutators.md
+++ b/eloquent-mutators.md
@@ -19,7 +19,9 @@ In addition to custom accessors and mutators, Eloquent can also automatically ca
 
 To define an accessor, create a `getFooAttribute` method on your model where `Foo` is the "camel" cased name of the column you wish to access. In this example, we'll defined an accessor for the `first_name` attribute. The accessor will automatically be called by Eloquent when attempting to retrieve the value of `first_name`:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -47,7 +49,9 @@ As you can see, the original value of the column is passed to the accessor, allo
 
 To define a mutator, define a `setFooAttribute` method on your model where `Foo` is the "camel" cased name of the column you wish to access. So, again, let's define a mutator for the `first_name` attribute. This mutator will be automatically called when we attempt to set the value of the `first_name` attribute on the model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -80,7 +84,9 @@ By default, Eloquent will convert the `created_at` and `updated_at` columns to i
 
 You may customize which fields are automatically mutated, and even completely disable this mutation, by overriding the `$dates` property of your model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -115,7 +121,9 @@ The `$casts` property on your model provides a convenient method of converting a
 
 For example, let's cast the `is_admin` attribute, which is stored in our database as an integer (`0` or `1`) to a boolean value:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -143,7 +151,9 @@ Now the `is_admin` attribute will always be cast to a boolean when you access it
 
 The `array` cast type is particularly useful when working with columns that are stored as serialized JSON. For example, if your database has a `TEXT` field type that contains serialized JSON, adding the `array` cast to that attribute will automatically deserialize the attribute to a PHP array when you access it on your Eloquent model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
diff --git a/eloquent-relationships.md b/eloquent-relationships.md
index 540deb2be63..19a3da6c13d 100644
--- a/eloquent-relationships.md
+++ b/eloquent-relationships.md
@@ -41,7 +41,9 @@ But, before diving too deep into using relationships, let's learn how to define
 
 A one-to-one relationship is a very basic relation. For example, a `User` model might be associated with one `Phone`. To define this relationship, we place a `phone` method on the `User` model. The `phone` method should return the results of the `hasOne` method on the base Eloquent model class:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -72,7 +74,9 @@ Additionally, Eloquent assumes that the foreign key should have a value matching
 
 So, we can access the `Phone` model from our `User`. Now, let's define a relationship on the `Phone` model that will let us access the `User` the owns the phone. We can define the inverse of a `hasOne` relationship using the `belongsTo` method:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -112,7 +116,9 @@ If your parent model does not use `id` as its primary key, or you wish to join t
 
 A "one-to-many" relationship is used to define relationships where a single model owns any amount of other models. For example, a blog post may have an infinite number of comments. Like all other Eloquent relationships, one-to-many relationships are defined by placing a function on your Eloquent model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -151,7 +157,9 @@ Like the `hasOne` method, you may also override the foreign and local keys by pa
 
 Now that we can access all of a post's comments, let's define a relationship to allow a comment to access its parent post. To define the inverse of a `hasMany` relationship, define a relationship function on the child model which calls the `belongsTo` method:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -199,7 +207,9 @@ Many-to-many relations are slightly more complicated than `hasOne` and `hasMany`
 
 Many-to-many relationships are defined by writing a method that calls the `belongsToMany` method on the base Eloquent class. For example, let's define the `roles` method on our `User` model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -238,7 +248,9 @@ In addition to customizing the name of the joining table, you may also customize
 
 To define the inverse of a many-to-many relationship, you simply place another call to `belongsToMany` on your related model. To continue our user roles example, let's define the `users` method on the `Role` model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -298,7 +310,9 @@ Though `posts` does not contain a `country_id` column, the `hasManyThrough` rela
 
 Now that we have examined the table structure for the relationship, let's define it on the `Country` model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -353,7 +367,9 @@ Two important columns to note are the `imageable_id` and `imageable_type` column
 
 Next, let's examine the model definitions needed to build this relationship:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -436,7 +452,9 @@ In addition to traditional polymorphic relations, you may also define "many-to-m
 
 Next, we're ready to define the relationships on the model. The `Post` and `Video` models will both have a `tags` method that calls the `morphToMany` method on the base Eloquent class:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -455,7 +473,9 @@ Next, we're ready to define the relationships on the model. The `Post` and `Vide
 
 Next, on the `Tag` model, you should define a method for each of its related models. So, for this example, we will define a `posts` method and a `videos` method:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -503,7 +523,9 @@ Since all types of Eloquent relationships are defined via functions, you may cal
 
 For example, imagine a blog system in which a `User` model has many associated `Post` models:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -567,7 +589,9 @@ If you need even more power, you may use the `whereHas` and `orWhereHas` methods
 
 When accessing Eloquent relationships as properties, the relationship data is "lazy loaded". This means the relationship data is not actually loaded until you first access the property. However, Eloquent can "eager load" relationships at the time you query the parent model. Eager loading alleviates the N + 1 query problem. To illustrate the N + 1 query problem, consider a `Book` model that is related to `Author`:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
diff --git a/eloquent-serialization.md b/eloquent-serialization.md
index 07d5631329c..153c5502315 100644
--- a/eloquent-serialization.md
+++ b/eloquent-serialization.md
@@ -52,7 +52,9 @@ Since models and collections are converted to JSON when cast to a string, you ca
 
 Sometimes you may wish to limit the attributes, such as passwords, that are included in your model's array or JSON representation. To do so, add a `$hidden` property definition to your model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -70,7 +72,9 @@ Sometimes you may wish to limit the attributes, such as passwords, that are incl
 
 Alternatively, you may use the `visible` property to define a white-list of attributes that should be included in your model's array and JSON representation:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -89,7 +93,9 @@ Alternatively, you may use the `visible` property to define a white-list of attr
 
 Occasionally, you may need to add array attributes that do not have a corresponding column in your database. To do so, first define an [accessor](/docs/{{version}}/eloquent-mutators) for the value:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -108,7 +114,9 @@ Occasionally, you may need to add array attributes that do not have a correspond
 
 Once you have created the accessor, add the attribute name to the `appends` property on the model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
diff --git a/eloquent.md b/eloquent.md
index 92fe38c3fee..85d37d37139 100644
--- a/eloquent.md
+++ b/eloquent.md
@@ -43,7 +43,9 @@ If you would like to generate a [database migration](/docs/{{version}}/schema#da
 
 Now, let's look at an example `Flight` model class, which will use to retrieve and store information from our `flights` database table:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -57,7 +59,9 @@ Now, let's look at an example `Flight` model class, which will use to retrieve a
 
 Note that we did not tell Eloquent which table to use for our `Flight` model. The "snake case", plural name of the class will be used as the table name unless another name is explicitly specified. So, in this case, Eloquent will assume the `Flight` model stores records in the `flights` table. You may specify a custom table by defining a `table` property on your model:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -79,7 +83,9 @@ Eloquent will also assume that each table has a primary key column named `id`. Y
 
 By default, Eloquent expects `created_at` and `updated_at` columns to exist on your tables.  If you do not wish to have these columns automatically managed by Eloquent, set the `$timestamps` property on your model to `false`:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -95,7 +101,9 @@ By default, Eloquent expects `created_at` and `updated_at` columns to exist on y
 
 If you need to customize the format of your timestamps, set the `$dateFormat` property on your model. This property determines how date attributes are stored in the database, as well as their format when the model is serialized to an array or JSON:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -114,7 +122,9 @@ If you need to customize the format of your timestamps, set the `$dateFormat` pr
 
 Once you have created a model and [its associated database table](/docs/{{version}}/schema), you are ready to start retrieving data from your database. Think of each Eloquent model as a powerful [query builder](/docs/{{version}}/queries) allowing you to fluently query the database table associated with the model. For example:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\Flight;
 	use App\Http\Controllers\Controller;
@@ -215,7 +225,9 @@ Of course, you may also use the query builder aggregate functions such as `count
 
 To create a new record in the database, simply create a new model instance, set attributes on the model, then call the `save` method:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\Flight;
 	use Illuminate\Http\Request;
@@ -271,7 +283,9 @@ A mass-assignment vulnerability occurs when user's pass unexpected HTTP paramete
 
 So, to get started, you should define which model attributes you want to make mass assignable. You may do this using the `$fillable` property on the model. For example, let's make the `name` attribute of our `Flight` model mass assignable:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -291,7 +305,9 @@ Once we have made the attributes mass assignable, we can use the `create` method
 
 While `$fillable` serves as a "white list" of attributes that should be mass assignable, you may also choose to use `$guarded`. The `$guarded` property should contain an array of attributes that you do not want to be mass assignable. All other attributes not in the array will be mass assignable. So, `$guarded` functions like a "black list". Of course, you should use either `$fillable` or `$guarded` - not both:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -349,7 +365,9 @@ Of course, you may also run a delete query on a set of models. In this example,
 
 In addition to actually removing records from your database, Eloquent can also "soft delete" models. When models are soft deleted, they are not actually removed from your database. Instead, a `deleted_at` attribute is set on the model and inserted into the database. If a model has a non-null `deleted_at` value, the model has been soft deleted. To enable soft deletes for a model, use the `Illuminate\Database\Eloquent\SoftDeletes` trait on the model and add the `deleted_at` column to your `$dates` property:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 	use Illuminate\Database\Eloquent\SoftDeletes;
@@ -434,7 +452,9 @@ Sometimes you may need to truly remove a model from your database. To permanentl
 
 Scopes allow you to define common sets of constraints that you may easily re-use throughout your application. For example, you may need to frequently retrieve all users that are considered "popular". To define a scope, simply prefix an Eloquent model method with `scope`:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -471,7 +491,9 @@ Once the scope has been defined, you may call the scope methods when querying th
 
 Sometimes you may wish to define a scope that accepts parameters. To get started, just add your additional parameters to your scope. Scope parameters should be defined after the `$query` argument:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Database\Eloquent\Model;
 
@@ -504,7 +526,9 @@ Whenever a new model is saved for the first time, the `creating` and `created` e
 
 For example, let's define an Eloquent event listener in a [service provider](/docs/{{version}}/providers). Within our event listener, we will call the `isValid` method on the given model, and return `false` if the model is not valid. Returning `false` from an Eloquent event listener will cancel the `save` / `update` operation:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use App\User;
 	use Illuminate\Support\ServiceProvider;
diff --git a/encryption.md b/encryption.md
index 612738ed797..892db792f7c 100644
--- a/encryption.md
+++ b/encryption.md
@@ -17,7 +17,9 @@ You may encrypt a value using the `Crypt` [facade](/docs/{{version}}/facades). A
 
 For example, we may use the `encrypt` method to encrypt a secret and store it on an [Eloquent model](/docs/{{version}}/eloquent):
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Crypt;
 	use Illuminate\Http\Request;
diff --git a/errors.md b/errors.md
index 44680d07bc4..729cd336bad 100644
--- a/errors.md
+++ b/errors.md
@@ -118,7 +118,9 @@ The views within this directory should be named to match the HTTP status code th
 
 The Laravel logging facilities provide a simple layer on top of the powerful [Monolog](http://github.com/seldaek/monolog) library. By default, Laravel is configured to create daily log files for your application which are stored in the `storage/logs` directory. You may write information to the logs using the `Log` [facade](/docs/{{version}}/facades):
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Log;
 	use App\Http\Controllers\Controller;
diff --git a/events.md b/events.md
index c328484a2b9..c4cdf34cfd4 100644
--- a/events.md
+++ b/events.md
@@ -45,7 +45,9 @@ Of course, manually creating the files for each event and listener is cumbersome
 
 An event class is simply a data container which holds the information related to the event. For example, let's assume our generated `PodcastWasPurchased` event receives a [Eloquent ORM](/docs/{{version}}/eloquent) object:
 
-	<?php namespace App\Events;
+	<?php
+
+	namespace App\Events;
 
 	use App\Podcast;
 	use App\Events\Event;
@@ -76,7 +78,9 @@ As you can see, this event class contains no special logic. It is simply a conta
 
 Next, let's take a look at the listener for our example event. Event listeners receive the event instance in their `handle` method. The `event:generate` command will automatically import the proper event class and type-hint the event on the `handle` method. Within the `handle` method, you may perform any logic necessary to respond to the event.
 
-	<?php namespace App\Listeners;
+	<?php
+
+	namespace App\Listeners;
 
 	use App\Events\PodcastWasPurchased;
 	use Illuminate\Queue\InteractsWithQueue;
@@ -124,7 +128,9 @@ Sometimes, you may wish to stop the propagation of an event to other listeners.
 
 Need to [queue](/docs/{{version}}/queues) an event listener? It couldn't be any easier. Simply add the `ShouldQueue` interface to the listener class. Listeners generated by the `event:generate` Artisan command already have this interface imported into the current namespace, so you can use it immediately:
 
-	<?php namespace App\Listeners;
+	<?php
+
+	namespace App\Listeners;
 
 	use App\Events\PodcastWasPurchased;
 	use Illuminate\Queue\InteractsWithQueue;
@@ -141,7 +147,9 @@ That's it! Now, when this listener is called for an event, it will be queued aut
 
 If you need to access the underlying queue job's `delete` and `release` methods manually, you may do so. The `Illuminate\Queue\InteractsWithQueue` trait, which is imported by default on generated listeners, gives you access to these methods:
 
-	<?php namespace App\Listeners;
+	<?php
+
+	namespace App\Listeners;
 
 	use App\Events\PodcastWasPurchased;
 	use Illuminate\Queue\InteractsWithQueue;
@@ -164,7 +172,9 @@ If you need to access the underlying queue job's `delete` and `release` methods
 
 To fire an event, you may use the `Event` [facade](/docs/{{version}}/facades), passing an instance of the event to the `fire` method. The `fire` method will dispatch the event to all of its registered listeners:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Event;
 	use App\Podcast;
@@ -222,7 +232,9 @@ Before broadcasting events, you will also need to configure and run a [queue lis
 
 To inform Laravel that a given event should be broadcast, implement the `Illuminate\Contracts\Broadcasting\ShouldBroadcast` interface on the event class. The `ShouldBroadcast` interface requires you to implement a single method: `broadcastOn`. The `broadcastOn` method should return an array of "channel" names that the event should be broadcast on:
 
-	<?php namespace App\Events;
+	<?php
+
+	namespace App\Events;
 
 	use App\User;
 	use App\Events\Event;
@@ -337,7 +349,9 @@ Using the `socket.io` and `ioredis` Node libraries, you can quickly write an eve
 
 Event subscribers are classes that may subscribe to multiple events from within the class itself, allowing you to define several event handlers within a single class. Subscribers should define a `subscribe` method, which will be passed an event dispatcher instance:
 
-	<?php namespace App\Listeners;
+	<?php
+
+	namespace App\Listeners;
 
 	class UserEventListener {
 
@@ -376,7 +390,9 @@ Event subscribers are classes that may subscribe to multiple events from within
 
 Once the subscriber has been defined, it may be registered with the event dispatcher. You may register subscribers using the `$subscribe` property on the `EventServiceProvider`. For example, let's add the `UserEventListener`.
 
-    <?php namespace App\Providers;
+    <?php
+
+    namespace App\Providers;
 
     use Illuminate\Contracts\Events\Dispatcher as DispatcherContract;
     use Illuminate\Foundation\Support\Providers\EventServiceProvider as ServiceProvider;
diff --git a/facades.md b/facades.md
index 956518c0954..4282712870e 100644
--- a/facades.md
+++ b/facades.md
@@ -18,7 +18,9 @@ A facade class only needs to implement a single method: `getFacadeAccessor`. It'
 
 In the example below, a call is made to the Laravel cache system. By glancing at this code, one might assume that the static method `get` is being called on the `Cache` class:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Cache;
 	use App\Http\Controllers\Controller;
diff --git a/filesystem.md b/filesystem.md
index 7e45804409f..db6a514da4d 100644
--- a/filesystem.md
+++ b/filesystem.md
@@ -43,7 +43,9 @@ Before using the S3 or Rackspace drivers, you will need to install the appropria
 
 The `Storage` facade may be used to interact with any of your configured disks. For example, you may use the `put` method on the facade to store an avatar on the default disk. If you call methods on the `Storage` facade without first calling the `disk` method, the method call will automatically be passed to the default disk:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Storage;
 	use Illuminate\Http\Request;
@@ -169,7 +171,9 @@ Laravel's Flysystem integration provides drivers for several "drivers" out of th
 
 In order to set up the custom filesystem you will need to create a [service provider](/docs/{{version}}/providers) such as `DropboxServiceProvider`. In the provider's `boot` method, you may use the `Storage` facade's `extend` method to define the custom driver:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Storage;
 	use League\Flysystem\Filesystem;
diff --git a/hashing.md b/hashing.md
index a903809c9f8..23646b64859 100644
--- a/hashing.md
+++ b/hashing.md
@@ -15,7 +15,9 @@ Bcrypt is a great choice for hashing passwords because its "work factor" is adju
 
 You may hash a password by calling the `make` method on the `Hash` facade:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Hash;
 	use Illuminate\Http\Request;
diff --git a/mail.md b/mail.md
index e2d10c9b59a..d888cd827e3 100644
--- a/mail.md
+++ b/mail.md
@@ -56,7 +56,9 @@ Laravel allows you to store your e-mail messages in [views](/docs/{{version}}/vi
 
 To send a message, use the `send` method on the `Mail` [facade](/docs/{{version}}/facades). The `send` method accepts three arguments. First, the name of a [view](/docs/{{version}}/views) that contains the e-mail message. Secondly, an array of data you wish to pass to the view. Lastly, a `Closure` callback which receives a message instance, allowing you to customize the recipients, subject, and other aspects of the mail message:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Mail;
 	use App\User;
diff --git a/middleware.md b/middleware.md
index 6851e7dcc17..97add910ff8 100644
--- a/middleware.md
+++ b/middleware.md
@@ -24,7 +24,9 @@ To create a new middleware, use the `make:middleware` Artisan command:
 
 This command will place a new `OldMiddleware` class within your `app/Http/Middleware` directory. In this middleware, we will only allow access to the route if the supplied `age` is greater than 200. Otherwise, we will redirect the users back to the "home" URI.
 
-	<?php namespace App\Http\Middleware;
+	<?php
+
+	namespace App\Http\Middleware;
 
 	use Closure;
 
@@ -56,7 +58,9 @@ It's best to envision middleware as a series of "layers" HTTP requests must pass
 
 Whether a middleware runs before or after a request depends on the middleware itself. For example, the following middleware would perform some task **before** the request is handled by the application:
 
-	<?php namespace App\Http\Middleware;
+	<?php
+
+	namespace App\Http\Middleware;
 
 	use Closure;
 
@@ -72,7 +76,9 @@ Whether a middleware runs before or after a request depends on the middleware it
 
 However, this middleware would perform its task **after** the request is handled by the application:
 
-	<?php namespace App\Http\Middleware;
+	<?php
+
+	namespace App\Http\Middleware;
 
 	use Closure;
 
@@ -120,7 +126,9 @@ Middleware can also receive additional custom parameters. For example, if your a
 
 Additional middleware parameters will be passed to the middleware after the `$next` argument:
 
-	<?php namespace App\Http\Middleware;
+	<?php
+
+	namespace App\Http\Middleware;
 
 	use Closure;
 
diff --git a/pagination.md b/pagination.md
index 6fac710d18e..804f3354624 100644
--- a/pagination.md
+++ b/pagination.md
@@ -23,7 +23,9 @@ There are several ways to paginate items. The simplest is by using the `paginate
 
 First, let's take a look at calling the `paginate` method on a query. In this example, the only argument passed to `paginate` is the number of items you would like displayed "per page". In this case, let's specify that we would like to display `15` items per page:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use DB;
 	use App\Http\Controllers\Controller;
diff --git a/providers.md b/providers.md
index 5c8b187b9b3..f19d53e74cb 100644
--- a/providers.md
+++ b/providers.md
@@ -34,7 +34,9 @@ As mentioned previously, within the `register` method, you should only bind thin
 
 Now, let's take a look at a basic service provider:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Riak\Connection;
 	use Illuminate\Support\ServiceProvider;
@@ -61,7 +63,9 @@ This service provider only defines a `register` method, and uses that method to
 
 So, what if we need to register a view composer within our service provider? This should be done within the `boot` method. **This method is called after all other service providers have been registered**, meaning you have access to all other services that have been registered by the framework:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Illuminate\Support\ServiceProvider;
 
@@ -123,7 +127,9 @@ If your provider is **only** registering bindings in the [service container](/do
 
 To defer the loading of a provider, set the `defer` property to `true` and define a `provides` method. The `provides` method returns the service container bindings that the provider registers:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Riak\Connection;
 	use Illuminate\Support\ServiceProvider;
diff --git a/queries.md b/queries.md
index 840e07aba8b..4ee015c0e1d 100644
--- a/queries.md
+++ b/queries.md
@@ -28,7 +28,9 @@ The database query builder provides a convenient, fluent interface to creating a
 
 To begin a fluent query, use the `table` method on the `DB` facade. The `table` method returns a fluent query builder instance for the given table, allowing you to chain more constraints onto the query and then finally get the results. In this example, let's just `get` all records from a table:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use DB;
 	use App\Http\Controllers\Controller;
diff --git a/queues.md b/queues.md
index b25f1c58a8f..5798b987133 100644
--- a/queues.md
+++ b/queues.md
@@ -63,7 +63,9 @@ This command will generate a new class in the `app/Jobs` directory, and the clas
 
 Job classes are very simple, normally containing only a `handle` method which is called when the job is processed by the queue. To get started, let's take a look at an example job class:
 
-	<?php namespace App\Jobs;
+	<?php
+
+	namespace App\Jobs;
 
 	use Mail;
 	use App\User;
@@ -142,7 +144,9 @@ As noted above, if an exception occurs while the job is being processed, it will
 
 The default Laravel controller located in `app/Http/Controllers/Controller.php` uses a `DispatchesJob` trait. This trait provides several methods allowing you to conveniently push jobs onto the queue, such as the `dispatch` method:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\User;
 	use Illuminate\Http\Request;
@@ -168,7 +172,9 @@ The default Laravel controller located in `app/Http/Controllers/Controller.php`
 
 Of course, sometimes you may wish to dispatch a job from somewhere in your application besides a route or controller. For that reason, you can include the `DispatchesJobs` trait on any of the classes in your application to gain access to its various dispatch methods. For example, here is a sample class that uses the trait:
 
-	<?php namespace App;
+	<?php
+
+	namespace App;
 
 	use Illuminate\Foundation\Bus\DispatchesJobs;
 
@@ -183,7 +189,9 @@ You may also specify the queue a job should be sent to.
 
 By pushing jobs to different queues, you may "categorize" your queued jobs, and even prioritize how many workers you assign to various queues. This does not push jobs to different queue "connections" as defined by your queue configuration file, but only to specific queues within a single connection. To specify the queue, use the `onQueue` method on the job instance. The `onQueue` method is provided by the base `App\Jobs\Job` class included with Laravel:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\User;
 	use Illuminate\Http\Request;
@@ -214,7 +222,9 @@ By pushing jobs to different queues, you may "categorize" your queued jobs, and
 
 Sometimes you may wish to delay the execution of a queued job. For instance, you may wish to queue a job that sends a customer a reminder e-mail 15 minutes after sign-up. You may accomplish this using the `delay` method on your job class, which is provided by the `Illuminate\Bus\Queueable` trait:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use App\User;
 	use Illuminate\Http\Request;
@@ -249,7 +259,9 @@ In this example, we're specifying that the job should be delayed in the queue fo
 
 It is very common to map HTTP request variables into jobs. So, instead of forcing you to do this manually for each request, Laravel provides some helper methods to make it a cinch. Let's take a look at the `dispatchFrom` method available on the `DispatchesJobs` trait. By default, this trait is included on the base Laravel controller class:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use App\Http\Controllers\Controller;
@@ -395,7 +407,9 @@ When running your [queue listener](#running-the-queue-listener), you may specify
 
 If you would like to register an event that will be called when a queued job fails, you may use the `Queue::failing` method. This event is a great opportunity to notify your team via e-mail or [HipChat](https://www.hipchat.com). For example, we may attach a callback to this event from the `AppServiceProvider` that is included with Laravel:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Queue;
 	use Illuminate\Support\ServiceProvider;
@@ -429,7 +443,9 @@ If you would like to register an event that will be called when a queued job fai
 
 For more granular control, you may define a `failed` method directly on a queue job class, allowing you to perform job specific actions when a failure occurs:
 
-	<?php namespace App\Jobs;
+	<?php
+
+	namespace App\Jobs;
 
 	use App\Jobs\Job;
 	use Illuminate\Queue\SerializesModels;
diff --git a/redis.md b/redis.md
index 3cac9516af4..e7e1fd3dc9a 100644
--- a/redis.md
+++ b/redis.md
@@ -40,7 +40,9 @@ If your Redis server requires authentication, you may supply a password by addin
 
 You may interact with Redis by calling various methods on the `Redis` [facade](/docs/{{version}}/facades). The `Redis` facade supports dynamic methods, meaning you may call any [Redis command](http://redis.io/commands) on the facade and the command will be passed directly to Redis. In this example, we will call the `GET` command on Redis by calling the `get` method on the `Redis` facade:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Redis;
 	use App\Http\Controllers\Controller;
@@ -99,7 +101,9 @@ Laravel also provides a convenient interface to the Redis `publish` and `subscri
 
 First, let's setup a listener on a channel via Redis using the `subscribe` method. We will place this method call within an [Artisan command](/docs/{{version}}/commands) since calling the `subscribe` method begins a long-running process:
 
-	<?php namespace App\Console\Commands;
+	<?php
+
+	namespace App\Console\Commands;
 
 	use Redis;
 	use Illuminate\Console\Command;
diff --git a/releases.md b/releases.md
index 169d28df31f..61ed3115c67 100644
--- a/releases.md
+++ b/releases.md
@@ -46,7 +46,9 @@ To learn more about event broadcasting, check out the [event documentation](/doc
 
 Middleware can now receive additional custom parameters. For example, if your application needs to verify that the authenticated user has a given "role" before performing a given action, you could create a `RoleMiddleware` that receives a role name as an additional argument:
 
-	<?php namespace App\Http\Middleware;
+	<?php
+
+	namespace App\Http\Middleware;
 
 	use Closure;
 
@@ -308,7 +310,9 @@ For more information on the Laravel Flysystem integration, consult the [full doc
 
 Laravel 5.0 introduces **form requests**, which extend the `Illuminate\Foundation\Http\FormRequest` class. These request objects can be combined with controller method injection to provide a boiler-plate free method of validating user input. Let's dig in and look at a sample `FormRequest`:
 
-	<?php namespace App\Http\Requests;
+	<?php
+
+	namespace App\Http\Requests;
 
 	class RegisterRequest extends FormRequest
 	{
diff --git a/requests.md b/requests.md
index 625ac6b023e..5e5e29fd7f7 100644
--- a/requests.md
+++ b/requests.md
@@ -13,7 +13,9 @@
 
 To obtain an instance of the current HTTP request via dependency injection, you should type-hint the `Illuminate\Http\Request` class on your controller constructor or method. The current request instance will automatically be injected by the [service container](/docs/{{version}}/container):
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use Illuminate\Routing\Controller;
@@ -40,7 +42,9 @@ If your controller method is also expecting input from a route parameter, simply
 
 You may still type-hint the `Illuminate\Http\Request` and access your route parameter `id` by defining your controller method like the following:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use Illuminate\Routing\Controller;
diff --git a/responses.md b/responses.md
index cc2b9978b80..72c80759844 100644
--- a/responses.md
+++ b/responses.md
@@ -184,7 +184,9 @@ If you would like to define a custom response that you can re-use in a variety o
 
 For example, from a [service provider's](/docs/{{version}}/providers) `boot` method:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Illuminate\Support\ServiceProvider;
 	use Illuminate\Contracts\Routing\ResponseFactory;
diff --git a/routing.md b/routing.md
index c6caf7cbeae..2702646440b 100644
--- a/routing.md
+++ b/routing.md
@@ -278,7 +278,9 @@ Sometimes you may wish to exclude a set of URIs from CSRF protection. For exampl
 
 You may exclude URIs by adding them to the `$except` property of the `VerifyCsrfToken` middleware:
 
-	<?php namespace App\Http\Middleware;
+	<?php
+
+	namespace App\Http\Middleware;
 
 	use Illuminate\Foundation\Http\Middleware\VerifyCsrfToken as BaseVerifier;
 
diff --git a/scheduling.md b/scheduling.md
index d88c24b1196..cbef2989253 100644
--- a/scheduling.md
+++ b/scheduling.md
@@ -27,7 +27,9 @@ This Cron will call the Laravel command scheduler every minute. Then, Laravel ev
 
 You may define all of your scheduled tasks in the `schedule` method of the `App\Console\Kernel` class. To get started, let's look at an example of scheduling a task. In this example, we will schedule a `Closure` to be called every day at midnight. Within the `Closure` we will execute a database query to clear a table:
 
-	<?php namespace App\Console;
+	<?php
+
+	namespace App\Console;
 
 	use DB;
 	use Illuminate\Console\Scheduling\Schedule;
diff --git a/session.md b/session.md
index 73b7f19fe86..12928842eee 100644
--- a/session.md
+++ b/session.md
@@ -63,7 +63,9 @@ If you need all stored session data to be encrypted, set the `encrypt` configura
 
 First, let's access the session. We can access the session instance via the HTTP request, which can be type-hinted on a controller method. Remember, controller method dependencies are injected via the Laravel [service container](/docs/{{version}}/container):
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use App\Http\Controllers\Controller;
@@ -165,7 +167,9 @@ If you need to keep your flash data around for even more requests, you may use t
 
 To add additional drivers to Laravel's session back-end, you may use the `extend` method on the `Session` [facade](/docs/{{version}}/session). You can call the `extend` method from the `boot` method of a [service provider](/docs/{{version}}/providers):
 
-    <?php namespace App\Providers;
+    <?php
+
+    namespace App\Providers;
 
     use Session;
     use App\Extensions\MongoSessionStore;
@@ -199,7 +203,9 @@ To add additional drivers to Laravel's session back-end, you may use the `extend
 
 Note that your custom session driver should implement the `SessionHandlerInterface`. This interface contains just a few simple methods we need to implement. A stubbed MongoDB implementation looks something like this:
 
-	<?php namespace App\Extensions;
+	<?php
+
+	namespace App\Extensions;
 
 	class MongoHandler implements SessionHandlerInterface
 	{
diff --git a/testing.md b/testing.md
index fc46cbd0255..68abbfd4b73 100644
--- a/testing.md
+++ b/testing.md
@@ -505,7 +505,9 @@ Laravel provides a convenient `expectsJobs` method that will verify that the exp
 
 When testing, you may often want to mock a call to a Laravel [facade](/docs/{{version}}/facades). For example, consider the following controller action:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Cache;
 	use Illuminate\Routing\Controller;
diff --git a/validation.md b/validation.md
index 19beb6dc0f4..6054b70ac7a 100644
--- a/validation.md
+++ b/validation.md
@@ -37,7 +37,9 @@ Of course, the `GET` route will display a form for the user to create a new blog
 
 Next, let's take a look at a simple controller that handles these routes. We'll leave the `store` method empty for now:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Http\Request;
 	use App\Http\Controllers\Controller;
@@ -120,7 +122,9 @@ So, in our example, the user will be redirected to our controller's `create` met
 
 If you wish to customize the format of the validation errors that are flashed to the session when validation fails, override the `formatValidationErrors` on your base controller. Don't forget to import the `Illuminate\Contracts\Validation\Validator` class at the top of the file:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Illuminate\Foundation\Bus\DispatchesJobs;
 	use Illuminate\Contracts\Validation\Validator;
@@ -152,7 +156,9 @@ In this example, we used a traditional form to send data to the application. How
 
 If you do not want to use the `ValidatesRequests` trait's `validate` method, you may create a validator instance manually using the `Validator` [facade](/docs/{{version}}/facades). The `make` method on the facade generates a new validator instance:
 
-	<?php namespace App\Http\Controllers;
+	<?php
+
+	namespace App\Http\Controllers;
 
 	use Validator;
 	use Illuminate\Http\Request;
@@ -726,7 +732,9 @@ The first argument passed to the `sometimes` method is the name of the field we
 
 Laravel provides a variety of helpful validation rules; however, you may wish to specify some of your own. One method of registering custom validation rules is using the `extend` method on the `Validator` [facade](/docs/{{version}}/facades). Let's use this method within a [service provider](/docs/{{version}}/providers) to register a custom validation rule:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Validator;
 	use Illuminate\Support\ServiceProvider;
diff --git a/views.md b/views.md
index 1250a5e1dba..2384bc3cc39 100644
--- a/views.md
+++ b/views.md
@@ -61,7 +61,9 @@ When passing information in this manner, `$data` should be an array with key/val
 
 Occasionally, you may need to share a piece of data with all views that are rendered by your application. You may do so using the view factory's `share` method. Typically, you would place calls to `share` within a service provider's `boot` method. You are free to add them to the `AppServiceProvider` or generate a separate service provider to house them:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	class AppServiceProvider extends ServiceProvider
 	{
@@ -93,7 +95,9 @@ View composers are callbacks or class methods that are called when a view is ren
 
 Let's register our view composers within a [service provider](/docs/{{version}}/providers). We'll use the `view` helper to access the underlying `Illuminate\Contracts\View\Factory` contract implementation. Remember, Laravel does not include a default directory for view composers. You are free to organize them however you wish. For example, you could create an `App\Http\ViewComposers` directory:
 
-	<?php namespace App\Providers;
+	<?php
+
+	namespace App\Providers;
 
 	use Illuminate\Support\ServiceProvider;
 
@@ -132,7 +136,9 @@ Remember, if you create a new service provider to contain your view composer reg
 
 Now that we have registered the composer, the `ProfileComposer@compose` method will be executed each time the `profile` view is being rendered. So, let's define the composer class:
 
-	<?php namespace App\Http\ViewComposers;
+	<?php
+
+	namespace App\Http\ViewComposers;
 
 	use Illuminate\Contracts\View\View;
 	use Illuminate\Users\Repository as UserRepository;