remove old refs

Author: taylorotwell

authentication.md

@@ -104,7 +104,6 @@ Alternatively, once a user is authenticated, you may access the authenticated us
     namespace App\Http\Controllers;
 
     use Illuminate\Http\Request;
-    use Illuminate\Routing\Controller;
 
     class ProfileController extends Controller
     {
@@ -202,7 +201,6 @@ We will access Laravel's authentication services via the `Auth` [facade](/docs/{
     namespace App\Http\Controllers;
 
     use Auth;
-    use Illuminate\Routing\Controller;
 
     class AuthController extends Controller
     {
@@ -421,7 +419,6 @@ Next, you are ready to authenticate users! You will need two routes: one for red
     namespace App\Http\Controllers;
 
     use Socialite;
-    use Illuminate\Routing\Controller;
 
     class AuthController extends Controller
     {

cache.md

@@ -78,7 +78,6 @@ For example, let's import the `Cache` facade into a controller:
     namespace App\Http\Controllers;
 
     use Cache;
-    use Illuminate\Routing\Controller;
 
     class UserController extends Controller
     {

container.md

@@ -172,7 +172,6 @@ The container will automatically inject dependencies for the classes it resolves
 
     namespace App\Http\Controllers;
 
-    use Illuminate\Routing\Controller;
     use App\Users\Repository as UserRepository;
 
     class UserController extends Controller

controllers.md

@@ -229,7 +229,6 @@ You may still type-hint the `Illuminate\Http\Request` and access your route para
     namespace App\Http\Controllers;
 
     use Illuminate\Http\Request;
-    use Illuminate\Routing\Controller;
 
     class UserController extends Controller
     {

testing.md

@@ -547,7 +547,6 @@ When testing, you may often want to mock a call to a Laravel [facade](/docs/{{ve
     namespace App\Http\Controllers;
 
     use Cache;
-    use Illuminate\Routing\Controller;
 
     class UserController extends Controller
     {