anchor.diff:  
   You can view available domains for the targeted organization using the `cf domains` command.
   
  -In this example, there are two available domains: a system-wide default `<%=vars.app_domain%>` domain and the custom `example.org` domain.
  -
  -<pre class="terminal">
  -	$ cf domains
  -	Getting domains in org console as user@example.org... OK
  -
  -	name           status
  -	<%=vars.app_domain%>    shared
  -	example.org    owned
  -</pre>
  -
  -### <a id='assign-domains-subdomains'></a>Assign Domains and Subdomains ###
  -
  -You can assign a domain and subdomain to your application from either the command line with `cf push` or in the application manifest.
  +In this example, there are two available domains: a system-wide default "<%=vars.app_domain%>" domain and the custom "example.org" domain.
  +
  +<pre class="terminal">
  +$ cf domains
  +Getting domains in org console as user@example.org... OK
  +
  +name           status
  +<%=vars.app_domain%>    shared
  +example.org    owned
  +</pre>
  +
  +### <a id='assign-domains-hosts'></a>Assign Domains and Hosts ###
  +
  +You can assign a domain and host to your application using either the command line or the application manifest.
   
   #### <a id='assign-at-push'></a>Assign Using the cf CLI ####
   
  -When you run `cf push`, you can optionally assign a domain and subdomain to the application.
  -
  -- Domain: Use the `-d` flag to specify one of the domains available to the targeted org.
  -- Subdomain: Use the `-n` flag to provide a string for the subdomain.
  +When you run `cf push`, you can optionally assign a domain and host to the application.
  +
  +- **Domain**: Use the `-d` flag to specify one of the domains available to the targeted org.
  +- **Subdomain**: Use the `-n` flag to provide a string for the host.
   
   The route Cloud Foundry creates for the application as a result of the following command is `myapp.example.org`.
   
   <pre class="terminal">
  -	$ cf push myapp -d example.org -n myapp
  +$ cf push myapp -d example.org -n myapp
   </pre>
   
   #### <a id='assign-in-manifest'></a>Assign Using the Manifest ####
   
  -When you create or edit the manifest for an application, you can use the `host` and `domain` attributes to define the subdomain and domain components of the application route, respectively. For more information, see [Application Manifests](../deploy-apps/manifest.html).
  +When you create or edit the manifest for an application, you can use the `host` and `domain` attributes to define the host and domain components of the application route, respectively. For more information, see [Application Manifests](../deploy-apps/manifest.html).
   
   ### <a id='delete-domains'></a>Delete a Domain ###
   
   You can delete a domain from Cloud Foundry with the `cf delete-domain` command:
   
   <pre class="terminal">
  -	$ cf delete-domain example.org
  +$ cf delete-domain example.org
   </pre>
   
   ## <a id='customize-route'></a>Managing Your Routes ##
   
   ### <a id='list-routes'></a>List Routes ###
   
  -You can list routes for the current space with `cf routes` command. Note that the subdomain is shown as "host," separate from the domain segment.
  +You can list routes for the current space with `cf routes` command. Note that the host is separate from the domain segment.
   
   For example:
   
   <pre class="terminal">
  -	$ cf routes
  -	Getting routes as user@example.org ...
  -
  -	host                     domain          apps
  -	myapp                    example.org     myapp1
  -	myapp2
  -	1test                    <%=vars.app_domain%>     1test
  -	sinatra-hello-world      <%=vars.app_domain%>     sinatra-hello-world
  -	sinatra-to-do            <%=vars.app_domain%>     sinatra-to-do
  +$ cf routes
  +Getting routes as user@example.org ...
  +
  +host                     domain          apps
  +myapp                    example.org     myapp1
  +myapp2
  +1test                    <%=vars.app_domain%>     1test
  +sinatra-hello-world      <%=vars.app_domain%>     sinatra-hello-world
  +sinatra-to-do            <%=vars.app_domain%>     sinatra-to-do
   </pre>
   
   ### <a id='create-route'></a>Create a Route ###
  
positive.code: 	<tr>
  		<td>ALIAS or ANAME</td>
  		<td>empty or @</td>
  		<td>yourappname.<%=vars.app_domain%>.</td>
  		<td>Refer to your DNS provider documentation to determine whether to use an empty or @ value for the Name entry.</td>
  	</tr>
  </table>
  
  If your DNS provider does not support ANAME or ALIAS records, use _subdomain redirection_, a technique also known as _domain forwarding_, to add a custom root domain. If you use this method, note that SSL requests to the root domain result in an error because the SSL certificate generally only matches the subdomain. This error does not display if you are not using SSL or are only using SSL with URLs in subdomain form, meaning `https://www.example.com`.
  
  Configure the redirect from the root domain to the target <code>www</code> subdomain, and configure the <code>www</code> subdomain as a CNAME record reference to the target app URL. The table below illustrates this pattern.
  
  <table border="1" class="nice" >
  	<tr>
  
negative.code: You can remove a route from an app using the `cf unmap-route` command. Unmapping a route leaves the route available in the targeted space for later use.
  
  <pre class="terminal">
  $ cf unmap-route myapp example.org -n myapp
  </pre>
  
  You can remove a route from a space using the `cf delete-route` command:
  
  <pre class="terminal">
  $ cf delete-route example.org -n myapp
  </pre>
  
  Note that for each of the above commands, using the `-n` parameter to specify the host is optional.