anchor.diff:  <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.
  +* 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
  +defined by the `$PORT` environment variable, which is `8080` on Diego. For 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
  
positive.code: </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.
  
  <pre class="terminal">
  $ cf push tcp-app -d <%= vars.tcp_app_domain %> --random-route
  
negative.code:   OK
    </pre>
  
  The developer can then map the new routes to different apps by following the procedure in [Map a Route to Your App](#map-route) below.
  
  If the developer maps the first route with path `products` to the `products` app, the second route with path `orders` to the `orders` app, and the last route
  to the `storefront` app. After this:
  
  * <%= vars.app_runtime_abbr %> routes requests to `http://store.<%= vars.app_domain %>/products` to the `products` app.
  
  * <%= vars.app_runtime_abbr %> routes requests to `http://store.<%= vars.app_domain %>/orders` to the `orders` app.
  
  * <%= vars.app_runtime_abbr %> routes requests to `http://store.<%= vars.app_domain %>` to the `storefront` app.
  
  <%= vars.app_runtime_abbr %> attempts to match routes with a path first, and then attempts to match host and domain.
  