anchor.diff:      cf push
       ```
   
  -## <a id='move-to-spring-cloud'></a> Move Config Settings to Spring Cloud Config Server 
  -
  -A multi-environment, production-ready configuration can be achieved using share and environment specific transforms and using Spring Cloud Config Server - backed by a git repository data source.
  +## <a id='move-to-spring-cloud'></a> Move Configuration Settings to Spring Cloud Config Server 
  +
  +A multi-environment, production-ready configuration can be achieved using Spring Cloud Config Server 
  +backed by environment-specific transforms anda git repository data source.
   
   1. Determine your manifest file's `ASPNETCORE_ENVIRONMENT` environment variable value.  
   1. Create a network accessible git repository for each application.  
  
positive.code:     </connectionStrings>
      ```
  
  1. Modify your transform file (ex: `Web.Release.config`) to  use tokenized configuration items in the following format `#{configPath:key}`.  
  <br>
      For example the `connectionString` properties below have been tokenized:  
  <br>
      **Web.Config**
  
  
negative.code:       - my_configserver
      ```
  
  ## <a id='push-app'></a> Push the App
  
  You can now push your app using your parameterized configuration.
  
  1. To push your app, run the following command:  
  
      ```script
      cf push --var env=CD-STEP
      ```
  <br>
      Where `CD-STEP` is the suffix used on your Web.config external settings YAML file's filename, such as `Development`, `QA`, `UAT`, or `Production`.  
  <br>
      For example:  
  
      ```script
      cf push --var env=Production
      ```
  
  1. To confirm your app runs using your WebConfig Transform, 
  review your logs for `WebConfig Transform Buildpack execution`:   
  
      ```
      ================================================================================
  