anchor.diff:    <tr>
       <td><code>key</code></td>
       <td>
  -    	A unique string to identify the step, block, or group. Alias: `identifier` or `id`.
  +    	A unique string to identify the step, block, or group. Alias: `identifier` or `id`.<br>
         <em>Example:</em> <code>"test-suite"</code>
       </td>
     </tr>  
  
positive.code:  
  A *group* step can contain various sub-steps, and display 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".
  
  {:toc}
   
  
negative.code: ```
  {: codeblock-file="pipeline.yml"}  
  
  These groups will be merged into one in the UI, and the `"docker build"` step will be added to the existing group.
  
  ```yml
  - group: "Setup"
  