anchor.diff:  <tbody>
     <tr>
       <th><code>branch_configuration</code></th>
  -    <td>A <a href="/docs/pipelines/branch-configuration#pipeline-level-branch-filtering">branch filter pattern</a> to limit which pushed branches trigger builds on this pipeline.<p class="Docs__api-param-eg"><em>Example:</em> <code>"master feature/*"</code><br><em>Default:</em> <code>null</code></p></td>
  +    <td>
  +      <p>A <a href="/docs/pipelines/branch-configuration#pipeline-level-branch-filtering">branch filter pattern</a> to limit which pushed branches trigger builds on this pipeline.</p>
  +      <p><em>Example:</em> <code>"master feature/*"</code><br><em>Default:</em> <code>null</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>cancel_running_branch_builds</code></th>
  -    <td>Cancel intermediate builds. When a new build is created on a branch, any previous builds that are running on the same branch will be automatically canceled.<p class="Docs__api-param-eg"><em>Example:</em> <code>true</code><br><em>Default:</em> <code>false</code></p></td>
  +    <td>
  +      <p>Cancel intermediate builds. When a new build is created on a branch, any previous builds that are running on the same branch will be automatically canceled.</p>
  +      <p><em>Example:</em> <code>true</code><br><em>Default:</em> <code>false</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>cancel_running_branch_builds_filter</code></th>
  -    <td>A <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch filter pattern</a> to limit which branches intermediate build cancelling applies to. <p class="Docs__api-param-eg"><em>Example:</em> <code>"develop prs/*"</code><br><em>Default:</em> <code>null</code></p></td>
  +    <td>
  +      <p>A <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch filter pattern</a> to limit which branches intermediate build cancelling applies to.</p>
  +      <p><em>Example:</em> <code>"develop prs/*"</code><br><em>Default:</em> <code>null</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>default_branch</code></th>
  -    <td>The name of the branch to prefill when new builds are created or triggered in Buildkite. It is also used to filter the builds and metrics shown on the Pipelines page.
  -      <p class="Docs__api-param-eg"><em>Example:</em> <code>"master"</code></p>
  +    <td>
  +      <p>The name of the branch to prefill when new builds are created or triggered in Buildkite. It is also used to filter the builds and metrics shown on the Pipelines page.</p>
  +      <p><em>Example:</em> <code>"master"</code></p>
       </td>
     </tr>
     <tr>
       <th><code>description</code></th>
  -    <td>The pipeline description. <p class="Docs__api-param-eg"><em>Example:</em> <code>":package: A testing pipeline"</code></p></td>
  +    <td>
  +      <p>The pipeline description.</p>
  +      <p><em>Example:</em> <code>":package: A testing pipeline"</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>env</code></th>
  -    <td>The pipeline environment variables. <p class="Docs__api-param-eg"><em>Example:</em> <code>{"KEY":"value"}</code></p></td>
  +    <td>
  +      <p>The pipeline environment variables.</p>
  +      <p><em>Example:</em> <code>{"KEY":"value"}</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>provider_settings</code></th>
  -    <td>The source provider settings. See the <a href="#provider-settings-properties">Provider Settings</a> section for accepted properties. <p class="Docs__api-param-eg"><em>Example:</em> <code>{ "publish_commit_status": true, "build_pull_request_forks": true }</code></p></td>
  +    <td>
  +      <p>The source provider settings. See the <a href="#provider-settings-properties">Provider Settings</a> section for accepted properties.</p>
  +      <p><em>Example:</em> <code>{ "publish_commit_status": true, "build_pull_request_forks": true }</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>skip_queued_branch_builds</code></th>
  -    <td>Skip intermediate builds. When a new build is created on a branch, any previous builds that haven't yet started on the same branch will be automatically marked as skipped.<p class="Docs__api-param-eg"><em>Example:</em> <code>true</code><br><em>Default:</em> <code>false</code></p></td>
  +    <td>
  +      <p>Skip intermediate builds. When a new build is created on a branch, any previous builds that haven't yet started on the same branch will be automatically marked as skipped.</p>
  +      <p><em>Example:</em> <code>true</code><br><em>Default:</em> <code>false</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>skip_queued_branch_builds_filter</code></th>
  -    <td>A <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch filter pattern</a> to limit which branches intermediate build skipping applies to. <p class="Docs__api-param-eg"><em>Example:</em> <code>"!master"</code><br><em>Default:</em> <code>null</code></p></td>
  +    <td>
  +      <p>A <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch filter pattern</a> to limit which branches intermediate build skipping applies to.</p>
  +      <p><em>Example:</em> <code>"!master"</code><br><em>Default:</em> <code>null</code></p>
  +    </td>
     </tr>
     <tr>
       <th><code>teams</code></th>
  -    <td>An array of team UUIDs to add this pipeline to. Allows you to specify the access level for the pipeline in a team. The available access level options are <code>read_only</code>, <code>build_and_read</code>, and <code>manage_build_and_read</code> You can find your team's UUID either using the <a href="/docs/apis/graphql-api">GraphQL API</a>, or on the settings page for a team. This property is only available if your organization has enabled Teams. Replaces deprecated <code>team_uuids</code> parameter.<p><em>Example:</em></p>
  +    <td>
  +      <p>An array of team UUIDs to add this pipeline to. Allows you to specify the access level for the pipeline in a team. The available access level options are <code>read_only</code>, <code>build_and_read</code>, and <code>manage_build_and_read</code> You can find your team's UUID either using the <a href="/docs/apis/graphql-api">GraphQL API</a>, or on the settings page for a team. This property is only available if your organization has enabled Teams. Replaces deprecated <code>team_uuids</code> parameter.</p>
  +      <p><em>Example:</em></p>
         <%= render_markdown text: %{
   ```javascript
   teams: {
  
positive.code:     </td>
    </tr>
    <tr>
    <th><code>visibility</code></th>
    <td>Whether the pipeline is visible to everyone, including users outside this organization. <p class="Docs__api-param-eg"><em>Example:</em> <code>"public"</code><br><em>Default:</em> <code>"private"</code></p></td>
  </tr>
  </tbody>
  </table>
  
  
negative.code: <tbody>
    <tr>
      <th><code>branch_configuration</code></th>
      <td>
        <p>A <a href="/docs/pipelines/branch-configuration#pipeline-level-branch-filtering">branch filter pattern</a> to limit which pushed branches trigger builds on this pipeline.</p>
        <p><em>Example:</em> <code>"master feature/*"</code><br><em>Default:</em> <code>null</code></p>
      </td>
    </tr>
    <tr>
      <th><code>cancel_running_branch_builds</code></th>
      <td>
        <p>Cancel intermediate builds. When a new build is created on a branch, any previous builds that are running on the same branch will be automatically canceled.</p>
        <p><em>Example:</em> <code>true</code><br><em>Default:</em> <code>false</code></p>
      </td>
    </tr>
    <tr>
      <th><code>cancel_running_branch_builds_filter</code></th>
      <td>
        <p>A <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch filter pattern</a> to limit which branches intermediate build cancelling applies to.</p>
        <p><em>Example:</em> <code>"develop prs/*"</code><br><em>Default:</em> <code>null</code></p>
      </td>
    </tr>
    <tr>
      <th><code>default_branch</code></th>
      <td>
        <p>The name of the branch to prefill when new builds are created or triggered in Buildkite. It is also used to filter the builds and metrics shown on the Pipelines page.</p>
        <p><em>Example:</em> <code>"master"</code></p>
      </td>
    </tr>
    <tr>
      <th><code>description</code></th>
      <td>
        <p>The pipeline description.</p>
        <p><em>Example:</em> <code>":package: A testing pipeline"</code></p>
      </td>
    </tr>
    <tr>
      <th><code>provider_settings</code></th>
      <td>
        <p>The source provider settings. See the <a href="#provider-settings-properties">Provider Settings</a> section for accepted properties.</p>
        <p><em>Example:</em> <code>{ "publish_commit_status": true, "build_pull_request_forks": true }</code></p>
      </td>
    </tr>
    <tr>
      <th><code>skip_queued_branch_builds</code></th>
      <td>
        <p>Skip intermediate builds. When a new build is created on a branch, any previous builds that haven't yet started on the same branch will be automatically marked as skipped.</p>
        <p><em>Example:</em> <code>true</code><br><em>Default:</em> <code>false</code></p>
      </td>
    </tr>
    <tr>
      <th><code>skip_queued_branch_builds_filter</code></th>
      <td>
        <p>A <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch filter pattern</a> to limit which branches intermediate build skipping applies to.</p>
        <p><em>Example:</em> <code>"!master"</code><br><em>Default:</em> <code>null</code></p>
      </td>
    </tr>
    <tr>
      <th><code>teams</code></th>
      <td>
        <p>An array of team UUIDs to add this pipeline to. Allows you to specify the access level for the pipeline in a team. The available access level options are <code>read_only</code>, <code>build_and_read</code>, and <code>manage_build_and_read</code> You can find your team's UUID either using the <a href="/docs/apis/graphql-api">GraphQL API</a>, or on the settings page for a team. This property is only available if your organization has enabled Teams. Replaces deprecated <code>team_uuids</code> parameter.</p>
        <p><em>Example:</em></p>
        <%= render_markdown text: %{
  ```javascript
  teams: {
  