anchor.diff:  
   You can use the Cloud Foundry Command Line Interface (cf CLI) to run a task in the context of an app.
   
  -<p class="note"><strong>Note</strong>: To run tasks with the cf CLI, you must install cf CLI v6.23.0 or later. See the <a href="../cf-cli/install-go-cli.html">Installing the Cloud Foundry Command Line Interface</a> topic for information about downloading, installing, and uninstalling the cf CLI.</p>
  +<p class="note"><strong>Note:</strong> To run tasks with the cf CLI, you must install cf CLI v6.23.0 or later. For information about downloading, installing, and uninstalling the cf CLI, see the <a href="../cf-cli/install-go-cli.html">Installing the Cloud Foundry Command Line Interface</a>.</p>
   
  -<p class="note"><strong>Note</strong>: To run a task without starting the app, push the app with <code>cf push -i 0</code> and then run the task. You can run the app later by scaling up its instance count.</p>
  +<p class="note"><strong>Note:</strong> To run a task without starting the app, push the app with <code>cf push -i 0</code> and then run the task. You can run the app later by scaling up its instance count.</p>
   
  +To run a task on an app:
   
  -To run a task on an app, perform the following steps:
  +1. Push your app by running:
   
  -1. Push your app:
  -	<pre class="terminal">$ cf push APP-NAME</pre>
  -1. Run your task on the deployed app:
  -	<pre class="terminal">$ cf run-task APP-NAME "TASK" --name TASK-NAME</pre>
  +	```
  +	cf push APP-NAME
  +	```
  +
  +1. Run your task on the deployed app by running:
  +	```
  +	cf run-task APP-NAME "TASK" --name TASK-NAME
  +	```
   
   The following example runs a database migration as a task on the `my-app` app:
   
  
positive.code: owner: CAPI
  ---
  
  
  
  This topic describes how to run tasks in Cloud Foundry. A task is an app or script whose code is included as part of a deployed app, but runs independently in its own container.
  
  ## <a id='about-tasks'></a> About Tasks
  
  In contrast to a long running process (LRP), tasks run for a finite amount of time, then stop. Tasks run in their own containers and are designed to use minimal resources. After a task runs, Cloud Foundry destroys the container running the task.
  
  As a single-use object, a task can be checked for its state and for a success or failure message.
  
  
negative.code: 
  ### <a id="use-cases"></a> Use Cases for Tasks
  
  Tasks are used to perform one-off jobs, which include:
  
  * Migrating a database
  * Sending an email
  