anchor.diff:  
   <p class="note"><strong>Note</strong>: This procedure uses <code>v3</code> commands because it requires the server-side manifest support in CAPI v3.</p>
   
  -1. If your app does not exist yet, create it:
  +1. Create an app. Or, use an existing app. Run the following command to create an app:
   
   	```
   	cf v3-create-app MY-APP
   	```
  -
  -1. If you do not already have one, create a manifest file in the root directory of your app, such as `manifest.yml`. For more information, see [Deploying with App Manifests](./deploy-apps/manifest.html). 
  +	Where `MY-APP` is a name that you define for your app.
  +
  +1. Create a manifest file in the root directory of your app, such as `manifest.yml`. Or, use an existing manifest file for your app. For more information, see [Deploying with App Manifests](./deploy-apps/manifest.html). 
   
   1. Add the following content to your app manifest file under the `applications` key:
   
  
positive.code: 	* `MY-PROCESS-TYPES` is a list of app processes for the sidecar to attach to, such as `web` or `worker`. You can attach multiple sidecars to each process type your app uses. 
  	* `MY-START-COMMAND` is the command used to start the sidecar. For example, `./my-binary` or `java -jar my-java-file.jar`. 
  
  	See the following example that includes multiple sidecars:
  
  	```
  	---
  
negative.code:          command: bundle exec run-performance-monitor
  	```
  
  1. Apply the manifest file to your app: 
  
  	```
  	cf v3-apply-manifest -f PATH-TO-MANIFEST
  