From b6d5612f551e982441097a67df001b5da99dee58 Mon Sep 17 00:00:00 2001
From: Vishnu Atrai <me@vishnuatrai.com>
Date: Fri, 15 Jul 2011 23:56:58 +0530
Subject: Should be "match" instead of "map"

---
 railties/guides/source/routing.textile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'railties/guides/source/routing.textile')

diff --git a/railties/guides/source/routing.textile b/railties/guides/source/routing.textile
index 06b3579720..57e390f385 100644
--- a/railties/guides/source/routing.textile
+++ b/railties/guides/source/routing.textile
@@ -560,13 +560,13 @@ would match +zoo/woo/foo/bar/baz+ with +params[:a]+ equals +"zoo/woo"+, and +par
 NOTE: Starting from Rails 3.1, wildcard routes will always match the optional format segment by default. For example if you have this route:
 
 <ruby>
-map '*pages' => 'pages#show'
+match '*pages' => 'pages#show'
 </ruby>
 
 NOTE: By requesting +"/foo/bar.json"+, your +params[:pages]+ will be equals to +"foo/bar"+ with the request format of JSON. If you want the old 3.0.x behavior back, you could supply +:format => false+ like this:
 
 <ruby>
-map '*pages' => 'pages#show', :format => false
+match '*pages' => 'pages#show', :format => false
 </ruby>
 
 h4. Redirection
-- 
cgit v1.2.3

