anchor.diff:  
   ## <a id='pushing_apps'></a> Push an App
   
  -Cloud Foundry automatically uses this buildpack if it detects a 
  +Cloud Foundry automatically uses this buildpack if it detects a
   `requirements.txt` or `setup.py` file in the root directory of your project.
   
   If your Cloud Foundry deployment does not have the Python Buildpack installed, or the installed version is out of date, you can use the latest version by specifying it with the `-b` option when you push your app. For example:
  
positive.code:     $ cf push python-app -c "waitress-serve --port=$PORT DJANGO-WEB-APP.wsgi:MY-APP"
      </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> Vendor App Dependencies
  
negative.code: 
  ## <a id='private-repos'></a> Private Dependency Repository
  
  If you deploy apps in an environment that needs to use a private dependency
  repository, add the URL of the repository to the `requirements.txt` file in the
  following format:
  
  ```
  --index-url=https://example.com/api/pypi/ext_pypi/simple
  fixtures==2.0.0
  ```
  
  If the private repository uses a custom SSL certificate that is installed on the platform, you may see an error similar to the following:
  <pre class="terminal">
  Could not fetch URL <span>https:</span>//example.com/api/pypi/ext_pypi/simple/fixtures/:
  There was a problem confirming the ssl certificate:
  [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777) - skipping
  </pre>
  
  This error occurs because `pip` does not use system cerificates by default.
  To resolve this issue, set the `PIP_CERT` environment variable in the `manifest.yml` file to point to the system certificate store.
  
  For example:
  
  ```
  ---
  env:
  