anchor.diff:  
   <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
  +====
  +
  +=== External Database Environment Variables
  +
  +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'
  +environment variables with the credentials described above. In our example, The 'helloworld'
   container will receive the following environment variables:
   
  -----
  -EXTERNAL_MYSQL_SERVICE_SERVICE_HOST=10.0.0.11 <1>
  -EXTERNAL_MYSQL_SERVICE_SERVICE_PORT=3306
  -MYSQL_USERNAME=<value of MySQL username>
  -MYSQL_PASSPHRASE=<value of MySQL passphrase>
  -MYSQL_DATABASE_NAME=<value of MySQL database name>
  -----
  -
  -<1> Example value only; actual IP will vary
  +* `EXTERNAL_MYSQL_SERVICE_SERVICE_HOST`=[replaceable]#<IP_Address>#
  +* `EXTERNAL_MYSQL_SERVICE_SERVICE_PORT`=[replaceable]#<Port_Number>#
  +* `MYSQL_USERNAME`=[replaceable]#<MySQL_username>#
  +* `MYSQL_PASSPHRASE`=[replaceable]#<MySQL_passphrase>#
  +* `MYSQL_DATABASE_NAME`=[replaceable]#<MySQL_database>#
   
   The application is responsible for reading the coordinates and credentials for the service from the
   environment and establishing a connection with the database via the service.
   
   
  -== Example: External SaaS Provider
  -
  -One of the most common types of external services is an external SaaS endpoint. As an example,
  -assume that you want to use a SaaS provider for an application. This requires:
  +== External SaaS Provider
  +
  +One of the most common types of external services is an external SaaS endpoint. To support an external SaaS provider, an application needs:
   
   1. An endpoint to communicate with
   2. A set of credentials, such as:
  
positive.code: }
  ----
  
  <1> The name must match the name of the `Service` instance
  <2> Traffic to the service will be load-balanced between the supplied `Endpoints` if more than one
      is supplied
  
  === Consuming credentials in pods
  
  Now that the service and endpoints are defined, we need to give pods the credentials to use the
  service.  This is done by setting environment variables in the appropriate containers.  In this
  example, the container will receive the following environment variables with credentials for the
  service:
  
  1.  `MYSQL_USERNAME`: Holds the username to use with the service
  2.  `MYSQL_PASSPHRASE`: Holds the passphrase to use with the service
  3.  `MYSQL_DATABASE_NAME`: Holds the database name to use
  
  ----
  {
  
negative.code: 
  ====
  
  === External SaaS Provider Environment Variables
  
  Using an external service in your application is just like using an internal service. Your application is
  injected with environment variables for the service and the additional environment variables with the credentials
  described above. In the following example, the 'helloworld' container receives the following environment variables:
  
  
  * `EXAMPLE_EXTERNAL_SERVICE_SERVICE_HOST`=[replaceable]#<IP_Address>#
  * `EXAMPLE_EXTERNAL_SERVICE_SERVICE_PORT`=[replaceable]#<Port_Number>#
  * `SAAS_API_KEY`=[replaceable]#<value of SaaS api key>#
  * `SAAS_USERNAME`=[replaceable]#<value of SaaS username>#
  * `SAAS_PASSPHRASE`=[replaceable]#<value of SaaS passphrase>#
  
  The application is responsible for reading the coordinates and credentials for the service from the environment
  and establishing a connection with the service.