anchor.diff:  ```
   {: codeblock-file="group-step-in-pipeline.yml"} 
   
  -And this is how it's displayed in the UI: 
  +This is how it's displayed in the UI: 
   
   <%= image "job-groups-in-UI.png", width: 1760, height: 436, alt: "Job groups displayed in the Buildkite UI" %>
   
  -Only the first 100 jobs within a build header can be displayed in the UI, so you might not see all of your groups at all times. However, the jobs are fine and will still show up on the build page. 
  +Only the first 100 jobs within a build header can ever be displayed in the UI, so you might not see all of your groups at all times. However, the jobs are fine and will still show up on the build page. 
   
   The group step type also groups jobs up by a `group_identifier` ([`key` attribute](/docs/pipelines/group-step#group-step-attributes)) if it exists.
   
  
positive.code: 
  ## 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. 
  
  For example, if you have a YAML file:
  
  
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>
  