anchor.diff:    <tr>
       <td><code>notify</code></td>
       <td>
  -      Notify attribute description.<br>
  -      <em>Example:</em> <code>Example</code><br>
  +      An attribute that allows you to trigger build notifications to different services.<br>
  +      <em>Example:</em> <code>github_check</code><br>
       </td>
     </tr>
     <tr>
  
positive.code: # Group Step
   
  A *group* step groups jobs and steps like block step, trigger step, comand step, etc. into logical groups, and allows displaying them within groups on the build page in the Buildkite UI.
  
  > Note: Group steps cannot be nested. 
  
  You can scale your build pipelines in Buildkite to support an unlimited number of jobs. However, a large number of jobs on the build page can look messy. If pipelines contain 4-5 steps that can be logically grouped together, you can put them in a group using the `group` step type.
  
  The group step also helps manage dependencies between a collection of steps in a DAG (for example, step X depends on everything in a group Y).
  
  > Note: In some cases, using group step might break the DAG visualisation feature.  
  
  {:toc}
   
  A group step can be defined in your pipeline settings, or in your [pipeline.yml](/docs/pipelines/defining-steps) file.  
  
  ```yml
  steps:
     - group: "Various Grouped Jobs"
                  steps:
                  - command: "test.sh"
                  - wait: ~
                  - trigger: "#{project.slug}"
                    label: "Deploy"
  ```
  {: codeblock-file="pipeline.yml"}
  
  This is what a typical group step use looks like:
  
  
negative.code:   <tr>
      <td><code>key</code></td>
      <td>
      	A unique string to identify the block step.
        <em>Example:</em> <code>"test-suite"</code>
      </td>
    </tr>  
  