anchor.diff:  
   ### <a id='no-route'></a> no-route
   
  -<p class='note'><strong>Note:</strong> If you use the `no-route` flag attribute in the manifest or the flag option, it overrides all route-related
  +<p class='note'><strong>Note:</strong> If you use the <code>no-route</code> flag attribute in the manifest or the flag option, it overrides all route-related
     attributes.</p>
   
   By default, `cf push` assigns a route to every app. But, some apps process data while running in the background and should not be assigned routes.
  
positive.code: With inheritance, child manifests inherited configurations from a parent manifest. The child manifests can use the inherited configurations as provided,
  extend them, or override them.
  
  ### <a id='buildpack-deprecated'></a> buildpack Attribute Is Deprecated
  
  The singular `buildpack` attribute is deprecated. It has been replaced by `buildpacks`, which specifies multiple buildpacks. For more information, see
  [buildpacks](#buildpacks) above.
  
negative.code: <p class='note warning'><strong>Warning:</strong> Running <code>cf push app -f manifest.yml</code> fails if your manifest uses any of these deprecated
    features along with the feature that replaces it.</p>
  
  ### <a id='yaml-anchors'></a> Top-Level Attributes
  
  Previously, you could declare top-level attributes, which are also known as global attributes. For example, you can move an attribute above the `applications`
  block, where it need appear only once.
  