anchor.diff:  ```
   
   ### <a id='pushing_Apps_with_native_Go_vendoring'></a>Push an App with Native Go Vendoring ###
  -If you are using the native Go vendoring system, which packages all local dependencies in the `vendor/` directory, you must specify your app's package name in the `GOPACKAGENAME` environment variable. An example `manifest.yml`:
  +If you use the native Go vendoring system, which packages all local dependencies in the `vendor/` directory, you must specify your app's package name in the `GOPACKAGENAME` environment variable. 
  +
  +An example `manifest.yml`:
   
   ```yaml
   ---
  
positive.code:     command: my-go-server
  ```
  
  If you do not specify a start command via a `Procfile`, in the manifest, or via the `-c` flag for `cf push`, the generated binary will be used as the start command. (ex. `my-go-server`)
  
  ### <a id='with_godep'></a>Push an App with godep ###
  If you are using [godep](https://github.com/tools/godep) to package your dependencies, make sure that you have created a valid `Godeps/Godeps.json` file in the root directory of your app by running `godep save`.
  
negative.code: 
  For more information about Procfiles, see the [Configuring a Production Server](../prod-server.html) topic.
  
  You can also specify the start command for your app in the `manifest.yml` file in the root directory. For example, your `manifest.yml` could contain the following:
  
  ```yaml
  ---
  