anchor.diff:  
   ```yml
   steps:
  -  - input: "Ask a question"
  +  - input: "What is the name of this release?"
   ```
   
   An [input step](/docs/pipelines/input-step) provides the same functionality as the block step, but doesn't create the implicit dependencies that a block step creates.
  
positive.code: 
  ```yml
  steps:
    - command: "a.sh"
    - command: "b.sh"
    - wait
    - command: "c.sh"
    - command: "d.sh"
  ```
  
  [Block steps](/docs/pipelines/block-step) perform the same function, but also require unblocking either manually or via an API call before the rest of the steps can be run.
  
negative.code: 
  ```yml
  steps:
    - command: "tests.sh"
      key: "tests"
    - command: "build.sh"
      key: "build"
      depends_on: "tests"
  ```
  
  In the above example, the second command step (build) will not run until the first command step (tests) has completed. Without the `depends_on` attribute, and given enough agents, these steps would run in parallel.
  
  To ensure that a step is not dependent on any other step, add an explicit empty dependency with the `~` character. This also ensures that the step will run immediately at the start of the build:
  
  ```yml
  steps:
    - command: "tests.sh"
    - wait
    - command: "lint.sh"
      depends_on: ~
  ```
  
  