update links.

artisan.md

@@ -49,7 +49,7 @@ Sometimes you may wish to execute an Artisan command outside of the CLI. For exa
   //
  });
 
-You may even queue Artisan commands so they are processed in the background by your [queue workers](/docs/5.0/queues):
+You may even queue Artisan commands so they are processed in the background by your [queue workers](/docs/master/queues):
 
  Route::get('/foo', function()
  {

authentication.md

@@ -58,7 +58,7 @@ If you choose not to use the provided `AuthController` implementation, you will
 
  }
 
-The `attempt` method accepts an array of key / value pairs as its first argument. The `password` value will be [hashed](/docs/5.0/hashing). The other values in the array will be used to find the user in your database table. So, in the example above, the user will be retrieved by the value of the `email` column. If the user is found, the hashed password stored in the database will be compared with the hashed `password` value passed to the method via the array. If the two hashed passwords match, a new authenticated session will be started for the user.
+The `attempt` method accepts an array of key / value pairs as its first argument. The `password` value will be [hashed](/docs/master/hashing). The other values in the array will be used to find the user in your database table. So, in the example above, the user will be retrieved by the value of the `email` column. If the user is found, the hashed password stored in the database will be compared with the hashed `password` value passed to the method via the array. If the two hashed passwords match, a new authenticated session will be started for the user.
 
 The `attempt` method will return `true` if authentication was successful. Otherwise, `false` will be returned.
 
@@ -140,7 +140,7 @@ Of course, if you are using the built-in Laravel authentication controllers, a c
 
 #### Authentication Events
 
-When the `attempt` method is called, the `auth.attempt` [event](/docs/5.0/events) will be fired. If the authentication attempt is successful and the user is logged in, the `auth.login` event will be fired as well.
+When the `attempt` method is called, the `auth.attempt` [event](/docs/master/events) will be fired. If the authentication attempt is successful and the user is logged in, the `auth.login` event will be fired as well.
 
 <a name="retrieving-the-authenticated-user"></a>
 ## Retrieving The Authenticated User
@@ -194,7 +194,7 @@ Second, you may access the authenticated user via an `Illuminate\Http\Request` i
 
  }
 
-Thirdly, you may type-hint the `Illuminate\Contracts\Auth\Authenticatable` contract. This type-hint may be added to a controller constructor, controller method, or any other constructor of a class resolved by the [service container](/docs/5.0/container):
+Thirdly, you may type-hint the `Illuminate\Contracts\Auth\Authenticatable` contract. This type-hint may be added to a controller constructor, controller method, or any other constructor of a class resolved by the [service container](/docs/master/container):
 
  <?php namespace App\Http\Controllers;
 
@@ -218,7 +218,7 @@ Thirdly, you may type-hint the `Illuminate\Contracts\Auth\Authenticatable` contr
 <a name="protecting-routes"></a>
 ## Protecting Routes
 
-[Route middleware](/docs/5.0/middleware) can be used to allow only authenticated users to access a given route. Laravel provides the `auth` middleware by default, and it is defined in `app\Http\Middleware\Authenticate.php`. All you need to do is attach it to a route definition:
+[Route middleware](/docs/master/middleware) can be used to allow only authenticated users to access a given route. Laravel provides the `auth` middleware by default, and it is defined in `app\Http\Middleware\Authenticate.php`. All you need to do is attach it to a route definition:
 
  // With A Route Closure...
 
@@ -247,7 +247,7 @@ By default, the `basic` middleware will use the `email` column on the user recor
 
 #### Setting Up A Stateless HTTP Basic Filter
 
-You may also use HTTP Basic Authentication without setting a user identifier cookie in the session, which is particularly useful for API authentication. To do so, [define a middleware](/docs/5.0/middleware) that calls the `onceBasic` method:
+You may also use HTTP Basic Authentication without setting a user identifier cookie in the session, which is particularly useful for API authentication. To do so, [define a middleware](/docs/master/middleware) that calls the `onceBasic` method:
 
  public function handle($request, Closure $next)
  {
@@ -293,7 +293,7 @@ To get started with Socialite, include the package in your `composer.json` file:
 
  "laravel/socialite": "~2.0"
 
-Next, register the `Laravel\Socialite\SocialiteServiceProvider` in your `config/app.php` configuration file. You may also register a [facade](/docs/5.0/facades):
+Next, register the `Laravel\Socialite\SocialiteServiceProvider` in your `config/app.php` configuration file. You may also register a [facade](/docs/master/facades):
 
  'Socialize' => 'Laravel\Socialite\Facades\Socialite',
 

billing.md

@@ -156,7 +156,7 @@ To verify that a user is subscribed to your application, use the `subscribed` co
   //
  }
 
-The `subscribed` method makes a great candidate for a [route middleware](/docs/5.0/middleware):
+The `subscribed` method makes a great candidate for a [route middleware](/docs/master/middleware):
 
  public function handle($request, Closure $next)
  {

bus.md

@@ -55,7 +55,7 @@ The newly generated class will be placed in the `app/Commands` directory. By def
 
  }
 
-The `handle` method may also type-hint dependencies, and they will be automatically injected by the [IoC container](/docs/5.0/container). For example:
+The `handle` method may also type-hint dependencies, and they will be automatically injected by the [IoC container](/docs/master/container). For example:
 
   /**
   * Execute the command.
@@ -116,7 +116,7 @@ If you would like to convert an existing command into a queued command, simply i
 
 Then, just write your command normally. When you dispatch it to the bus that bus will automatically queue the command for background processing. It doesn't get any easier than that.
 
-For more information on interacting with queued commands, view the full [queue documentation](/docs/5.0/queues).
+For more information on interacting with queued commands, view the full [queue documentation](/docs/master/queues).
 
 <a name="command-pipeline"></a>
 ## Command Pipeline
@@ -141,7 +141,7 @@ A command pipe is defined with a `handle` method, just like a middleware:
 
  }
 
-Command pipe classes are resolved through the [IoC container](/docs/5.0/container), so feel free to type-hint any dependencies you need within their constructors.
+Command pipe classes are resolved through the [IoC container](/docs/master/container), so feel free to type-hint any dependencies you need within their constructors.
 
 You may even define a `Closure` as a command pipe:
 

collections.md

@@ -31,7 +31,7 @@ As mentioned above, the `collect` helper will return a new `Illuminate\Support\C
 
  $collection = Collection::make([1, 2, 3]);
 
-Of course, collections of [Eloquent](/docs/5.0/eloquent) objects are always returned as `Collection` instances; however, you should feel free to use the `Collection` class wherever it is convenient for your application.
+Of course, collections of [Eloquent](/docs/master/eloquent) objects are always returned as `Collection` instances; however, you should feel free to use the `Collection` class wherever it is convenient for your application.
 
 #### Explore The Collection
 

commands.md

@@ -122,4 +122,4 @@ Sometimes you may wish to call other commands from your command. You may do so u
 
 #### Registering An Artisan Command
 
-Once your command is finished, you need to register it with Artisan so it will be available for use. This is typically done in the `app/Console/Kernel.php` file. Within this file, you will find a list of commands in the `commands` property. To register your command, simply add it to this list. When Artisan boots, all the commands listed in this property will be resolved by the [IoC container](/docs/5.0/container) and registered with Artisan.
+Once your command is finished, you need to register it with Artisan so it will be available for use. This is typically done in the `app/Console/Kernel.php` file. Within this file, you will find a list of commands in the `commands` property. To register your command, simply add it to this list. When Artisan boots, all the commands listed in this property will be resolved by the [IoC container](/docs/master/container) and registered with Artisan.

configuration.md

@@ -30,7 +30,7 @@ Renaming your application is entirely optional, and you are free to keep the `Ap
 
 Laravel needs very little configuration out of the box. You are free to get started developing! However, you may wish to review the `config/app.php` file and its documentation. It contains several options such as `timezone` and `locale` that you may wish to change according to your location.
 
-Once Laravel is installed, you should also [configure your local environment](/docs/5.0/configuration#environment-configuration).
+Once Laravel is installed, you should also [configure your local environment](/docs/master/configuration#environment-configuration).
 
 > **Note:** You should never have the `app.debug` configuration option set to `true` for a production application.
 
@@ -83,7 +83,7 @@ You may also pass arguments to the `environment` method to check if the environm
   // The environment is either local OR staging...
  }
 
-To obtain an instance of the application, resolve the `Illuminate\Contracts\Foundation\Application` contract via the [service container](/docs/5.0/container). Of course, if you are within a [service provider](/docs/5.0/providers), the application instance is available via the `$this->app` instance variable.
+To obtain an instance of the application, resolve the `Illuminate\Contracts\Foundation\Application` contract via the [service container](/docs/master/container). Of course, if you are within a [service provider](/docs/master/providers), the application instance is available via the `$this->app` instance variable.
 
 An application instance may also be accessed via the `app` helper of the `App` facade:
 
@@ -117,7 +117,7 @@ The default template for maintenance mode responses is located in `resources/vie
 
 ### Maintenance Mode & Queues
 
-While your application is in maintenance mode, no [queued jobs](/docs/5.0/queues) will be handled. The jobs will continue to be handled as normal once the application is out of maintenance mode.
+While your application is in maintenance mode, no [queued jobs](/docs/master/queues) will be handled. The jobs will continue to be handled as normal once the application is out of maintenance mode.
 
 <a name="pretty-urls"></a>
 ## Pretty URLs
@@ -143,4 +143,4 @@ On Nginx, the following directive in your site configuration will allow "pretty"
   try_files $uri $uri/ /index.php?$query_string;
  }
 
-Of course, when using [Homestead](/docs/5.0/homestead), pretty URLs will be configured automatically.
+Of course, when using [Homestead](/docs/master/homestead), pretty URLs will be configured automatically.

container.md

@@ -61,7 +61,7 @@ A deep understanding of the Laravel service container is essential to building a
 
 ### Binding
 
-Almost all of your service container bindings will be registered within [service providers](/docs/5.0/providers), so all of these examples will demonstrate using the container in that context. However, if you need an instance of the container elsewhere in your application, such as a factory, you may type-hint the `Illuminate\Contracts\Container\Container` contract and an instance of the container will be injected for you. Alternatively, you may use the `App` facade to access the container.
+Almost all of your service container bindings will be registered within [service providers](/docs/master/providers), so all of these examples will demonstrate using the container in that context. However, if you need an instance of the container elsewhere in your application, such as a factory, you may type-hint the `Illuminate\Contracts\Container\Container` contract and an instance of the container will be injected for you. Alternatively, you may use the `App` facade to access the container.
 
 #### Registering A Basic Resolver
 
@@ -295,7 +295,7 @@ Laravel provides several opportunities to use the service container to increase
 
  }
 
-In this example, the `OrderRepository` class will automatically be injected into the controller. This means that a "mock" `OrderRepository` may be bound into the container when [unit testing](/docs/5.0/testing), allowing for painless stubbing of database layer interaction.
+In this example, the `OrderRepository` class will automatically be injected into the controller. This means that a "mock" `OrderRepository` may be bound into the container when [unit testing](/docs/master/testing), allowing for painless stubbing of database layer interaction.
 
 #### Other Examples Of Container Usage
 

contracts.md

@@ -136,7 +136,7 @@ Contract | Laravel 4.x Facade
 <a name="how-to-use-contracts"></a>
 ## How To Use Contracts
 
-So, how do you get an implementation of a contract? It's actually quite simple. Many types of classes in Laravel are resolved through the [service container](/docs/5.0/container), including controllers, event listeners, filters, queue jobs, and even route Closures. So, to get an implementation of a contract, you can just "type-hint" the interface in the constructor of the class being resolved. For example, take a look at this event handler:
+So, how do you get an implementation of a contract? It's actually quite simple. Many types of classes in Laravel are resolved through the [service container](/docs/master/container), including controllers, event listeners, filters, queue jobs, and even route Closures. So, to get an implementation of a contract, you can just "type-hint" the interface in the constructor of the class being resolved. For example, take a look at this event handler:
 
  <?php namespace App\Handlers\Events;
 
@@ -175,4 +175,4 @@ So, how do you get an implementation of a contract? It's actually quite simple.
 
  }
 
-When the event listener is resolved, the service container will read the type-hints on the constructor of the class, and inject the appropriate value. To learn more about registering things in the service container, check out [the documentation](/docs/5.0/container).
+When the event listener is resolved, the service container will read the type-hints on the constructor of the class, and inject the appropriate value. To learn more about registering things in the service container, check out [the documentation](/docs/master/container).

controllers.md

@@ -76,7 +76,7 @@ You may access the name of the controller action being run using the `currentRou
 <a name="controller-middleware"></a>
 ## Controller Middleware
 
-[Middleware](/docs/5.0/middleware) may be specified on controller routes like so:
+[Middleware](/docs/master/middleware) may be specified on controller routes like so:
 
  Route::get('profile', [
   'middleware' => 'auth',
@@ -212,7 +212,7 @@ If it becomes necessary to add additional routes to a resource controller beyond
 
 #### Constructor Injection
 
-The Laravel [service container](/docs/5.0/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 Laravel [service container](/docs/master/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:
 
  <?php namespace App\Http\Controllers;
 
@@ -239,7 +239,7 @@ The Laravel [service container](/docs/5.0/container) is used to resolve all Lara
 
  }
 
-Of course, you may also type-hint any [Laravel contract](/docs/5.0/contracts). If the container can resolve it, you can type-hint it.
+Of course, you may also type-hint any [Laravel contract](/docs/master/contracts). If the container can resolve it, you can type-hint it.
 
 #### Method Injection
 
@@ -290,7 +290,7 @@ If your controller method is also expecting input from a route parameter, simply
 
  }
 
-> **Note:** Method injection is fully compatible with [model binding](/docs/5.0/routing#route-model-binding). The container will intelligently determine which arguments are model bound and which arguments should be injected.
+> **Note:** Method injection is fully compatible with [model binding](/docs/master/routing#route-model-binding). The container will intelligently determine which arguments are model bound and which arguments should be injected.
 
 <a name="route-caching"></a>
 ## Route Caching