anchor.diff:  
   This approach creates a route with the same address as the domain itself and is permitted for private domains only. For more information, see the [Private Domains](#private-domains) section.
   
  -A developer can create a route in space `my-space` from the domain `<%=vars.private_app_domain%>` with no hostname with the [cf create-route](http://cli.cloudfoundry.org/en-US/cf/create-route.html) command:
  +A developer can create a route in space `my-space` from the domain `<%=vars.private_app_domain%>` with no hostname with the [cf create-route](https://cli.cloudfoundry.org/en-US/cf/create-route.html) command:
   
   <pre class="terminal">
   $ cf create-route my-space <%=vars.private_app_domain%>
  
positive.code: 
  ### <a id='list-routes'></a>List Routes ###
  
  Developers can list routes for the current space with the [cf routes](http://cli.cloudfoundry.org/en-US/cf/routes.html) command. A route is uniquely identified by the combination of hostname, domain, port, and path.
  
  <pre class="terminal">
  $ cf routes
  
negative.code: 
  ### <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>
  