anchor.diff:  Route store.<%=vars.app_domain%>/products does exist
   </pre>
   
  -### <a id='map-route'></a>Map a Route to Your Application ###
  +### <a id='map-route'></a> Map a Route to Your Application
   
   For an app to receive requests to a route, developers must map the route to the app with the [cf map-route](https://cli.cloudfoundry.org/en-US/cf/map-route.html) command. If the route does not already exist, this command creates it.
   
  -<p class="note"><strong>Note</strong>: Any app that is not routed to port <code>80</code> or port <code>443</code> must be explicitly mapped using the <code>cf map-route</code> command . Otherwise, the route is automatically mapped to port <code>443</code>.
  +<p class="note"><strong>Note:</strong> Any app that is not routed to port <code>80</code> or port <code>443</code> must be explicitly mapped using the <code>cf map-route</code> command . Otherwise, the route is automatically mapped to port <code>443</code>.
   </p>
   
  -Developers can create and reserve routes for later use by following the steps in the <a href="#map-route-manually">Manually Map a Route</a> section. Or they can map routes to their app immediately as part of a push by following the steps in the <a href="#map-route-on-push">Map a Route with Application Push</a> section.
  -
  -<p class="note"><strong>Note</strong>: Changes to route mappings are executed asynchronously. On startup, an application will be accessible at its route within a few seconds. Similarly, upon mapping a new route to a running app, the app will be accessible at this route within a few seconds of the CLI exiting successfully.</p>
  -
  -#### <a id='map-route-manually'></a>Manually Map a Route ####
  +Developers can create and reserve routes for later use by following the steps in the [Manually Map a Route](#map-route-manually) section. Or they can map routes to their app immediately as part of a push by following the steps in the [Map a Route with Application Push](#map-route-on-push) section.
  +
  +<p class="note"><strong>Note:</strong> Changes to route mappings are executed asynchronously. On startup, an application will be accessible at its route within a few seconds. Similarly, upon mapping a new route to a running app, the app will be accessible at this route within a few seconds of the CLI exiting successfully.</p>
  +
  +#### <a id='map-route-manually'></a> Manually Map a Route
   
   Given the following routes and applications:
   
  
positive.code: 
  <%=vars.dns_warning%>
  
  #### <a id='root-domain-dns'></a>Configuring DNS for Your Registered Root Domain ####
  
  To use your root domain (for example, `example.com`) for apps on <%=vars.product_short%> you can either use custom DNS record types like ALIAS and ANAME, if your DNS provider offers them, or subdomain redirection.
  
  <p class="note"><strong>Note</strong>: Root domains are also called zone apex domains.</p>
  
  If your DNS provider supports using an ALIAS or ANAME record, configure your root domain with your DNS provider to point at a shared domain in <%=vars.product_short%>.
  
  
negative.code: 
  If a client sends a request to `http://app.foo.<%=vars.app_domain%>` by accident, attempting to reach `myapp.foo.<%=vars.app_domain%>`, <%=vars.product_short%> routes the request to the app mapped to the route `*.foo.<%=vars.app_domain%>`.
  
  #### <a id='create-route-with-path'></a> Create an HTTP Route with a Path
  
  Developers can use paths to route requests for the same hostname and domain to different apps.
  
  