Updated docs

docs/guide.1

@@ -176,14 +176,14 @@ A route is simple a string which is compiled to a \fIRegExp\fR internally\. For
 .IP "" 0
 .
 .P
-Regular expression literals may also be passed for complex uses\. Since capture groups with literal \fIRegExp\fR\'s are anonymous we use the \fIparams\.captures\fR array\.
+Regular expression literals may also be passed for complex uses\. Since capture groups with literal \fIRegExp\fR\'s are anonymous we can access them directly from the \fIparams\fR array\.
 .
 .IP "" 4
 .
 .nf
 
 app\.get(/^\\/users?(?:\\/(\\d+)(?:\\\.\\\.(\\d+))?)?/, function(req, res, params){
-    res\.send(params\.captures);
+    res\.send(params);
 });
 .
 .fi

docs/guide.html

@@ -340,10 +340,10 @@ <h3 id="Routing">Routing</h3>
 </code></pre>
 
 <p>Regular expression literals may also be passed for complex uses. Since capture
-groups with literal <em>RegExp</em>'s are anonymous we use the <em>params.captures</em> array.</p>
+groups with literal <em>RegExp</em>'s are anonymous we can access them directly from the <em>params</em> array.</p>
 
 <pre><code>app.get(/^\/users?(?:\/(\d+)(?:\.\.(\d+))?)?/, function(req, res, params){
-    res.send(params.captures);
+    res.send(params);
 });
 </code></pre>
 

docs/guide.md

@@ -101,10 +101,10 @@ when _/user/:id_ is compiled, a simplified version of the regexp may look simila
     \/user\/([^\/]+)\/?
 
 Regular expression literals may also be passed for complex uses. Since capture
-groups with literal _RegExp_'s are anonymous we use the _params.captures_ array.
+groups with literal _RegExp_'s are anonymous we can access them directly from the _params_ array.
 
     app.get(/^\/users?(?:\/(\d+)(?:\.\.(\d+))?)?/, function(req, res, params){
-        res.send(params.captures);
+        res.send(params);
     });
 
 Curl requests against the previously defined route: