anchor.diff:  
   <strong><%= modified_date %></strong>
   
  -This documentation is intended for service authors who are interested in offering a service to a Cloud Foundry services marketplace. Developers interested in consuming these services can read the  [Manage Application Requests with Route Services](../devguide/services/route-binding.html) topic.
  +This documentation is intended for service authors who are interested in 
  +offering a service to a Cloud Foundry (CF) services marketplace. Developers 
  +interested in consuming these services can read the [Manage Application Requests with Route Services](../devguide/services/route-binding.html) topic.
   
   <%= vars.route_services %>
   
   ## <a id='introduction'></a>Introduction ##
   
  -Cloud Foundry application developers may wish to apply transformation or processing to requests before they reach an application. Common examples of use cases are authentication, rate limiting, and caching services. Route Services are a new kind of Marketplace Service that developers can use to apply various transformations to application requests by binding an application's route to a service instance. Through integrations with service brokers and optionally with the Cloud Foundry routing tier, providers can offer these services to developers with a familiar automated, self-service, and on-demand user experience.
  +Cloud Foundry application developers may wish to apply transformation or 
  +processing to requests before they reach an application. Common examples of use 
  +cases include authentication, rate limiting, and caching services. Route 
  +Services are a kind of Marketplace Service that developers can use to apply 
  +various transformations to application requests by binding an application's 
  +route to a service instance. Through integrations with service brokers and,  
  +optionally, with the Cloud Foundry routing tier, providers can offer these 
  +services to developers with a familiar, automated, self-service, and on-demand 
  +user experience.
   
   <%= vars.route_services_appsman1 %>
   
   ## <a id='architecture'></a>Architecture ##
   
  -Cloud Foundry supports three models for Route Services: fully-brokered services; static, brokered services; and user-provided services. In each case, you configure a route service to process traffic addressed to an app.
  +Cloud Foundry supports the following three models for Route Services: 
  +
  +* [Fully-brokered services](#fully-brokered)
  +* [Static, brokered services](#static-brokered)
  +* [User-provided services](#user-provided)
  +
  +In each model, you configure a route service to process traffic addressed to an 
  +app.
   
   ### <a id="fully-brokered"></a>Fully-Brokered Service ###
   
  -In this model, the CF 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 CF 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 CF router. The second time through, the CF router recognizes that the route service has already handled them, and forwards them directly to app instances.
  +In the fully-Brokered Service model, the CF 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 
  +CF 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 CF router. 
  +The second time through, the CF 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)
   
  -The route service can run inside or outside of CF, so long as it fulfills the [Service Instance Responsibilities](#service-instance-responsibilities) to integrate it with the CF router. A service broker publishes the route service to the CF marketplace, making it available to developers. Developers can then create an instance of the service and bind it to their apps with the following commands:
  -
  -`cf create-service BROKER_SERVICE_PLAN SERVICE_INSTANCE`
  -`cf bind-route-service YOUR_APP_DOMAIN SERVICE_INSTANCE [--hostname HOSTNAME]`
  -
  -Developers configure the service either through the service provider's web interface or by passing [arbitrary parameters](../devguide/services/managing-services.html#arbitrary-params-create) to their `cf create-service` call, through the `-c` flag.
  +The route service can run inside or outside of CF, so long as it fulfills the 
  +[Service Instance Responsibilities](#service-instance-responsibilities) to 
  +integrate it with the CF router. A service broker publishes the route service 
  +to the CF marketplace, making it available to developers. Developers can then 
  +create an instance of the service and bind it to their apps with the following 
  +commands:
  +
  +`cf create-service BROKER-SERVICE-PLAN SERVICE-INSTANCE`
  +`cf bind-route-service YOUR-APP-DOMAIN SERVICE-INSTANCE [--hostname HOSTNAME]`
  +
  +Developers configure the service either through the service provider's web 
  +interface or by passing [arbitrary parameters](../devguide/services/managing-services.html#arbitrary-params-create)
  + to their `cf create-service` call through the `-c` flag.
   
   **Advantages:**
   
   - Developers can use a Service Broker to dynamically configure how the route service processes traffic to specific applications.
   - Adding route services requires no manual infrastructure configuration.
  -- Traffic to apps that do not use the service makes fewer network hops; requests for those apps do not pass through the route service.
  +- Traffic to apps that do not use the service makes fewer network hops because requests for those apps do not pass through the route service.
   
   **Disadvantages:**
   
  
positive.code: 
  #### <a id='how-it-works'></a>How It Works ####
  
  Binding a service instance to a route will associate the `route_service_url` with the route in the Cloud Foundry router. All requests for the route will be proxied to the URL specified by `route_service_url`.
  
  Once a route service completes its function, it is expected to forward the request to the route the original request was sent to. The Cloud Foundry router will include a header that provides the address of the route, as well as two headers that are used by the route itself to validate the request sent by the route service.
  
  #### <a id='headers'></a>Headers ####
  The `X-CF-Forwarded-Url` header contains the URL of the application route. The route service should forward the request to this URL.
  
negative.code:     $ cf logs logger
      </pre>
  
  1. Send a request to the sample app and view in the route service logs that the request is forwarded to it.
  
      <pre class="terminal">
      $ curl spring-music.cf.example.com
  