anchor.diff:  
   Apps are deployed into app spaces. An app can only bind to services instances that exist in the target app space before the app is deployed.
   
  -The `services` block consists of a heading, then one or more service instance names.
  -
  -Whoever creates the service chooses the service instance names. These names can convey logical information, as in `backend_queue`; describe the nature of the
  -service, as in `mysql_5.x`; or do neither, as in the following example:
  +The `services` block consists of a heading and one or more service instance names.
  +
  +Whoever creates the service chooses the service instance names. These names can convey logical information, describe the nature of the service, or neither.
  +
  +For example:
   
   ```
   ---
  
positive.code: 
  #### <a id='push-flag-options'></a> Push Flag Options
  
  This attribute has unique interactions with different command line options.
  
  <table border="1" class="nice" >
    <tr>
      <th>Push Flag Option</th>
      <th>Resulting Behaviour</th>
    </tr>
    <tr>
      <td><code>--no-route</code></td>
  
negative.code: 
  ### <a id='no-route'></a> no-route
  
  <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.
  