anchor.diff:  }
   ----
   
  -<1> The service spec must have no `selector` field
  +<1> The `selector` field to leave blank.
  +
  +====
   
   === Setting the endpoints
   
  -The next step is to create endpoints for the service.  This will give the service proxy and router
  -information about where to send traffic going to the service.
  +The next step is to create endpoints for the service. This gives information about where to send traffic going to the
  +service to the service proxy and router.
  +
  +====
   
   ----
   {
  
positive.code: }
  ----
  
  <1> Other fields on the `DeploymentConfig` are omitted
  
  === Using the service in your application
  
  Using an external service in your application is just like using an internal service.  Your
  application will be injected with environment variables for the service and the additional
  environment variables with the credentials described above.  In our example, The 'helloworld'
  container will receive the following environment variables:
  
  ----
  EXAMPLE_EXTERNAL_SERVICE_SERVICE_HOST=10.0.0.11 <1>
  EXAMPLE_EXTERNAL_SERVICE_SERVICE_PORT=1234
  SAAS_API_KEY=<value of SaaS api key>
  SAAS_USERNAME=<value of SaaS username>
  SAAS_PASSPHRASE=<value of SaaS passphrase>
  ----
  
  <1> Example value only; actual IP will vary
  
  The application is responsible for reading the coordinates and credentials for the service from the
  environment and establishing a connection with the service.
  
negative.code: }
  ----
  
  ====
  
  <1> The name of the `Service` instance.
  <2> Traffic to the service is load-balanced between the `Endpoints` supplied here.
  
  === Consuming credentials in pods
  
  Now that the service and endpoints are defined, give pods the credentials to use the service. This is done
  by setting environment variables in the appropriate containers. 
  
  ====
  
  ----
  {
  