anchor.diff:      usage: 1GB x 1 instances
       urls: my-app.example.com
       </pre>
  +<br>
  +    If your <%= vars.product_windows %> deployment does not have the .NET Core buildpack installed or the installed version is out of date, 
  +    run the push command with the `-b` option to specify buildpack:
  +
  +    ```
  +    cf push APP-NAME -b https://github.com/cloudfoundry/dotnet-core-buildpack.git
  +    ```
  +
  +    Where `APP-NAME` is the name you want to give your app.  
   
   1. Find the URL of your app in the push command output. In the example above, `my-app.example.com` is the URL of the app. 
  -Open a browser and navigate to the URL to see your app running.  
  +1. Open a browser and navigate to the URL to see your app running.  
   
   For a basic example app, see [ASP.NET Core getting started app](https://github.com/IBM-Bluemix/aspnet-core-helloworld) in GitHub.
   
   ## <a id='source-based'></a>Source-Based, Non-Published Deployments
   
  -When using this workflow, you push the source code for your app to Cloud Foundry by running the `cf push` command.
  -Note that for a source-based, non-published deployment, you push the source code for your app, not the output directory of the `dotnet publish` command.
  +For a source-based, non-published deployment, you push your app's source code, not the output directory of the `dotnet publish` command. 
   
   The source-based, non-published workflow ensures the buildpack can keep all your dependencies in sync and up to date.
   For additional information about using source-based, non-published deployments, see the following sections:
  
positive.code: 1. `*.fsproj`
  
  <p class="note"><strong>Note</strong>: The app respects the SDK version specified in <code>global.json</code> at runtime.
  If you provide versions in the <code>global.json</code> and <code>buildpack.yml</code> files,
  ensure that you specify the same versions in both files.</p>
  
  ## <a id='dotnet-runtime'></a>Specify .NET Runtime Versions
  
  
negative.code: 1. Save your changes.
  
  With these changes, the `dotnet run` command copies your app `Views` to the build output where the .NET CLI can find them.
  
  ## <a id='custom-libraries'></a>Add Custom Libraries
  
  