anchor.diff:  - 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>Add a Global Error Handler
  +## <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.
  -Without a global error handler, you will not receive any log information from your app if it crashes on startup.
  +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> Push an App
  +## <a id='push-your-app'></a> Step 3. Push an App
   
   Follow the steps below to push your application.
   
  -1. Build your app in Visual Studio. On the command line, navigate to the directory that contains the app files.
  +1. Build your HWC app in Visual Studio.
   
  -1. Run `cf push APP-NAME -s windows2016 -b hwc_buildpack` to push your app, where `APP-NAME` is the name you want to give your app. For example:
  +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
  
positive.code: The HWC buildpack provides a runtime server that uses the Hosted Web Core API for running .NET Framework applications in Windows Server containers. For more information, see [Hosted Web Core API Reference](https://msdn.microsoft.com/en-us/library/ms693832(v=vs.90).aspx) in the Microsoft documentation.
  
  The HWC buildpack provides access to .NET Framework 4.5.1 and later, made available by the Windows root file system (rootfs).
  Using the HWC buildpack requires deploying Windows cells with <%= vars.product_windows %>. 
  
  The HWC buildpack supports the following common app types by default:
  
  * ASP.NET MVC
  * ASP.NET Web Forms
  * ASP.NET WebAPI Apps
  * Windows Communication Foundation (WCF)
  
  For information about deploying different types of .NET apps, follow the links in the table below.
  
  
negative.code:   </tr>
  </table>
  
  ## <a id='hwc'></a> Step 1. Configure HWC
  
  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:
  
  