diff --git a/en/controllers/middleware.rst b/en/controllers/middleware.rst
index 821a2962d1..aaef527b90 100644
--- a/en/controllers/middleware.rst
+++ b/en/controllers/middleware.rst
@@ -81,6 +81,9 @@ a variety of operations::
             $layer
         );
 
+In addition to applying middleware to your entire application, you can apply
+middleware to specific sets of routes using :ref:`connecting-scoped-middleware`.
+
 Adding Middleware from Plugins
 ------------------------------
 
diff --git a/en/development/routing.rst b/en/development/routing.rst
index c1dc6df76b..5f98756f49 100644
--- a/en/development/routing.rst
+++ b/en/development/routing.rst
@@ -42,14 +42,14 @@ homepage of your site is visited. Sometimes you need dynamic routes that will
 accept multiple parameters, this would be the case, for example of a route for
 viewing an article's content::
 
-    Router::connect('/articles/*', ['controller' => 'Articles', 'action' => 'view']);
+    $routes->connect('/articles/*', ['controller' => 'Articles', 'action' => 'view']);
 
 The above route will accept any URL looking like ``/articles/15`` and invoke the
 method ``view(15)`` in the ``ArticlesController``. This will not, though,
 prevent people from trying to access URLs looking like ``/articles/foobar``. If
 you wish, you can restring some parameters to conform to a regular expression::
 
-    Router::connect(
+    $routes->connect(
         '/articles/:id',
         ['controller' => 'Articles', 'action' => 'view'],
         ['id' => '\d+', 'pass' => ['id']]
@@ -75,14 +75,16 @@ Routes can also be labelled with a unique name, this allows you to quickly
 reference them when building links instead of specifying each of the routing
 parameters::
 
-    use Cake\Routing\Router;
 
-    Router::connect(
+    // In routes.php
+    $routes->connect(
         '/login',
         ['controller' => 'Users', 'action' => 'login'],
         ['_name' => 'login']
     );
 
+    use Cake\Routing\Router;
+
     echo Router::url(['_name' => 'login']);
     // Will output
     /login
@@ -110,12 +112,11 @@ added your own routes, you can remove the default routes if you don't need them.
 Connecting Routes
 =================
 
-.. php:staticmethod:: connect($route, $defaults = [], $options = [])
+.. php:method:: connect($route, $defaults = [], $options = [])
 
 To keep your code :term:`DRY` you should use 'routing scopes'. Routing
 scopes not only let you keep your code DRY, they also help Router optimize its
-operation. As seen above you can also use ``Router::connect()`` to connect
-routes. This method defaults to the ``/`` scope. To create a scope and connect
+operation. This method defaults to the ``/`` scope. To create a scope and connect
 some routes we'll use the ``scope()`` method::
 
     // In config/routes.php
@@ -753,6 +754,40 @@ Then to create links which map back to the routes simply use::
 File extensions are used by :doc:`/controllers/components/request-handling`
 to do automatic view switching based on content types.
 
+.. _connecting-scoped-middleware:
+
+Connecting Scoped Middleware
+----------------------------
+
+Middleware can be applied to your entire application, or to an individual
+routing scope. Before middleware can be applied to a scope, it needs to be
+registered::
+
+    // in config/routes.php
+    use Cake\Http\Middleware\CsrfProtectionMiddleware;
+    use Cake\Http\Middleware\EncryptedCookieMiddleware;
+
+    Router::scope('/', function ($routes) {
+        $routes->registerMiddleware('csrf', new CsrfProtectionMiddleware());
+        $routes->registerMiddleware('cookies', new EncryptedCookiesMiddleware());
+    });
+
+Once registered into the route builder, middleware can be applied to specific
+scopes::
+
+    $routes->scope('/cms', function ($routes) {
+        // Enable registered middleware for this scope.
+        $routes->applyMiddleware('csrf', 'cookies');
+    });
+
+In situations where you have nested scopes, all middleware applied in each scope
+will be applied starting from the top-most scope and ending with the nested
+scopes. By applying middleware in specific scopes you can omit complicated URL
+matching logic out of your middleware layers and let them focus on their task.
+
+.. versionadded:: 3.5.0
+    Scoped middleware support was added in 3.5.0
+
 .. _resource-routes:
 
 Creating RESTful Routes