anchor.diff:  
   #### <a id='map-route-manually'></a>Manually Map a Route ####
   
  -The `-n HOSTNAME` option identfies the route to map to your application. Omit the `-n` flag if your route was created from a private domain without a hostname, as described in [Routes without Hostnames](#create-route-without-hostname).
  -
  -<pre class="terminal">
  -$ cf map-route myapp <%=vars.app_domain%> -n myapp
  -</pre>
  -
  -The command below maps the wildcard route `*.foo.<%=vars.app_domain%>` to the application `myfallbackapp`.
  -
  -<pre class="terminal">
  -$ cf map-route myfallbackapp foo.<%=vars.app_domain%> -n *
  -</pre>
  -
  -
  -The `--path` option allows you to map an application to a route with a path, as described in [Create Route with a Path](#create-route-with-path).
  -
  -For example, based on the following:
  +Given the following routes and applications:
  +
   <table border="1" class="nice" >
   	<tr>
   		<th>Route</th>
  
positive.code: To check to see if a particular route is already taken, use the `cf check-route` command.
  
  Check if a particular route exists:
  <pre class="terminal">
  $ cf check-route myapp <%=vars.app_domain%>
  Checking for route...
  OK
  Route myapp.<%=vars.app_domain%> does exist
  </pre>
  
  Check if a particular route with path exists:
  <pre class="terminal">
  $ cf check-route store <%=vars.app_domain%> --path /products
  Checking for route...
  
negative.code: Routes can be created and subsequently added to an app. See [Map a Route to your App](#map-route) for further detail.
  
  <pre class="terminal">
  $ cf create-route my-space <%=vars.app_domain%> --hostname myapp
  </pre>
  
  Only requests for `http://myapp.<%=vars.app_domain%>`, `https://myapp.<%=vars.app_domain%>`, or any path under those URLs (for example `http://myapp.<%=vars.app_domain%>/bar`), will be routed to apps mapped to this route.
  