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: 
  1. Click the <%= vars.app_runtime_abbr %> tile.
  
  1. Select the **Networking** side-tab.
  
  1. Under **TCP routing**, select **Disable**.
  
  1. Run `cf delete-domain DOMAIN` on a command line to remove the TCP routing
  domain, where DOMAIN is the name of your TCP routing domain.
  
  <% end %>
  
  ## <a id="administering-tcp-routing"></a> Further TCP Routing Administration
  
  ### <a id="create-tcp-route"></a> Create a TCP Route
  
  For information about creating a TCP Route, see the
  [Create a TCP Route with a Port](../devguide/deploy-apps/routes-domains.html#create-route-with-port)
  section of the _Configuring Routes and Domains_ topic.
  
  ### <a id="modify-ports"></a> Router Groups: Modify TCP port reservations
  
  After deployment, you can modify the range of ports available for TCP routes
  using `cf curl` commands, as demonstrated with the commands below. These commands
  require an admin user with the `routing.router_groups.read` and
  `routing.router_groups.write` scopes.
  
  1. In a terminal window, run `cf curl /routing/v1/router_groups` to view the
  `reservable_ports`:
    <pre class="terminal">
    $ cf curl /routing/v1/router\_groups
      [
  