anchor.diff:  
   1. Open and review the `manifest.yml` file. Under `sidecars`, the sidecar is specified with a name, process type, and start command. Under `env`, there is an environment variable that defines the port on which the app and sidecar communicate. 
   
  -1. Apply the manifest to the app:
  -	* **cf CLI v7**
  +1. To apply the manifest to the app:
  +	* If you are using cf CLI v7, run:
   
   		```
   		cf7 apply-manifest
   		```
  -	* **cf CLI v6**
  +	* If you are using cf CLI v6, run:
   
   		```
   		cf v3-apply-manifest
   		```
   
  -1. Push the app: 
  -	* **cf CLI v7**
  +1. To push the app: 
  +	* If you are using cf CLI v7, run:
   
   		```
   		cf7 push sidecar-dependent-app
   		```
  -	* **cf CLI v6**
  +	* If you are using cf CLI v6, run:
   	
   		```
   		cf v3-push sidecar-dependent-app
   		```
   
  -After you push the app, you can further explore it in the following sections: 
  -* [View the Processes Running in the Container](#view-processes) 
  -* [View the Web URL and App Logs](#view-logs)
  +After you push the app, you can further explore it in t[View the Processes Running in the Container](#view-processes) and [View the Web URL and App Logs](#view-logs)
   
   ### <a id="view-processes"></a> View the Processes Running in the Container
   
  -To view the app and sidecar process running in the container, do the following:
  -
  -1. SSH into the app container:
  +To view the app and sidecar process running in the container:
  +
  +1. SSH into the app container by running:
   	
   	```
   	cf ssh sidecar-dependent-app
   	```
   
  -1. Run `ps aux` to see both processes running: The `rackup` process for the main app and `config-server` process for the sidecar. For example:
  +1. To see both the `rackup` process for the main app and `config-server` process for the sidecar, run:
  +
  +	```
  +	ps aux
  +	```
  +	The output you see should resemble the output below:
   
   	<pre class="terminal">
   	vcap@f00949bd-6601-4731-6f7e-e859:~$ ps aux
  
positive.code: This topic describes sidecar processes and how to include them when you push your app. 
  
  <div class="note">
  <strong>Note:</strong>
  This topic includes references to cf CLI v7 beta commands. Consider the following when using these commands:
  <ul>
  <li> cf CLI v7 beta and CAPI v3 are both in active development and subject to change. </li>
  <li> cf CLI v7 beta is developed and tested against the latest CAPI release candidate. </li>
  <li> cf CLI v7 beta does not yet use CAPI v3 for all commands. Some commands still use CAPI v2 during beta. </li>
  </ul>
  For more information, see <a href="../cf-cli/v7.html">Upgrading to cf CLI v7 (Beta)</a>. 
  </div>
  
  <%= vars.capi_sidecar_req %>
  
  ## <a id="overview"></a> Overview
  
  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. 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). 
  
  For sample apps that use sidecars, see [cloudfoundry-samples/capi-sidecar-samples](https://github.com/cloudfoundry-samples/capi-sidecar-samples) on GitHub. The tutorial in this document shows you how to push one of these sample apps. 
  
  
  ## <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. 
  
  For example, you can use sidecars for processes that must do the following:
  
  * Communicate over a Unix socket or through localhost
  * Share the same filesystem
  
negative.code: vcap         227 0.0  0.0     86268    3116  pts/0 R      23:12 0:00  ps aux	
  	</pre>
  
  1. To see that the sidecar is listening on the port specified by `CONFIG_SERVER_PORT` and that the main `ruby` process is connected to it, run:
  
  	```
  	lsof -i | grep $CONFIG_SERVER_PORT
  	```
  	The output you see should resemble the output below: 
  
  	<pre class="terminal">
  	vcap@f00949bd-6601-4731-6f7e-e859:~$ lsof -i | grep $CONFIG_SERVER_PORT
  