anchor.diff:  	</tr>
   	<tr>
   		<td>App port</td>
  -		<td>The port on the container; this should match a port the app is configured to listen on</td>
  +		<td>The port on the container; this must match a port the app is configured to listen on</td>
   		<td>Diego Cell to app container</td>
   	</tr>
   </table>
   
  -The following diagram provides an example data path and Network Address Translation for TCP Routing. For HTTP Routing, the Route Port is always 80 or 443.  
  +The following diagram provides an example data path and Network Address Translation for TCP Routing. For HTTP Routing, the Route Port is always `80` or `443`.  
   
   ![Traffic-flow-diagram](route_ports.png)
   
  
positive.code: 	``` 
  	Where `APP-NAME` is the name of your app
  
  1. Configure CF with the ports your app is listening on:
  
  	```
  	cf curl /v2/apps/APP-GUID -X PUT -d '{"ports": [PORT1, PORT2, PORT3...]}'. 
  
negative.code: 
  Before following the procedure to configure routing to your app on custom ports, you must have the following:
  
  * An app pushed to <%= vars.product_short %> that can listen on one or more custom ports. 
  * Routes for which you want traffic forwarded to your app on custom ports. 
  	* If your app listens on two ports and you want clients to be able to send requests to both of them, create two routes. These can be from HTTP or TCP domains (see [Routes and Domains](./deploy-apps/routes-domains.html) for more info). Consider an example in which you have two routes: `foo.example.com` and `bar.example.com`. In the following procedure, you use API endpoints to map these routes to your app on the ports it is listening.
  
  ## <a id="procedure"></a> Procedure
  
  