anchor.diff:  3.  Environment variables in the appropriate pods that contain the credentials
   ////
   
  -The following sections outline a scenario for integrating with an external SaaS provider:
  +The following sections outline a scenario for integrating with an external SaaS
  +provider:
   
   . Create an OpenShift service to represent the external service. This is similar
   to creating an internal service; however the difference is in the service's
  
positive.code: `Selector` field.
  +
  Internal OpenShift services use the `Selector` field to associate pods with
  services via labels. A system component called `EndpointsController`
  synchronizes the endpoints for services that specify selectors with the pods
  that match the selector. The service proxy and OpenShift router load-balance
  requests to the service amongst the service's endpoints.
  +
  Services that represent an external resource do not require pods to be
  associated with an external service. For external services, leave the `Selector`
  field unset. This represents the external service, making the
  `EndpointsController` ignore the service and allows you to specify endpoints
  manually:
  +
  ====
  
  
negative.code: ====
  
  . Next, create endpoints for the service containing the information about where
  to send traffic directed to the service proxy and the router:
  +
  ====
  
  