anchor.diff:  	* `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:
  +	See the following example manifest file that includes multiple sidecars:
   
   	```
   	---
  
positive.code: 
  You can run additional processes in the same container as your app. These are called sidecar processes, or sidecars. An example of a sidecar is an Application Performance Monitoring (APM) tool. 
  
  When you provide a sidecar for your app, Cloud Foundry packages the required code and configuration needed to run the sidecar and app in the same droplet. It deploys this droplet in a single container on Diego and both processes within the container are health checked independently.
  
  For additional information about sidecars, see the _Sidecars_ section of the [CAPI v3 documentation](http://v3-apidocs.cloudfoundry.org/version/release-candidate/#sidecars). 
  
  
  ### <a id="use-case"></a> Use Cases
  
  You can use sidecars for processes that depend on each other or must run in the same container. 
  
  Some examples include processes that need do the following:
  
  * Communicate over a Unix socket or through localhost
  * Share the same filesystem
  * Be scaled and placed together
  * Have fast interprocess communication
  
  ### <a id="limitations"></a> Limitations
  
  Sidecars have the following limitations:
  
  * The start and stop order of app processes and their sidecars is undefined.
  * App processes and sidecars are codependent: if either crashes or exits, the other will as well.
  * Sidecars are currently not independently scalable and share resources with the main app process and other sidecars within the container. 
  * Sidecars only support PID-based health checks. HTTP health-checks for sidecars are not currently supported.
  
  ## <a id="create"></a> Push an App with a Sidecar
  
  This section provides general instructions for pushing an app with a sidecar. For an example that you can try yourself, see the [Sidecar Tutorial](#tutorial) section below. 
  
  ### <a id="prerequisite"></a> Prerequisites
  
  Before you can push an app with a sidecar, you have a must have the following:
  
  * An app that is currently running or ready to be pushed. 
  * A file that Cloud Foundry can execute inside the app container as a sidecar process. A few examples include an executable binary, a Java .jar file, or Ruby scripts
  
  ### <a id="create"></a> Procedure
  
  
negative.code: 	cf ssh sidecar-dependent-app
  	```
  
  1. Terminate the sidecar process:
  
  	```
  	kill -9 $(pgrep config-server)
  	```
  1. View the output in the terminal window where you are streaming the app logs. The app logs indicate that the sidecar process crashed and that Diego  restarted the app container. For example:
  	<pre class="terminal">
  	2019-04-17T16:48:55.41-0700 [API/0] OUT App instance exited with guid 
  	21df1eb8-f25d-43b2-990b-c1a417310553 payload: 
  