anchor.diff:  
   ## <a id='create-manifest'></a> Create a Parameterized Cloud Foundry App Manifest 
   
  -A Cloud Foundry app manifest is required for the extension buildpack to perform token replacements during `cf push`.  
  +Cloud Foundry performs token replacements during `cf push` by using an extension buildpack. 
  +You must provide a Cloud Foundry app manifest for the extension buildpack to perform token 
  +replacements for your application.  
  +
  +Perform the following steps to test your tokenizations by using environment variables 
  +to perform token replacements from a Cloud Foundry App Manifest.  
  +
  +<p class='note'><strong>Note:</strong> Adding token replacements with Environment variables is only for experimental activities. 
  +    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  
   
  
positive.code: 
  ### <a id='modify-manifest'></a> Modify Your Cloud Foundry App Manifest  
  
  To modify your workload's Cloud Foundry app manifest to perform token 
  replacements during `cf push`, complete the following steps:  
  
  1. Review [web-config-transform-buildpack](https://github.com/cloudfoundry-community/web-config-transform-buildpack/releases">web-config-transform-buildpack) 
      in GitHub to determine the Web Config Transform Buildpack version to pull.  
  
  1. Open the manifest file in a text editor.
  
  1. Add a reference for your chosen Web Config Transform Buildpack buildpack version to the manifest file's `buildpacks` 
  property. 
  
      <p class='note'><strong>Note:</strong> Ensure the new entry precedes the existing 
        <code>hwc_buildpack</code> buildpacks entry. The <code>hwc_buildpack</code> entry is the step
  
negative.code:     <connectionStrings>
          <add name="MyDB" 
               connectionString="Data Source=LocalSQLServer;Initial Catalog=MyReleaseDB;User ID=serviceacc3;Password=PaKsAsEwWoOrOdT3" />
      </connectionStrings>
      ```
  
      **Web.Debug.config**
  
      ```xml
      <connectionStrings>
          <add name="TestDB" 
               connectionString="Data Source=ReleaseSQLServer;Initial Catalog=TestDB010;User ID=testaccount;Password=ABC123!" 
               xdt:Transform="SetAttributes" 
               xdt:Locator="Match(name)"/>
      </connectionStrings>
      ```
  
  