anchor.diff:    <tr>
       <td><code>key</code></td>
       <td>
  -      The slug to identify the field for later access via the buildkite-agent meta-data command.<br>
  +      The meta-data key used to later retrieve the value (e.g. via the <a href="/docs/agent/cli-meta-data">buildkite-agent meta-data command</a>)<br>
         <em>Example:</em> <code>"release-name"</code>
       </td>
     </tr>
  
positive.code: 
  <%= image "click-prompt-example-animated.gif", width: 944/2, height: 826/2, alt: "Animated screenshot of a block step with input fields" %>
  
  For a more complete example, see the Block Step example pipeline:
  
  <a class="Docs__example-repo" href="https://github.com/buildkite/block-step-example">:pipeline: Block Step Example Pipeline<span class="repo">github.com/buildkite/block-step-example</span></a>
  
  
negative.code: 
  <%= image "click-example.png", width: 338/2, height: 154/2, alt: "Screenshot of clicking a block step" %>
  
  Block steps that request additional input can be created using the [pipeline.yml](/docs/pipelines/uploading-pipelines) version, allowing you to later retrieve the answers via [build meta-data](/docs/builds/build-meta-data):
  
  ```yml
  steps:
  