anchor.diff:  
       This allows the buildpack to pass the correct port from `$PORT` to the app when running the initial startup command.
   
  -
  -
  -
   1. Add `Microsoft.Extensions.Configuration.CommandLine` as a dependency in `*.csproj`:
   
  -        ```xml
  -        <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
  -            <Version>VERSION</Version>
  -        </PackageReference>
  -        ```
  -
  -    In the above examples, replace `VERSION` with the version of the package to use. Valid versions can be found at https://www.nuget.org.
  +    ```
  +    <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
  +        <Version>VERSION</Version>
  +    </PackageReference>
  +    ```
  +
  +    In the above example, replace `VERSION` with the version of the package to use. You can find valid versions at https://www.nuget.org.
   
   1. If your app requires any other files at runtime, such as JSON configuration files, add them to the `include` section of `copyToOutput`.
   
   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. Refer to the following example `Main` method:
  +With these changes, the `dotnet run` command copies your app `Views` to the build output where the .NET CLI can find them.
  +Refer to the following example `Main` method:
   
   ```c#
   public static void Main(string[] args)
  
positive.code:   sdk: 2.x
  ```
  
  The buildpack chooses which SDK to install based on the files present at the app root, according to the following order of precedence:
  
  1. `buildpack.yml`
  1. `global.json`
  1. If the app contains only `*.fsproj` files, the buildpack installs the latest 1.1.x SDK.
  
  <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 both <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>Specifying .NET Runtime Versions
  ### <a id='dotnet-runtime-source-based'></a>For source-based apps
  
  Specify a minor version of the .NET Runtime.
  Do not specify a patch version, because
  buildpacks contain only the two most recent patch versions of each minor version.
  
  Add the following to your `.csproj` or `.fsproj` file to lock the .NET Runtime version:
  
  ```
  <PropertyGroup>
  
negative.code: }
  ```
  
  ## <a id='offline'></a> Push an App in a Disconnected Environment
  
  For offline environments, Cloud Foundry recommends using the [Framework-Dependent Deployments](#framework-dependent)
  workflow. This workflow enables the deployed app to use the latest runtime provided by the offline buildpack.
  
  ## <a id='runtime-store'></a>Maintain Runtime Package Store
  
  <p class="note"><strong>Note:</strong> This section applies only to source-based and framework-dependent deployments.</p>
  
  For maintaining ASP.NET Core assemblies, update your `.csproj` file with the following:
  
  ```
  <PropertyGroup>
  