From 0e523ffc28b7e9d2600a76dc371769a320ccd0a5 Mon Sep 17 00:00:00 2001 From: ydakuka Date: Fri, 28 Jul 2017 15:44:10 +0300 Subject: [PATCH] Squashed commit of the following: commit 4a3d295f3011e771cddead80de7497ca15d15c13 Author: Yauheni Dakuka Date: Fri Jul 28 14:31:35 2017 +0300 Update routing.md commit 620a4ce47288e3ef6504290c78f931214968e7e3 Author: Yauheni Dakuka Date: Fri Jul 28 14:19:29 2017 +0300 [ci skip] update routing guide --- guides/source/routing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/source/routing.md b/guides/source/routing.md index 6ed453a726..f52b1862a8 100644 --- a/guides/source/routing.md +++ b/guides/source/routing.md @@ -418,7 +418,7 @@ resources :articles do end ``` -Also you can use them in any place that you want inside the routes, for example in a scope or namespace call: +Also you can use them in any place that you want inside the routes, for example in a `scope` or `namespace` call: ```ruby namespace :articles do @@ -808,14 +808,14 @@ NOTE: For the curious, `'articles#index'` actually expands out to `ArticlesContr If you specify a Rack application as the endpoint for a matcher, remember that the route will be unchanged in the receiving application. With the following -route your Rack application should expect the route to be '/admin': +route your Rack application should expect the route to be `/admin`: ```ruby match '/admin', to: AdminApp, via: :all ``` If you would prefer to have your Rack application receive requests at the root -path instead, use mount: +path instead, use `mount`: ```ruby mount AdminApp, at: '/admin'