anchor.diff:  * Linux, Windows or MacOS development machine or VM.
   * A foundation with Windows cells available to push to.
   
  -
   ## <a id='overview'></a> Overview
   
  -To run legacy ASP.Net applications configuration settings are typically injected through Web.config files. 
  -As per cloud-native principles, an app's build artifacts should not include configuration settings.  
  +Typical applications use environment-specific appSettings and connectionStrings to connect to external data repositories. 
  +Typically, legacy Web and WCF application settings are injected through a `Web.config` file.  
  +
  +As per cloud-native principles, an application's build artifacts should not include configuration settings, 
  +so an external process must inject environment-specific settings into a cloud application.  
   
   The Web Config Transform Extension Buildpack injects environment-specific appSettings and connectionString values 
  -into legacy ASP.Net app containers by performing token replacements during `cf push` staging.
  +into legacy Web and WCF application containers by performing token replacements during `cf push` staging.  
  +
  +Web and WCF applications are created with `Web.Debug.config` and `Web.Release.config` files as the 
  +"_debug_" and "_release_" transform versions of their `Web.config` file. 
  +You must externalize and parameterize your `Web.Debug.config` and `Web.Release.config`  
  +environment-specific configurations for deployment to the cloud.  
   
   To leverage the Web Config Transform Extension Buildpack, complete the following procedures:  
   
  
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:     Where:  
      * `APP-NAME` is your app's name.  
      * `VERSION` is the buildpack version.   
      * `SETTING-NAME` is the name of a configuration setting used by your app. 
      * `SETTING-VALUE` is the development value of the setting. 
  
      For example:
  
  