Permalink
Browse files

Clarifying improvements to router documentation (#4137)

* Improve documentation of what router actions are passed

* Clarify that actions are functions (as opposed to events)
  • Loading branch information...
captbaritone authored and akre54 committed May 1, 2017
1 parent 4445d49 commit a0825c77ac341acd0999795ca3df60db6c69f431
Showing with 2 additions and 2 deletions.
  1. +2 −2 index.html
View
@@ -2388,7 +2388,7 @@ <h2 id="Router">Backbone.Router</h2>
<p id="Router-extend">
<b class="header">extend</b><code>Backbone.Router.extend(properties, [classProperties])</code>
<br />
- Get started by creating a custom router class. Define actions that are
+ Get started by creating a custom router class. Define action functions that are
triggered when certain URL fragments are
matched, and provide a <a href="#Router-routes">routes</a> hash
that pairs routes to actions. Note that you'll want to avoid using a
@@ -2430,7 +2430,7 @@ <h2 id="Router">Backbone.Router</h2>
<p>
For example, a route of <tt>"search/:query/p:page"</tt> will match
a fragment of <tt>#search/obama/p2</tt>, passing <tt>"obama"</tt>
- and <tt>"2"</tt> to the action.
+ and <tt>"2"</tt> to the action as positional arguments.
</p>
<p>

0 comments on commit a0825c7

Please sign in to comment.