anchor.diff:      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.
  +1. Confirm your application is running by finding your app's URL in the push command output and navigating to it. 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.
  +The following features can be used with HWC buildpack:
  +<ul>
  +  <li>[Context Path Routing](#context-path)</li>
  +  <li>[Shadow Copy Setting](#shadow-copy)</li>
  +  <li>[Dynamic and Static HTTP Compression](#http-compression)</li>
  +  <li>[URL Rewrite](#url-rewrite)</li>
  +  <li>[Profile Scripts](#profile-scripts)</li>
  +</ul>
   
   ### <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.
  +Context path routing enables multiple applications to share the same route hostname, 
  +such as `app1.example.com/app2`. The context path routing feature is analogous to IIS virtual directories.
   
  -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`.
  +Making an application accessible under another app's URL requires a series of commands. 
  +To define a context path route, such as `app1.example.com/app2`, run the following commands:
   
  -Run the following commands to define context path routing that makes `app2` accessible under `app1`'s URL.
  -For example, `app1.example.com/app2`:
  +1. To push the primary app, run the following command:
  +
  +    ```
  +    cf push APP-NAME -s STEMCELL-NAME -b hwc_buildpack
  +    ```
  +1. To push the secondary app and disable the app's starting and default routing, run the following command:
  +
  +    ```
  +    cf push SECONDARY-APP --no-start --no-route -s STEMCELL-NAME -b hwc_buildpack
  +    ```
  +1. To map routes between the primary and secondary apps, run the following command:
  +
  +    ```
  +    cf map-route SECONDARY-APP DOMAIN --hostname APP-NAME --path SECONDARY-APP
  +    ```
  +1. To start the secondary app, run the following command:
  +
  +    ```
  +    cf start SECONDARY-APP
  +    ```
  +
  +    Where:  
  +      * `APP-NAME` is your primary app's name.  
  +      * `SECONDARY-APP` is your secondary app's name.  
  +      * `DOMAIN` is your site's public domain name. 
  +      * `STEMCELL-NAME` if the name of your stemcell.  
  +
  +For example, the following commands define context path routing for `app2` to be accessible under `app1`'s URL as `app1.example.com/app2`:
   
   <pre class='terminal'>
  -$ cf push app1 #find the URL for your app1
  -$ cf push app2 --no-start --no-route
  +$ cf push app1 -s windows2016 -b hwc_buildpack     #find the URL for your app1
  +$ cf push app2 --no-start --no-route -s windows2016 -b hwc_buildpack
   $ cf map-route app2 example.com --hostname app1 --path app2
   $ cf start app2
   </pre>
  +<br>
  +<p class="note"><strong>Note</strong>: HWC-hosted apps use the <code>VCAP_APPLICATION</code> 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 <code>applicationHost.config</code>.</p>
   
   ### <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
  +to the app's temporary files directory. This feature is turned off and
   unnecessary for apps running under Cloud Foundry. An app can override this
   setting in its `Web.config` file.
   
  
positive.code:   </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>Configure HWC
  
  HWC relies on a `Web.config` configuration file for configuring the .NET applications.
  
  Most `Web.config` files work out of the box with <%= vars.product_windows %>, with the following constraints:
  
  
negative.code: 
  ## <a id='help'></a>Buildpack Support
  
  A number of channels exist to assist you with using the HWC buildpack, or when developing your own HWC buildpack.
  
  * **HWC Buildpack Repository in GitHub**: Find more information about using and extending the HWC buildpack in the [HWC buildpack repository](https://github.com/cloudfoundry/hwc-buildpack) in GitHub.
  
  