anchor.diff:  	</tr>
   	<tr>
   		<td>4</td>
  -		<td>Operator confirms apps have been migrated and deletes the stack. See <a href="#delete-stacks">Delete a Stack</a>.
  +		<td>Operator confirms apps have been migrated.</td>
  +	</tr>
  +	<tr>
  +		<td>4</td>
  +		<td>Operator deletes buildpacks associated with <code>cflinuxfs3</code>.</td>
  +	</tr>
  +	<tr>
  +		<td>5</td>
  +		<td>Operator deletes the stack. See <a href="#delete-stacks">Delete a Stack</a>.
   		<p class="note"><strong>Note</strong>: If you upgrade your deployment to a version that contains the stack you deleted, the stack returns on upgrade.</p></td>
   	</tr>
   	<tr>
  -		<td>5</td>
  +		<td>6</td>
   		<td>If applicable, operator upgrades the deployment to the version that does not contain the old stack.</td>
   	</tr>
   </table>
  
positive.code: 
  1. To delete a stack, run the following command:
  
  	```
  	cf delete-stack STACK-NAME
  	```
  
negative.code: 
  ### <a id="change-stacks"></a> Change Stacks
  
  This section describes how to change the stack that an app uses. Stack Auditor rebuilds the app onto the new stack without a change in the source code of the app. If you want to move the app to a new stack with updated source code, follow the procedure in the [Changing Stacks](../devguide/deploy-apps/stacks.html) topic. 
  
  <p class="note warning"><strong>WARNING</strong>: Stack Auditor rebuilds the app, which causes downtime. To avoid downtime, use a blue-green deployment strategy. See <a href="../devguide/deploy-apps/blue-green.html">Using Blue-Green Deployment to Reduce Downtime and Risk</a>.</p>
  
  To change the stack an app uses, do the following:
  
  