anchor.diff:  
   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 using the `dotnet run -p src/MyApp.Web/MyApp.Web.csproj` command.
  +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>Use Non-Default Package Sources
   
  
positive.code: 
  If your app requires external shared libraries that are not provided by the rootfs or the buildpack, you must place the libraries in an `ld_library_path` directory at the app root.
  
  <p class="note"><strong>Note</strong>: You must keep these libraries up to date. They do not update automatically.</p>
  
  The .NET Core buildpack automatically adds the directory `<app-root>/ld_library_path` to `LD_LIBRARY_PATH` so that your app can access these libraries at runtime.
  
negative.code: 
  ## <a id='framework-dependent'></a>Framework-Dependent Deployments##
  
  This is the recommended workflow if you deploy an app in an offline setting.
  
  In a framework-dependent deployment (FDD), you deploy only your app and third-party dependencies.
  For information about deploying FDDs, see
  [Framework-dependent deployments (FDD)](https://docs.microsoft.com/en-us/dotnet/core/deploying/index#framework-dependent-deployments-fdd)
  in the Microsoft documentation.
  To deploy an FDD using the buildpack, do the following:
  
  1. Publish the app by running the `dotnet publish [-f YOUR-FRAMEWORK] [-c Release]` command.
  
  1. Navigate to the `bin/Debug|Release/YOUR-FRAMEWORK/YOUR-RUNTIME>/publish` directory.
  Alternatively, if your app uses a `manifest.yml`, specify a path to the output folder of `dotnet publish`.
  This allows you to push your app from any directory.
  
  