anchor.diff:  
   ## Group merging  
   
  -Different groups that are have the same name and are defined consecutively in the pipeline will be merged together in the Buildkite UI. 
  +Different groups that have the same name and are defined consecutively in the pipeline will be merged together in the Buildkite UI. 
   
   For example, if you have a YAML file:
   
  
positive.code: # Group Step
   
  A *group* step groups jobs and other steps into logical groups and displays them in a single logical group on the Build page. For example, you can group all of your linting steps or all of your UI test steps to keep the Build page less messy. Sub-groups and nested groups are not supported. 
  
  The group step also helps manage dependencies between a collection of steps, for example, "step X" [`depends-on`](/docs/pipelines/group-step#group-step-attributes) everything in "group Y".
  
  
negative.code:     <td>
        The label that will be displayed in the pipeline visualisation in Buildkite (name of the group in the UI). Supports emoji.<br>
        <em>Example:</em> <code>"\:hammer\: Tests" will be rendered as "🔨: Tests"</code><br>
      </td>
    </tr>
    <tr>
      <td><code>notify</code></td>
      <td>
        Allows you to <a href="/docs/pipelines/notifications">trigger</a> build notifications to different services. You can also choose to conditionally send notifications based on pipeline events.<br>
        <em>Example:</em> <code>"github_check:"</code><br>
      </td>
    </tr>
    <tr>
  