anchor.diff:  # Deployments with Buildkite
   
  -There are many ways to deploy your code and infrastructure using Buildkite. If you're already working with a dedicated deployment system, this can be integrated with your Buildkite pipelines, or you can deploy using Buildkite Agents from either your test pipeline or a dedicated deployment pipeline.
  +There are many ways to set up both manual and continuous deployment workflows using Buildkite.
   
   <%= toc %>
   
  -## Adding a deployment step
  +## Single deployment steps
   
  -The simplest way to perform deployments is to add an additional deploy step to your pipeline, and to make use of [step-level branch filtering](http://localhost:3000/docs/pipelines/branch-configuration#step-level-branch-filtering).
  +Adding a deployment step that runs after your tests pass is the simplest way to deploy from a Buildkite pipeline.
   
  -For example, the following pipeline includes a deployment step that runs after the tests pass. The deploy step is only included on `master` builds, and uses [concurrency limiting](/docs/pipelines/controlling-concurrency) to ensure only one deployment is run at a time:
  +The following example shows how to set up continuous deployment using a single step that runs after the tests pass. It uses [step-level branch filtering](/docs/pipelines/branch-configuration#step-level-branch-filtering) to perform continuous deployment on `master` branch builds, and uses [concurrency limiting](/docs/pipelines/controlling-concurrency) to ensure only one deployment runs at a time.
   
   ```yml
   steps:
     - label: ":hammer:"
       command: "scripts/test"
  +  
     - wait
  +  
     - label: ":rocket:"
       command: "scripts/deploy"
       branches: "master"
  
positive.code: 
  <screenshot of a deploy pipeline>
  
  ## External deployment systems
  
  - can use anything for deployments like spinnaker, shipit, samson
  
negative.code: steps:
    - label: ":hammer:"
      command: "scripts/test"
  
    - wait
  
    - label: ":rocket:"
      trigger: "my-app-deployment"
      branches: "master"
  