anchor.diff:    </tr>
   </table>
   
  -## Parallel groups  
  +## Parallel groups
   
   If you put two or more group steps in a YAML config file consecutively, they will run in parallel. For example:  
   
  
positive.code:   <tr>
      <td><code>key</code></td>
      <td>
      	A unique string to identify the step, block, or group. Alias: `identifier` or `id`.<br>
        <em>Example:</em> <code>"test-suite"</code>
      </td>
    </tr>  
    <tr>
      <td><code>label</code></td>
      <td>
  
negative.code:     - name: "\:yarn\: Outdated Check"
        command: ".buildkite/steps/outdated"
  ```
  {: codeblock-file="pipeline.yml"}
  
  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 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.
  
  You can [merge groups](#group-merging) by giving them the same `label` or name.
  
  ## Group step attributes
  
  _Required attributes:_
  
  <table data-attributes>
  <tr>
  