anchor.diff:         MyDB: "Data Source=prodserver;Initial Catalog=mydb;User ID=serviceacc3;Password=PaKsAsEwWoOrOdT3"
       ```    
   
  -
  -## <a id='create-spring-cloud-service'></a> Create a Configuration Service for Spring Cloud Config Server
  -
  -The Web Config Transform Extension Buildpack requires a configuration file pointing to your GitHub repository. 
  -To provide this, create a JSON file pointing to your GitHub repository and start a config server service.
  -
  -1. To confirm you have either `p.config-server` or `p-config-server` config servers available 
  -in your CF Marketplace, run the following command:  
  +### <a id='copy-to-git'></a> Move Your Configurations to a Spring Cloud Config Server GitHub Repository
  +
  +Your Spring Cloud Config Server must be backed by transforms stored in a git repository data source.  
  +
  +To move your transformations to a git repository, complete the following steps:  
  +
  +1. Create a network accessible git repository specifically for storing this application's transform configuration files.  
  +
  +1. Copy the configuration files created in [Create Configurations for Spring Cloud Config Server](#create-for-spring-cloud), above to the new git repository.  
  +
  +
  +### <a id='create-spring-cloud-service'></a> Create a Configuration Service for Spring Cloud Config Server
  +
  +The Web Config Transform Extension Buildpack requires a configuration file pointing to your transform configurations 
  +GitHub repository.  
  +
  +1. To confirm the name of the config servers available in your CF Marketplace, run the following command:  
   
       ```
       cf marketplace
       ```
   
  -1. Create a text file for configuration server setup using the following format:  
  +    Review the return and determine whether you have either `p.config-server` or `p-config-server`.  
  +
  +1. Create a text file for configuration server settings with the following content:  
   
       ```json
       {
  
positive.code:     The manifest should contain configuration item keys and values for testing purposes only. 
      Configuration settings should be externalized using git repositories and Spring Cloud Config Server.  
      For more information about externalizing configuration settings in Spring Cloud Config Server, 
      see <a href="#move-to-spring-cloud">Move Configuration Settings to Spring Cloud Config Server</a>, below.
  </p>
  
  ### <a id='create-manifest'></a> Create a Cloud Foundry App Manifest  
  
negative.code:     cf push
      ```
  
  ## <a id='move-to-spring-cloud'></a> Establish a Spring Cloud Config Server 
  
  You must store your environment-specific transformations in a secured environment for your deployment to be production-ready.  
  
  A multi-environment, production-ready deployment configuration can be achieved by using Spring Cloud Config Server 
  backed by transforms stored in a git repository data source.
  
  ### <a id='create-for-spring-cloud'></a> Create Configurations for Spring Cloud Config Server
  
  To create transformations for use by Spring Cloud Config Server, complete the following steps:   
  
  1. Determine the name you are using for your environment. For example you could be creating a "Development", "Debug" or "Production" manifest.
      <p class='note'><strong>Note:</strong> You will use this name for both the file you create in this task as well as
      in your manifest file's <code>ASPNETCORE_ENVIRONMENT</code> environment variable value.
      </p>
  
  1. Create a YAML file to hold your common settings across all environments. 
  Name the file `YOUR-APPLICATION`.yaml.  
  <br>
      Where `YOUR-APPLICATION` is the identifier name for your application.  
  <br>
  