anchor.diff:  
   Applications can bind to services such as databases, messaging, and key-value stores.
   
  -Applications are deployed into App Spaces. An application can only bind to services that exist in the target App Space before the application is deployed.
  +Applications are deployed into App Spaces. An application can only bind to services instances that exist in the target App Space before the application is deployed.
   
   The `services` block consists of a heading, then one or more service instance names.
   
  
positive.code:  - instance_ABC
   - instance_XYZ
  ~~~
  
  ## <a id='multi-apps'></a>Describing Multiple Applications with One Manifest ##
  
  
negative.code: 
  **Note:** If you want to push more than a single file, but not the entire contents of a directory, consider using a `.cfignore` file to tell `cf push` what to exclude.
  
  ## <a id='precedence'></a>Precedence Between Manifests, Command-line Options, and Most Recent Values ##
  
  When you push an application for the first time, `cf` applies default values to any attributes that you do not set in a manifest or `cf push` command-line options.
  
  * For example, `cf push <application_name>` with no manifest might deploy one instance of the app, drawing on default values to allocate one gigabyte of memory and one gigabyte of disk.
  
  Between one push and another, attribute values can change in other ways.
  
  * For example, the `cf scale` command changes the number of instances.
  
  The attribute values on the server at any one time represent the cumulative result of defaults, manifest settings, `cf push` command-line options, and commands like `cf scale` applied up to that point.
  There is no special name for this resulting set of values on the server.
  You can think of them as the most recent values.
  
  On pushes after the first one, `cf` follows rules of precedence when setting attribute values:
  
  * Manifests override most recent values.
  * Command-line options override manifests.
  
  In general, you can think of manifests as just another input to `cf push`, to be combined with command-line options and most recent values.
  
  ## <a id='optional-attributes'></a>Optional Attributes ##
  
  This section explains how to describe optional application attributes in manifests. Each of these attributes can also be specified by a command-line option. Command-line options override the manifest.
  
  ### <a id='buildpack'></a>The buildpack attribute
  
  