anchor.diff:  </pre>
   
   To map a TCP route during `push`, specify a TCP domain and request a random port using `--random-route`. To specify a port, push the app without a route, then
  -create and map the route manually by following the steps in [Create a TCP Route with a Port](#create-route-with-port) above.
  +create and map the route manually by following the procedure in [Create a TCP Route with a Port](#create-route-with-port) above.
   
   <pre class="terminal">
   $ cf push tcp-app -d <%= vars.tcp_app_domain %> --random-route
  
positive.code: <p class='note'><strong>Note:</strong> Developers can use the Cloud Controller API to update the ports an app can receive requests on. For more information,
    see <a href="../custom-ports.html">Configuring Apps to Listen on Custom Ports (Beta)</a>.</p>
  
  * Requests to HTTP routes must be sent to ports 80 or 443.
  * Ports cannot be reserved for HTTP routes.
  
  TCP routes include a domain and a route port. A route port is the port clients make requests to. This is not the same port as what an app pushed to Cloud
  Foundry listens on. `tcp.shared-domain.example.com:60000` is an example of a TCP route. Just as for HTTP routes, apps should listen to the `localhost` port
  defined by the `$PORT` environment variable, which is `8080` on Diego. As an example, requests to `tcp.shared-domain.example.com:60000` would be routed to the
  app container at `localhost:8080`.
  
  * Once a port is reserved for a route, it cannot be reserved for another route.
  * Hostname and path are not supported for TCP routes.
  
  ### <a id='internal-routes'></a> Internal Container-to-Container Routes
  
negative.code: If DNS has been configured correctly, this command instructs <%= vars.app_runtime_abbr %> to route requests to apps mapped to this route from these URLs:
  
  * `http://<%= vars.private_app_domain %>`
  
  * `https://<%= vars.private_app_domain %>`
  
  * Any path under either of the above URLs, such as `http://<%= vars.private_app_domain %>/foo`
  
  If there are no other routes for the domain, requests to any subdomain, such as `http://foo.<%= vars.private_app_domain %>`, fail.
  