anchor.diff:  The following table provides some example CNAME record mappings.
   
   <table border="1" class="nice" >
  -    <tr>
  -        <th>Record Set in Custom Domain</th>
  -        <th>Type</th>
  -        <th>Target in <%=vars.product_short%></th>
  -    </tr>
  -    <tr>
  -        <td>myapp.yourcustomdomain.com.</td>
  -        <td>CNAME</td>
  -        <td>myapp.<%=vars.app_domain%></td>
  -    </tr>
  -    <tr>
  -        <td>www.yourcustomdomain.com.</td>
  -        <td>CNAME</td>
  -        <td>myapp.<%=vars.app_domain%></td>
  -    </tr>
  +  <tr>
  +    <th>Record Set in Custom Domain</th>
  +    <th>Type</th>
  +    <th>Target in <%=vars.product_short%></th>
  +  </tr>
  +  <tr>
  +    <td>myapp.yourcustomdomain.com.</td>
  +    <td>CNAME</td>
  +    <td>myapp.<%=vars.app_domain%></td>
  +  </tr>
  +  <tr>
  +    <td>www.yourcustomdomain.com.</td>
  +    <td>CNAME</td>
  +    <td>myapp.<%=vars.app_domain%></td>
  +  </tr>
   </table>
   
   After you create the CNAME mapping, your DNS provider routes your custom domain to `myapp.<%=vars.app_domain%>`. 
  
positive.code: 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%>.
  
  <table border="1" class="nice" >
      <tr>
          <th>Record</th>
          <th>Name</th>
          <th>Target</th>
          <th>Note</th>
      </tr>
      <tr>
          <td>ALIAS or ANAME</td>
          <td>empty or @</td>
          <td><%=vars.private_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 you can use subdomain redirection, also known as domain forwarding, to redirect requests for your root domain to a subdomain configured as a CNAME.
  
negative.code: 
  ### <a id='private-domains'></a>Private Domains ###
  
  Org Managers can add private domains, or custom domains, and give members of the org permission to create routes for privately registered domain names. Private domains can be shared with other orgs, enabling users of those orgs to create routes from the domain.
  
  Private domains can be HTTP or HTTPS only. TCP Routing is supported for Shared Domains only.
  
  #### <a id='create-private-domain'></a>Create a Private Domain ####
  
  