anchor.diff:      </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 Cloud Foundry app manifest is required for the extension buildpack to perform token replacements during `cf push`.  
  +
   ### <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:  
  +If the manifest file does not exist create it.  
  +<br>
  +    If your application is in Cloud Foundry, you can create the manifest file 
  +    by running the following command:  
   
       ```
       cf create-app-manifest APP-NAME
  
positive.code: 
      Where:  
      * `ACCOUNT-ID` is the is the github account ID.  
      * `CONFIG-REPO` is github configuration repository.  
  
  **Question: `CONFIG-REPO` is XXXXXX. **  
  
  1. Save the text file as a JSON file, for example `config-server.json`.  
  
  
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**
  
  