anchor.diff:  
   ## <a id='routes'></a>Routes ##
   
  -The <%=vars.product_short%> router routes requests to applications by associating an app with an address, known as a route. This association is called a mapping: for example, the cf CLI command for associating an app and route is `map-route`.
  +The <%=vars.product_short%> router routes requests to applications by associating an app with an address, known as a route. This association is called a mapping: for example, the cf CLI command for associating an app and route is [cf map-route](http://cli.cloudfoundry.org/en-US/cf/map-route.html).
   
   The routing tier compares each request with a list of all the routes mapped to apps and attempts to find the best match. For example, the router would make the following matches for the two routes `myapp.<%=vars.app_domain%>` and `myapp.<%=vars.app_domain%>/products`:
   
  
positive.code: 
  <pre class="terminal">
  $ cf create-route tcp.<%=vars.app_domain%> --port 60035
  </pre>
  
  ### <a id='list-routes'></a>List Routes ###
  
  Developers can list routes for the current space with the `cf routes` command. A route is uniquely identified by the combination of hostname, domain, and path.
  
  <pre class="terminal">
  $ cf routes
  
negative.code: 
  In <%=vars.product_short%>, a hostname is the domain name label that indicates a subdomain of the domain associated with the route. 
  
  A developer can create the route `myapp.<%=vars.app_domain%>` in space `my-space` by specifying the hostname `myapp` and the domain `<%=vars.app_domain%>` in the [cf create-route](http://cli.cloudfoundry.org/en-US/cf/create-route.html) command: 
  
  <pre class="terminal">
  $ cf create-route my-space <%=vars.app_domain%> --hostname myapp
  Creating route myapp.<%=vars.app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
  OK
  
  </pre>
  
  This command instructs <%=vars.product_short%> to only route requests to apps mapped to this route from the following URLs: 
  