anchor.diff:  
   ## Parallel groups  
   
  -If you put two (or more) group steps in a YAML config file consecutively, they run in parallel. For example:  
  +If you put two or more group steps in a YAML config file consecutively, they will run in parallel. For example:  
   
   ```yml
   # 1.sh and 3.sh will start at the same time.
  
positive.code: Running jobs in parallel has some limitations:  
  
  <!-- vale off -->
  * If you put even a single command between consecutive groups in a YAML config, the groups will no longer be interpreted as parallel.
  * Parallel groups will be displayed ungrouped if the build's jobs are truncated because Buildkite doesn't currently store or calculate any information about the number of jobs in a non-parallel group.
  * If a parallel step exists within a group, parallel jobs are treated as regular jobs within a step group - so you can't have parallel groups within step groups. So, for example, a `group` that contains two `steps` each with `parallel: 4` will display eight jobs in it, with no visual indication that those eight jobs are two parallel steps. 
  <!-- vale on -->
  
  * If a parallel job group is within a named group, the groups are handled as though the parallel group isn't there.  
  * It's impossible to have a parallel job with only some of the jobs within a group, as they're all created on the same YAML step entry.  
  
  ## Using wait steps in job groups
   
  
negative.code: ```
  {: codeblock-file="group-step-in-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. 
  
  The group step type also groups jobs up by a `group_identifier` ([`key` attribute](/docs/pipelines/group-step#group-step-attributes)) if it exists.
  
  