anchor.diff:  </PropertyGroup>
   ```
   
  -###.runtimeconfig.json Apps
  -
  -In a `.runtimeconfig.json` app, the latest .NET Framework patch version is used by default. To pin to a specific .NET Framework version, add the `applyPatches` property and set it to `false`.
  +### <a id='dotnet-framework-fdd'></a>For framework-dependent apps
  +
  +In your `.runtimeconfig.json` app, the latest .NET Framework patch version is used by default. To pin to a specific .NET Framework version, add the `applyPatches` property and set it to `false`.
   
   ```
   {
  
positive.code: 
  See the [Environment Variables](../../devguide/deploy-apps/manifest.html#env-block) section of the <em>Deploying with Application Manifests</em> topic for more information.
  
  ## <a id='framework-dependent'></a>Framework Dependent Deployments (FDD) Workflow ##
  This is the recommended workflow when deploying an app in an offline setting.
  
  
negative.code: 
  For a basic example app, see [ASP.NET Core getting started application](https://github.com/IBM-Bluemix/aspnet-core-helloworld) in GitHub.
  
  ## <a id='source-based'></a>Source-based, Non-published Workflow
  
  To use this workflow, simply `cf push` the source code for your app (i.e. not the resultant directory of a `dotnet publish`).
  
  This is the recommended workflow because the buildpack can keep all your dependencies in-sync and up-to-date.
  When using this workflow, here are some edge-cases you may run into:
  
  ### <a id='multiple-projects'></a>Deploy Apps with Multiple Projects
  
  To deploy an app that contains multiple projects, you must specify a main project for the buildpack to run. 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. Set `project` to the `*.csproj` or `*.fsproj` file of the main project.
  
  For example, if an app contains three projects in the `src` folder (the main project `MyApp.Web`, `MyApp.DAL`, and `MyApp.Services`), format the `.deployment` file as follows:
  
  ```text
  [config]
  project = src/MyApp.Web/MyApp.Web.csproj
  ```
  
  In this example, 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. The buildpack attempts to execute the main project with `dotnet run -p src/MyApp.Web/MyApp.Web.csproj`.
  
  ### <a id='non-default-package-sources'></a>Using Non-Default Package Sources
  
  To deploy an app that uses non-default package sources, you must specify those package sources in the [`NuGet.Config` file](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file).
  For a basic example, see this [Hello World sample](https://github.com/IBM-Bluemix/aspnet-core-helloworld).
  
  ### <a id='disabling-nuget'></a>Disabling and Clearing the NuGet Package Cache
  
  You may need to disable NuGet package caching, or clear NuGet packages cached in the staging environment, in one of the following scenarios:
  