anchor.diff:  
   When you provide a sidecar for your app, <%= vars.platform_name %> 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 undergo health checks independently. 
   
  +You can push sidecar processes with your app by using one of two different methods:
  +
  +* Using an app manifest. For instructions, see [Push an App with a Sidecar Using an App Manifest](#create).
  +* With a custom buildpack. For instructions, see [Sidecar Buildpacks (Beta)](../buildpacks/sidecar-buildpacks.html). 
  +
   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 the [capi-sidecar-samples](https://github.com/cloudfoundry-samples/capi-sidecar-samples) repository on GitHub. This topic shows you how to push one of these sample apps. 
  -
  +For sample apps that use sidecars, see the [capi-sidecar-samples](https://github.com/cloudfoundry-samples/capi-sidecar-samples) repository on GitHub. This topic shows you how to push one of these sample apps using an app manifest. 
   
   ## <a id="use-case"></a> Use Cases
   
  
positive.code: ---
  
  This topic describes sidecar processes and how to include them when you push your app.
  
  This topic describes specifying a sidecar process with an app manifest. 
  As an alternative to this method, you can also push sidecar processes for your apps with a custom buildpack. 
  For more information, see [Sidecar Buildpacks](../buildpacks/sidecar-buildpacks.html). 
  
  <div class="note">
  <strong>Note:</strong> This topic includes references to cf CLI v7 beta commands. When using these commands, consider:
  
negative.code: 		cf v3-push APP-NAME
  		```
  		Where `APP-NAME` is the name of your app.
  
  
  ## <a id="tutorial"></a> Sidecar Tutorial
  