anchor.diff:  
   These commands requires the Cloud Foundry Command Line Interface (cf CLI) v6.16 or later.
   
  -To use the Logging Route Service:
  -
  -1. Push the Logging Route Service as an app by running:
  +To use the logging route service:
  +
  +1. Push the logging route service as an app by running:
   
       ```
       cf push logger
       ```
   
  -1. Create a user-provided service instance, and include the route of the Logging Route Service you pushed as `route_service_url`. Be sure to use `https` for the scheme. Run:
  +1. Create a user-provided service instance, and include the route of the logging route service you pushed as `route_service_url`. Be sure to use `https` for the scheme. Run:
   
       ```
       cf create-user-provided-service mylogger -r https://logger.cf.example.com
  
positive.code: 
  ### <a name="fully-brokered"></a> Fully-Brokered Service
  
  In the fully-Brokered Service model, the <%= vars.app_runtime_abbr %> router receives all traffic to apps in the deployment before any processing by the route service. Developers can bind a route service to any app, and if an app is bound to a route service, the <%= vars.app_runtime_abbr %> router sends its traffic to the service. After the route service processes requests, it sends them back to the load balancer in front of the <%= vars.app_runtime_abbr %> router. The second time through, the <%= vars.app_runtime_abbr %> router recognizes that the route service has already handled them, and forwards them directly to app instances.
  
  ![Fully brokered](images/route-services-fully-brokered.png)
  
  
negative.code: 
  **Advantages:**
  
  - Developers can use a service broker to dynamically configure how the route service processes traffic to specific apps.
  - Traffic to apps that use the route service takes fewer network hops.
  
  **Disadvantages:**
  