anchor.diff:      * `SERVER-NAME` is the name for your config server.  
       * `CONFIG-FILE` is the filename of your server config json file.  
   
  -## <a id='create-spring-cloud-service'></a> Bind Config Service to App Using Manifest
  +## <a id='create-spring-cloud-service'></a> Bind the Config Service to Your App Using Your Manifest
   
   The newly created config server must be bound to your app to be used by the app.
   
  
positive.code:     - name: sampleapp
        stack: windows
        buildpacks:
        - https://github.com/cloudfoundry-community/web-config-transform-buildpack/releases/download/VERSION/web-config-transform-buildpack-VERSION.zip
        - hwc_buildpack
        env:
          "connectionStrings:MyDB": "Data Source=ReleaseSQLServer;Initial Catalog=MyReleaseDB;User ID=ACCOUNT-ID;Password=PASSWORD"
      ```
  
      <p class='note'><strong>Note:</strong> Adding token replacements with Environment variables is only for experimental activities. 
      Only put configuration item keys and values in the manifest for testing purposes.	
      Config settings should be externalized using git repositories and Spring Cloud Config Server. 
      Spring Cloud Config Server should be used for externalizing configuration settings. 
      For more information about externalizing configuration settings in Spring Cloud Config Server, see <a href="#move-to-spring-cloud">Move Config Settings to Spring Cloud Config Server</a>, below.
      </p>
  
  ## <a id='add-transforms'></a> Push the App
  
  1. Build and push the app to Cloud Foundry to verify that your config settings are properly transformed by running the following command:   
  
  
negative.code:     cf marketplace
      ```
  
  1. Create a text file for config server setup using the following format:  
  
      ```json
      {
  