anchor.diff:  
   This will start a single process, but can run up to 5 different jobs at the same time.
   
  -The start command can also be run multiple times with different configurations, for example to change the [queue](/docs/agent/v3/queues):
  +The start command can also be run multiple times with different configurations. For example, to change the [queue](/docs/agent/v3/queues):
   
   ```bash
   buildkite-agent start --tags queue=test
  
positive.code: 
  ### Multiple agents on many machines
  
  The secret to really fast builds is running as many build agents as you can. The best way to do that is to have lots of machines running build agents. Those machines can be anything you like, whether it's your laptop, a few spare computers in your office, or a fleet of thousands of cloud compute instances.
  
  The Buildkite Agent runs on many platforms, and should run on any hardware and any cloud compute provider. It is built to be flexible, and can be composed in any way that suits the platform, infrastructure, or workload. The [installation instructions](/docs/agent/v3/installation) demonstrate how to run the agent across various platforms.
  
  For example, you could start several [Google Cloud Compute instances](/docs/agent/v3/gcloud#running-the-agent-on-google-compute-engine), then install and start build agents. These instructions can be automated using infrastructure as code tools like [Terraform](https://www.terraform.io), and then [add auto-scaling rules](#auto-scaling-your-build-agents) so you always have enough capacity.
  
  The [Elastic CI Stack for AWS](/docs/quickstart/elastic-ci-stack-aws) provides a pre-built CloudFormation Stack for AWS that runs multiple auto-scaling agents.
  
  ## Parallel Jobs
  
  `parallelism` is an attribute on a single [command step](/docs/pipelines/command-step) which causes it to be split into many jobs. Those jobs will be the same except for having a parallel index and count. They share the same dependencies and agent tags.
  
  
negative.code: 
  You can use these two environment variables to divide your application's tests between the different jobs.
  
  ## Libraries
  
  The following libraries have built-in support the `BUILDKITE_PARALLEL_JOB` and `BUILDKITE_PARALLEL_JOB_COUNT` environment variables:
  
  