anchor.diff:  Specify any non-default package sources in the `NuGet.Config` file.
   
   For a basic example, see this [Hello World sample](https://github.com/IBM-Bluemix/aspnet-core-helloworld).
  -4
  +
   ## <a id='cli_tools'></a> .NET Core SDKs ##
   
  -The first several releases of the .NET Core SDKs used `project.json` files for project build configuration. However, the current release of the .NET Core SDK uses MSBuild as its build tool, which uses `*.csproj` and `*.fsproj` files for configuration.
  +The first several releases of the .NET Core SDKs used `project.json` files for project build configuration. The current release of the .NET Core SDK uses MSBuild as its build tool, which uses `*.csproj` and `*.fsproj` files for configuration.
   
  -Currently, the .NET Core buildpack includes both types of SDKs. If the pushed app contains a `global.json` file, the buildpack will install the version specfied by that file. Otherwise, the buildpack will choose the SDK to install as follows:
  +Currently, the .NET Core buildpack includes both types of SDKs. If the pushed app contains a `global.json` file, the buildpack installs the version specified by that file. Otherwise, the buildpack chooses which SDK to install as follows:
   
  -1. If the app only contains `project.json` files, install the latest SDK that supports this configuration.
  -2. If the app only contains `*.csproj` and `*.fsproj` files, install the latest SDK that uses MSBuild.
  -3. If the app contains both file types without a `global.json`, the buildpack will throw an error as it cannot determine the proper SDK to install.
  +1. If the app only contains `project.json` files, the buildpack installs the latest SDK that supports this configuration.
  +2. If the app only contains `*.csproj` and `*.fsproj` files, the buildpack installs the latest SDK that uses MSBuild.
  +3. If the app contains both file types without a `global.json`, the buildpack throws an error, as it cannot determine the proper SDK to install.
   
  -<p class="note">
  -  <strong>Note</strong>: Microsoft has removed support for project.json from the <a href="https://blogs.msdn.microsoft.com/dotnet/2016/11/16/announcing-net-core-tools-msbuild-alpha/">.NET Core SDK tools.</a>. As such, support for project.json apps in the buildpack will soon be deprecated.
  +<p class="note"><strong>Note</strong>: Microsoft has removed support for project.json from the <a href="https://blogs.msdn.microsoft.com/dotnet/2016/11/16/announcing-net-core-tools-msbuild-alpha/">.NET Core SDK tools</a>. Consequently, support for <code>project.json</code> apps in the buildpack will soon be deprecated.
   </p>
  -
  -
   
   ## <a id='port'></a>Configure the Listen Port ##
   
  -For your .NET Core app to work on Cloud Foundry, you must modify the `Main` method to make the app listen on the port specified by the `$PORT` environment variable, which Cloud Foundry sets automatically.
  +For your .NET Core app to work on Cloud Foundry, you must modify the `Main` method to configure the app to listen on the port specified by the `$PORT` environment variable, which Cloud Foundry sets automatically.
   
   1. Open the file that contains your `Main` method.
   
  -1. Add a `using` statement to the top of the file:
  +1. Add a `using` statement to the top of the file.
   
       ```c#
       using Microsoft.Extensions.Configuration;
  
positive.code: }
  ```
  
  <p class="note">
    <strong>Note</strong>: The samples provided in the <a href="https://github.com/aspnet/cli-samples">cli-samples repository</a> and the templates provided by Visual Studio and Yeoman work with this buildpack after you have followed the steps above.</a>
  </p>
  
  ## <a id='multiple_projects'></a>Deploy Apps with Multiple Projects ##
  
  In order to deploy an app that contains multiple projects, a main project for the buildpack to run must be specified.
  
  To do so, create a `.deployment` file in the root folder of the app which sets the path to the main project as follows:
  
  ```text
  [config]
  project = <main project>
  ```
  
  1. If the app uses `project.json` set `project` to the directory containing the `project.json` file of the main project
  2. If the app uses MSBuild, set `project` to the `*.csproj` or `*.fsproj` file of the main project
  
  For example, if an app using MSBuild contains three projects in the `src` folder, the main project `MyApp.Web` plus `MyApp.DAL` and `MyApp.Services`, format the `.deployment` file as follows:
  
  ```text
  [config]
  project = src/MyApp.Web/MyApp.Web.csproj
  ```
  
  In this case, the buildpack automatically compiles the `MyApp.DAL` and `MyApp.Services` projects if the `MyApp.Web.csproj` file of the main project lists them as dependencies, `MyApp.Web`. The buildpack attempts to execute the main project with `dotnet run -p src/MyApp.Web/MyApp.Web.csproj`.
  
  ## <a id='disconnected_environments'></a>Push an App in a Disconnected Environment ##
  
  
negative.code:     ```
      This allows the buildpack to pass the correct port from `$PORT` to the app when running the initial startup command.
  
  1. Remove the following line from the `Main` method:
  
      ```c#
      .UseContentRoot(Directory.GetCurrentDirectory())
      ```
  
  1. Add the following line after `.UseKestrel()`:
  
      ```c#
      .UseConfiguration(config)
      ```
  
  1. Add `Microsoft.Extensions.Confugration.CommandLine` as a dependency using one of the following:
      - `project.json`:
          
  		  ```json
          "Microsoft.Extensions.Configuration.CommandLine": "1.0.0",
          ```
      - `*.csproj`:
  
          ```xml
          <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
              <Version>1.0.0</Version>
          </PackageReference>
          ```
  
  1. Remove the following line from the `Startup` method:
  
  