anchor.diff:    <tr>
       <td><code>key</code></td>
       <td>
  -      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>
  +      The meta-data key that stores the field's input (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: 
  <%= toc %>
  
  Simple block steps can be defined in your pipeline settings, or in your [pipeline.yml](/docs/pipelines/uploading-pipelines) file.
  
  Block steps that request additional input are defined in your repository's [pipeline.yml](/docs/pipelines/uploading-pipelines). You can access the answers your team provide in the [build meta-data](/docs/builds/build-meta-data) on subsequent steps.
  
  <%= image "click-prompt-example-animated.gif", width: 944/2, height: 826/2, alt: "Animated screenshot of a block step with input fields" %>
  
  
negative.code:   <tr>
      <td><code>required</code></td>
      <td>
        A boolean value that defines whether the field is required for form submission.<br>
        <em>Default:</em> <code>true</code>
      </td>
    </tr>
    <tr>
      <td><code>default</code></td>
      <td>
        The value of the option that will be pre-selected in the dropdown.<br>
        <em>Example:</em> <code>"beta"</code>
      </td>
    </tr>
  