anchor.diff:  
   ### <a id="post-deploy"></a> Post-Deployment Steps
   
  -In the following procedures, you use the Cloud Foundry Command Line Interface (cf CLI) to add the TCP shared domain and configure org quotas to grant developers the ability to create TCP routes. This requires an admin user account.
  -
  -For more information about the cf CLI, see [Using the Cloud Foundry Command Line Interface (cf CLI)](../cf-cli/index.html).
  -
  -#### <a id="configure-domain"></a> Configure <%= vars.app_runtime_abbr %> with Your TCP Domain
  -
  -After deployment, you must configure <%= vars.app_runtime_abbr %> with the domain that you configured in the pre-deployment step above so developers can create TCP routes from it.
  +In the following procedures, you use the Cloud Foundry Command Line Interface
  +(cf CLI) to add the TCP shared domain and configure org quotas to grant
  +developers the ability to create TCP routes. This requires an admin user account.
  +
  +For more information about the cf CLI, see [Using the Cloud Foundry Command Line
  +Interface (cf CLI)](../cf-cli/index.html).
  +
  +#### <a id="configure-domain"></a> Configure <%= vars.app_runtime_abbr %> with
  +Your TCP Domain
  +
  +After deployment, you must configure <%= vars.app_runtime_abbr %> with the domain
  +that you configured in the pre-deployment step above so developers can create
  +TCP routes from it.
   
   1. Run `cf router-groups`. You should see `default-tcp` as a response.
   
  -1. Run `cf create-shared-domain` to create a shared domain and associate it with the router group.
  +1. Run `cf create-shared-domain` to create a shared domain and associate it with
  +the router group.
     <pre class="terminal">
     $ cf create-shared-domain tcp.APPS-DOMAIN.com --router-group default-tcp
     </pre>
  
positive.code: 
  <%= vars.mutual_tls_tcp %>
  
  Before enabling TCP routing, you must set up networking requirements. To set up networking requirements:
  
  1. Choose a domain name from which your developers are to create TCP routes for their apps. For example, create a domain which is similar to your app domain but prefixed by the TCP subdomain: `tcp.APPS-DOMAIN.com`
  
  1. Configure DNS to resolve this domain name to the IP address of a highly-available load balancer that can forward traffic for the domain to the TCP routers. For more information, see the [Domains](../devguide/deploy-apps/routes-domains.html#domains) section of the _Configuring Routes and Domains_ topic. If you are operating an environment that does not require high availability, configure DNS to resolve the TCP domain name you have chosen directly to a single instance of the TCP router.
  
  1. (Optional) Choose IP addresses for the TCP routers and configure your load balancer to forward requests for the domain you chose in the step above to these addresses. Skip this step if you have configured DNS to resolve the TCP domain name to an instance of the TCP router.
  <%= vars.tcp_iaas %>
  
  1. (Optional) Decide on the number of TCP routes you want to support. For each TCP route, you must reserve a port. Configure your load balancer to forward the range of ports to the TCP routers. Skip this step if you have configured DNS to resolve the TCP domain name to an instance of the TCP router.
  
  1. <%= partial vars.tcp_port %>
  
  
negative.code: 
  #### <a id="configure-quota"></a> Configure a Quota for TCP Routes
  
  Since TCP route ports are a limited resource in some environments, quotas are
  configured to allow creation of zero TCP routes by default. After you deploy
  <%= vars.app_runtime_abbr %>, you can increase the maximum number of TCP routes
  for all orgs or for particular orgs and spaces. Because you reserve a route port
  for each TCP route, the quota for this resource is managed with the cf CLI
  command option `--reserved-route-ports`. For more information, see
  [Creating and Modifying Quota Plans](../adminguide/quota-plans.html).
  
  If you have a default quota that applies to all orgs, you can update it to
  configure the number of route ports that can be reserved by each org by running:
  
  ```
  cf update-quota QUOTA --reserved-route-ports X
  ```
  
  To create a new org quota that can be allocated to particular orgs, provide the
  following required quota attributes in addition to the number of reserved route
  ports by running:
  
  ```
  cf create-quota QUOTA --reserved-route-ports X
  ```
  
  You can also create a quota that governs the number of route ports that can be
  created in a particular space by running:
  
  ```
  cf create-space-quota QUOTA --reserved-route-ports X
  