anchor.diff:  	Where:
   	* `APP-GUID` is the app GUID you recorded previously
   	* `ROUTE-GUID` is the route GUID you recorded previously
  -	* `WEIGHT` is an integer used to calculate the percentage of requests the app receives. You can enter a value from `1` to `128`. See [How Weights are Calculated](#calculation) above. 
  +	* `WEIGHT` is an integer used to calculate the percentage of requests the app receives. You can enter a value from `1` to `128`. See [How Weights are Used to Calculate Percentage of Requests](#calculation) above. 
   
   ### <a id="existing"></a> Update an Existing Route Mapping
   
  
positive.code: * 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 <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
  
negative.code: 	```
  	Where:
  	* `ROUTE_MAPPING_GUID` is the route mapping GUID you got from the previous step.
  	* `WEIGHT` is an integer used to calculate the percentage of requests the app receives. You can enter a value from `1` to `128`. See [How Weights are Used to Calculate Percentage of Requests](#calculation) above.  
  
  ## <a id="observe"></a> Confirm Routing Weights
  
  