anchor.diff:  ```
   
   
  -## <a id='vendoring'></a> Vendor App Dependencies
  +## <a id='vendoring'></a> Vendoring App Dependencies
   
   If you are deploying in an environment that is disconnected from the Internet, your application [must vendor its dependencies](https://github.com/cf-buildpacks/buildpack-packager/blob/master/doc/disconnected_environments.md).
   
  -Inside your `r.yml`, provide the names of your vendored packages in the `packages` list:
  +To set up your own custom, local CRAN-like repository to vendor your packages, create the `src/contrib` directories and populate them with your package source tarballs. For more information, check out this [step-by-step guide](https://rstudio.github.io/packrat/custom-repos.html).
  +
  +Add the `src/contrib` directories containing your package tarballs to a `vendor_r` directory at the root of your app. This directory is named as such so as not to conflict with vendor directories of other languages, such as python.
  +
  +Then, inside your `r.yml`, provide the names of your vendored packages in the `packages` list:
   
   <pre class="terminal">
   
  
positive.code: 
  - Specify a start command with `-c`:
  
      <pre class="terminal">
      $ cf push r-app -c "R -f simple.r"
      </pre>
  
  - Specify a start command in the application manifest by setting the `command` attribute. For more information, see the [Deploying with Application Manifests](../../devguide/deploy-apps/manifest.html#start-commands) topic.
  
  ## <a id='vendoring'></a> Specifying App Dependencies
  
  As of v0.0.5, the following packages are provided by the buildpack:
  
  
negative.code: 
  To stage with the R buildpack and start an application, do one of the following:
  
  -  Supply a Procfile. For more information about Procfiles, see the [Configuring a Production Server](../prod-server.html) topic. The following example Procfile specifies `R -f` as the start command for a web app with the entrypoint `simple.r`:
  
      ```
      web: R -f simple.r
  