anchor.diff:    </tr>
   </table>
   
  -Before you push your first app using the HWC buildpack, see the [Getting Started](https://dotnet-cookbook.cfapps.io/intro/getting_started/) guide in the <em>.NET Cookbook</em>.
  +## <a id='hwc'></a> Step 1. Configure HWC
   
  -## <a id='hwc'></a>Configure HWC
  -
  -HWC relies on a `Web.config` configuration file for configuring the .NET applications.
  +HWC relies on `Web.config` and `applicationHost.config` configuration files for configuring the .NET applications.
   
   Most `Web.config` files work out of the box with <%= vars.product_windows %>, with the following constraints:
   
  
positive.code:     urls: my-app.example.com
      </pre>
  
  1. Find the URL of your app in the output from the push command and navigate to it to see your HWC app running. In the example above, `my-app.example.com` is the URL of your app.
  
  ## <a id='features'></a> Features
  
  Below are a set of features that can be used with HWC buildpack.
  
  ### <a id='context-path'></a> Context Path Routing
  
  Context path routing is a feature analogous to IIS virtual directories.
  It enables multiple applications to share the same route hostname.
  
  HWC-hosted apps use the `VCAP_APPLICATION` environment variable
  to read out the bound app URIs. Any context path that exists underneath the root in the
  app's bound route corresponds to the `applicationHost.config`.
  
  Run the following commands to define context path routing that makes `app2` accessible under `app1`'s URL.
  For example, `app1.example.com/app2`:
  
  <pre class='terminal'>
  $ cf push app1 #find the URL for your app1
  $ cf push app2 --no-start --no-route
  $ cf map-route app2 example.com --hostname app1 --path app2
  $ cf start app2
  </pre>
  
  ### <a id='shadow-copy'></a> Shadow Copy Setting
  [Shadow Copy](https://msdn.microsoft.com/en-us/library/ms228159(v=vs.100).aspx)
  is a hosting option that copies assemblies for an app in the `bin` directory
  to the app's temporary files directory. This features is turned off and
  unnecessary for apps running under Cloud Foundry. An app can override this
  setting in its `Web.config` file.
  
  
negative.code: - SQL server connection strings must use fully qualified domain names.
  - Place connection string values in environment variables or [user-provided service instances](../../devguide/services/user-provided.html).
  
  Additionally, [Shadow Copy Setting](#shadow-copy), and [Dynamic and Static HTTP Compression](#http-compression) `Web.config` settings can be customized as needed.
  
  The HWC buildpack includes a default configuration for the `applicationHost.config`, similar to IIS.
  
  ## <a id="error-handling"></a> Step 2. Add a Global Error Handler
  
  Before you push your app for the first time, add a global error handler to receive log information from your app if it crashes on startup.
  
  To configure a global error handler that logs to `stdout`, see [Application Error Handling](https://dotnet-cookbook.cfapps.io/intro/getting_started/#application-error-handling) in the <em>.NET Cookbook</em>.
  
  ## <a id='push-your-app'></a> Step 3. Push an App
  
  Follow the steps below to push your application.
  
  1. Build your HWC app in Visual Studio.
  
  1. On the command line, navigate to the directory that contains the app files.
  
  1. To push your HWC app, run the following `cf push` command:
  
      ```
      cf push APP-NAME -s STEMCELL-NAME -b hwc_buildpack
      ```
  
      Where:  
        * `APP-NAME` is the name you want to give your app.  
        * `STEMCELL-NAME` if the name of your stemcell.  
    
      
      For example:
  
      <pre class='terminal'>
      $ cf push my-app -s windows2016 -b hwc_buildpack
  