anchor.diff:  1. [Parameterize the Manifest Environment Name](#parameterize)
   1. [Push the App](#push-app)
   
  -For additional information about extension buildpack configuration and creation commands see: 
  -[Creating a Custom Buildpack](http://engineering.pivotal.io/post/creating-a-custom-buildpack/) 
  -in the _Pivotal Engineering Journal_.
  -
  -<p class='note'><strong>Note:</strong> The Web Config Transform Extension Buildpack can inject settings 
  +<p class='note'><strong>Note:</strong> The Web Config Transform Extension Buildpack can inject appSettings and connectionStrings 
   regardless of whether the replacement tokens are present in Web.Release.Config file.
   </p>
   
  -## <a id='tokenize'></a> Identify Environment Dependent Configurations and Externalize
  +## <a id='tokenize'></a> Identify Environment-Dependent Configurations and Externalize
   
   To externalize your workload's environment dependent configurations settings, complete the following steps:  
   
   1. Backup your workload's `Web.config` and `Web.Release.config` files.  
  -1. Review the `Web.config` and `Web.Release.config` files, 
  +    <p class='note'><strong>Note:</strong> Web and WCF apps are created with "<i>debug</i>" and "<i>release</i>" versions of the web config transformation file 
  +        named <code>Web.Debug.config</code> and <code>Web.Release.config</code>. 
  +    When debugging on a developer machine, transform the <i>debug</i> file <code>Web.Debug.config</code> and use the <code>Debug</code> configuration profile.
  +    </p> 
  +1. Review your `Web.config` and any transform files, such as `Web.Release.config`, 
   identifying the environment-specific configuration settings.  
   <br>
       For example, the `connectionString` properties in the sample files below are environment-specific:  
  
positive.code: 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.
  
  To create a Web Config Transform Extension Buildpack, complete the following procedures:  
  
  1. [Identify Environment Dependent Configurations and Externalize](#tokenize)
  1. [Create a Parameterized Cloud Foundry App Manifest](#create-manifest)
  
negative.code:     </connectionStrings>
      ```
  
  
  
  1. To externalize your `Web.config` and `Web.Release.config` files, tokenize each of the files' 
  environment-specific properties using the format `#{configPath:key}`.  
  