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-stream"</code>
       </td>
     </tr>
     <tr>
       <td><code>options</code></td>
       <td>
  -      The list of select field options. For 6 or less options they’ll be shown as radio buttons, otherwise they'll be shown in a select-style dropdown.
  +      The list of select field options. For 6 or less options they’ll be displayed as radio buttons, otherwise they'll be displayed in a dropdown box.
       </td>
     </tr>
   </table>
  
positive.code:   <tr>
      <td><code>hint</code></td>
      <td>
        The explanatory text to show after the label.<br>
        <em>Example:</em> <code>"What’s the code name for this release? \:name_badge\:"</code>
      </td>
    </tr>
    <tr>
      <td><code>required</code></td>
      <td>
        Whether the field is required to be filled out.<br>
        <em>Default value:</em> <code>true</code>
      </td>
    </tr>
    <tr>
      <td><code>default</code></td>
      <td>
        The text field’s prefilled text.<br>
        <em>Example:</em> <code>"Flying Dolphin"</code>
      </td>
    </tr>
  
negative.code:   <tr>
      <td><code>fields</code></td>
      <td>
        A list of input fields required to be filled out before unblocking the step.<br>
        Available input field types: <code>text</code>, <code>select</code>
      </td>
    </tr>
    <tr>
      <td><code>branches</code></td>
      <td>
        The <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch pattern</a> defining which branches will include this block step in their builds.<br>
        <em>Example:</em> <code>"master stable/*"</code>
      </td>
    </tr>
  