anchor.diff:  	</tr>
   	<tr>
   		<td>app-a</td>
  -		<td>1</td>
  -		<td>1/(1+3)</td>
  -		<td>25%</td>
  +		<td><code>1</code></td>
  +		<td><code>1</code>/(<code>1</code>+<code>3</code>)</td>
  +		<td><code>25%</code></td>
   	</tr>
   	<tr>
   		<td>app-b</td>
  -		<td>3</td>
  -		<td>3/(1+3)</td>
  -		<td>75%</td>
  +		<td><code>3</code></td>
  +		<td><code>3</code>/(<code>1</code>+<code>3</code>)</td>
  +		<td><code>75%</code></td>
   	</tr>
   </table>
   
  -In this example, you can also unmap the route from one of the apps and observe 100% of the requests going to just one app, which simulates a migration.
  +In this example, you can also unmap the route from one of the apps and observe <code>100%</code> of the requests going to just one app, which simulates a migration.
   
   ### <a id="considerations"></a> Considerations for Working with Routing Weights
   
   Consider the following when working with routing weights:
   
  -* The default weight is 1. This means that if multiple apps are mapped to the same route and their weights are not updated, traffic is equally distributed between them.  
  +* The default weight is <code>1</code>. This means that if multiple apps are mapped to the same route and their weights are not updated, traffic is equally distributed between them.  
   * The percentage of requests described above is not applied exactly, but over time the requests reflect the percentage.
  -* You cannot set a weight to 0. You can stop weighting traffic by deleting apps or unmapping apps from the route. 
  -* You cannot exceed 100 routes mappings for a particular route. This could result in some apps not receiving any requests.
  +* You cannot set a weight to <code>0</code>. You can stop weighting traffic by deleting apps or unmapping apps from the route. 
  +* You cannot exceed <code>100</code> routes mappings for a particular route. This could result in some apps not receiving any requests.
   
   
   ## <a id="procedure"></a> Configure Routing Weights
   
  -<p class="note"><strong>Note</strong>: This feature does not yet have cf CLI integration. The steps for updating a routing weight require you to curl the Cloud Controller v3 API.</p>
  +<p class="note"><strong>Note</strong>: This feature does not yet have cf CLI integration. The steps for updating a routing weight require you to <code>curl</code> the Cloud Controller v3 API.</p>
   
   You can configure routing weights when creating or updating a route mapping, Follow the procedure below that corresponds to your use case. 
   
  
positive.code: 
  <% end %>
  
  1. Get the GUID of your route:
  
  	```
  	cf curl /v2/routes?q=host:HOSTNAME
  	```
  	Where `HOSTNAME` is the hostname you specified when creating the route.
  
  1. Get the GUID of the app that you want to map the route to:
  
  	```
  	cf app APP-NAME --guid
  
negative.code: 
  To update an existing route mapping with a new weight, do the following:
  
  1. Run the following command and record the GUID of the app:
  
  	```
  	cf app APP-NAME --guid
  	```
  
  
  1. Run the following command and record the GUID of the route:
  	
  	```
  	cf curl /v2/routes?q=host:HOSTNAME
  