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:     </configuration>
      ```
  
      <p class='note'><strong>Note:</strong> Web and WCF apps are created with <strong>Debug</strong> and <strong>Release</strong> configurations 
      of the <code>Web.Debug.config</code>, and <code>Web.Release.config</code> web config transformation files. 
      When debugging on a developer machine, transform the <code>Debug</code> <code>Web.Debug.config</code> file and use the <code>Debug</code> configuration profile.
      </p>
  
      <p class='note'><strong>Note:</strong> Transform xml attributes and tokens are case-sensitive.</p>
  
  ## <a id='create-manifest'></a> Create a Parameterized Cloud Foundry App Manifest 
  
  ### <a id='create-manifest'></a> Create a Cloud Foundry App Manifest  
  
  To create a Cloud Foundry app manifest for your workload, complete the following steps:  
  
  1. Ensure your application has a Cloud Foundry manifest file. 
  If it does not and your application is in Cloud Foundry, create the manifest by running the following command:  
  
      ```
      cf create-app-manifest APP-NAME
  
negative.code:     </connectionStrings>
      ```
  
      <p class='note'><strong>Note:</strong> Web and WCF apps are created with <strong>Debug</strong> and <strong>Release</strong> configurations 
      of the <code>Web.Debug.config</code>, and <code>Web.Release.config</code> web config transformation files. 
      When debugging on a developer machine, transform the <code>Debug</code> <code>Web.Debug.config</code> file and use the <code>Debug</code> configuration profile.
      </p>
  
  1. The environment-specific properties must be externalized by tokenizing each configuration setting 
  using the format `#{configPath:key}`. The following are examples of tokenized  
  `Web.config` and `Web.Release.config` files:  
  <br>
      **Web.Config**
  
  