From e48a727090c396ed45f2d8772b19bbb30a780ad5 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 11 May 2026 10:01:22 +0000
Subject: [PATCH] chore: update documentation from upstream Bazel repo [skip
 ci]

Synchronized pre-converted MDX files from upstream Bazel repository.
---
 external/vendor.mdx                          | 16 ------
 navigation.json                              |  8 +++
 reference/command-line-reference.mdx         | 51 +++++++++++-------
 release/index.mdx                            |  2 +-
 rules/lib/builtins/ToolchainContext.mdx      | 14 +----
 rules/lib/builtins/module_ctx.mdx            |  4 +-
 rules/lib/builtins/repository_ctx.mdx        |  4 +-
 rules/lib/fragments.mdx                      |  1 +
 rules/lib/overview.mdx                       |  1 +
 rules/lib/repo/git.mdx                       | 44 ++--------------
 upstream                                     |  2 +-
 versions/8.0.1/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/8.1.1/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/8.2.1/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/8.3.1/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/8.4.2/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/8.5.1/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/8.6.0/reference/flag-cheatsheet.mdx | 52 +++++++++----------
 versions/9.0.0/reference/flag-cheatsheet.mdx | 54 ++++++++++----------
 versions/9.1.0/reference/flag-cheatsheet.mdx | 54 ++++++++++----------
 20 files changed, 290 insertions(+), 329 deletions(-)

diff --git a/external/vendor.mdx b/external/vendor.mdx
index f02e94a2..ab82c46c 100644
--- a/external/vendor.mdx
+++ b/external/vendor.mdx
@@ -95,22 +95,6 @@ Note that vendoring all dependencies has a few **disadvantages**:
 
 Therefore, consider vendoring for specific targets first.
 
-### Vendor tools for Bazel subcommands {#vendor-tools-for-subcommands}
-
-Some Bazel subcommands (such as `bazel mod tidy`) have implicit tool
-dependencies that are not reachable from user build targets, so they are
-**not** included by `bazel vendor //...`. To vendor those tools as well, add
-the `@bazel_tools//tools:tools_for_bazel_subcommands` filegroup to your
-vendor invocation:
-
-```none
-bazel vendor //... @bazel_tools//tools:tools_for_bazel_subcommands
-```
-
-This is required if you plan to run commands like `bazel mod tidy` in an
-offline or hermetic environment (for example with `--vendor_dir` and
-`--nofetch`).
-
 ## Configure vendor mode with VENDOR.bazel {#configure-vendor-mode}
 
 You can control how given repos are handled with the VENDOR.bazel file located
diff --git a/navigation.json b/navigation.json
index 99f6ff9e..a3d046ca 100644
--- a/navigation.json
+++ b/navigation.json
@@ -87,6 +87,14 @@
           "$ref": "./navigation/7.7.en.json"
         }
       ]
+    },
+    {
+      "version": "6.5",
+      "languages": [
+        {
+          "$ref": "./navigation/6.5.en.json"
+        }
+      ]
     }
   ]
 }
diff --git a/reference/command-line-reference.mdx b/reference/command-line-reference.mdx
index 6f51089e..0f00cb9d 100644
--- a/reference/command-line-reference.mdx
+++ b/reference/command-line-reference.mdx
@@ -1470,6 +1470,15 @@ Remote caching and execution options:
 `--[no]experimental_remote_discard_merkle_trees` default: "true"
 :   If set to true, discard in-memory copies of the input root's Merkle tree and associated input mappings during calls to GetActionResult() and Execute(). This reduces memory usage significantly, but does require Bazel to recompute them upon remote cache misses and retries.
 
+`--experimental_remote_downloader=<a string>` default: see description
+:   A Remote Asset API endpoint URI, to be used as a remote download proxy. The supported schemes are grpc, grpcs (grpc with TLS enabled) and unix (local UNIX sockets). If no scheme is provided Bazel will default to grpcs. See: https://github.com/bazelbuild/remote-apis/blob/master/build/bazel/remote/asset/v1/remote_asset.proto
+
+`--[no]experimental_remote_downloader_local_fallback` default: "false"
+:   Whether to fall back to the local downloader if remote downloader fails.
+
+`--[no]experimental_remote_downloader_propagate_credentials` default: "false"
+:   Whether to propagate credentials from netrc and credential helper to the remote downloader server. The server implementation needs to support the new `http_header_url:<url-index>:<header-key>` qualifier where the `<url-index>` is a 0-based position of the URL inside the FetchBlobRequest's `uris` field. The URL-specific headers should take precedence over the global headers.
+
 `--experimental_remote_failure_rate_threshold=<an integer in 0-100 range>` default: "10"
 :   Sets the allowed number of failure rate in percentage for a specific time window after which it stops calling to the remote cache/executor. By default the value is 10. Setting this to 0 means no limitation.
 
@@ -1549,18 +1558,9 @@ Remote caching and execution options:
     Tags:
     [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS)
 
-`--remote_downloader=<a string>` default: see description
-:   A Remote Asset API endpoint URI, to be used as a remote download proxy. The supported schemes are grpc, grpcs (grpc with TLS enabled) and unix (local UNIX sockets). If no scheme is provided Bazel will default to grpcs. See: https://github.com/bazelbuild/remote-apis/blob/master/build/bazel/remote/asset/v1/remote_asset.proto
-
 `--remote_downloader_header=<a 'name=value' assignment>` multiple uses are accumulated
 :   Specify a header that will be included in remote downloader requests: --remote_downloader_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.
 
-`--[no]remote_downloader_local_fallback` default: "false"
-:   Whether to fall back to the local downloader if remote downloader fails.
-
-`--[no]remote_downloader_propagate_credentials` default: "false"
-:   Whether to propagate credentials from netrc and credential helper to the remote downloader server. The server implementation needs to support the new `http_header_url:<url-index>:<header-key>` qualifier where the `<url-index>` is a 0-based position of the URL inside the FetchBlobRequest's `uris` field. The URL-specific headers should take precedence over the global headers.
-
 `--remote_exec_header=<a 'name=value' assignment>` multiple uses are accumulated
 :   Specify a header that will be included in execution requests: --remote_exec_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.
 
@@ -3397,6 +3397,9 @@ Miscellaneous options, not otherwise categorized.:
     Tags:
     [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE)
 
+`--j2objc_translation_flags=<comma-separated list of options>` multiple uses are accumulated
+:   Additional options to pass to the J2ObjC tool.
+
 `--java_debug`
 :   Causes the Java virtual machine of a java test to wait for a connection from a JDWP-compliant debugger (such as jdb) before starting the test. Implies -test_output=streamed.
 
@@ -4434,6 +4437,15 @@ Remote caching and execution options:
 `--[no]experimental_remote_discard_merkle_trees` default: "true"
 :   If set to true, discard in-memory copies of the input root's Merkle tree and associated input mappings during calls to GetActionResult() and Execute(). This reduces memory usage significantly, but does require Bazel to recompute them upon remote cache misses and retries.
 
+`--experimental_remote_downloader=<a string>` default: see description
+:   A Remote Asset API endpoint URI, to be used as a remote download proxy. The supported schemes are grpc, grpcs (grpc with TLS enabled) and unix (local UNIX sockets). If no scheme is provided Bazel will default to grpcs. See: https://github.com/bazelbuild/remote-apis/blob/master/build/bazel/remote/asset/v1/remote_asset.proto
+
+`--[no]experimental_remote_downloader_local_fallback` default: "false"
+:   Whether to fall back to the local downloader if remote downloader fails.
+
+`--[no]experimental_remote_downloader_propagate_credentials` default: "false"
+:   Whether to propagate credentials from netrc and credential helper to the remote downloader server. The server implementation needs to support the new `http_header_url:<url-index>:<header-key>` qualifier where the `<url-index>` is a 0-based position of the URL inside the FetchBlobRequest's `uris` field. The URL-specific headers should take precedence over the global headers.
+
 `--experimental_remote_failure_rate_threshold=<an integer in 0-100 range>` default: "10"
 :   Sets the allowed number of failure rate in percentage for a specific time window after which it stops calling to the remote cache/executor. By default the value is 10. Setting this to 0 means no limitation.
 
@@ -4513,18 +4525,9 @@ Remote caching and execution options:
     Tags:
     [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS)
 
-`--remote_downloader=<a string>` default: see description
-:   A Remote Asset API endpoint URI, to be used as a remote download proxy. The supported schemes are grpc, grpcs (grpc with TLS enabled) and unix (local UNIX sockets). If no scheme is provided Bazel will default to grpcs. See: https://github.com/bazelbuild/remote-apis/blob/master/build/bazel/remote/asset/v1/remote_asset.proto
-
 `--remote_downloader_header=<a 'name=value' assignment>` multiple uses are accumulated
 :   Specify a header that will be included in remote downloader requests: --remote_downloader_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.
 
-`--[no]remote_downloader_local_fallback` default: "false"
-:   Whether to fall back to the local downloader if remote downloader fails.
-
-`--[no]remote_downloader_propagate_credentials` default: "false"
-:   Whether to propagate credentials from netrc and credential helper to the remote downloader server. The server implementation needs to support the new `http_header_url:<url-index>:<header-key>` qualifier where the `<url-index>` is a 0-based position of the URL inside the FetchBlobRequest's `uris` field. The URL-specific headers should take precedence over the global headers.
-
 `--remote_exec_header=<a 'name=value' assignment>` multiple uses are accumulated
 :   Specify a header that will be included in execution requests: --remote_exec_header=Name=Value. Multiple headers can be passed by specifying the flag multiple times. Multiple values for the same name will be converted to a comma-separated list.
 
@@ -6063,6 +6066,9 @@ Miscellaneous options, not otherwise categorized.:
     Tags:
     [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE)
 
+`--j2objc_translation_flags=<comma-separated list of options>` multiple uses are accumulated
+:   Additional options to pass to the J2ObjC tool.
+
 `--java_debug`
 :   Causes the Java virtual machine of a java test to wait for a connection from a JDWP-compliant debugger (such as jdb) before starting the test. Implies -test_output=streamed.
 
@@ -7874,6 +7880,9 @@ Miscellaneous options, not otherwise categorized.:
     Tags:
     [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE)
 
+`--j2objc_translation_flags=<comma-separated list of options>` multiple uses are accumulated
+:   Additional options to pass to the J2ObjC tool.
+
 `--java_debug`
 :   Causes the Java virtual machine of a java test to wait for a connection from a JDWP-compliant debugger (such as jdb) before starting the test. Implies -test_output=streamed.
 
@@ -9506,6 +9515,9 @@ Miscellaneous options, not otherwise categorized.:
     Tags:
     [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE)
 
+`--j2objc_translation_flags=<comma-separated list of options>` multiple uses are accumulated
+:   Additional options to pass to the J2ObjC tool.
+
 `--java_debug`
 :   Causes the Java virtual machine of a java test to wait for a connection from a JDWP-compliant debugger (such as jdb) before starting the test. Implies -test_output=streamed.
 
@@ -12496,6 +12508,9 @@ Miscellaneous options, not otherwise categorized.:
     Tags:
     [`loading_and_analysis`](#effect_tag_LOADING_AND_ANALYSIS), [`incompatible_change`](#metadata_tag_INCOMPATIBLE_CHANGE)
 
+`--j2objc_translation_flags=<comma-separated list of options>` multiple uses are accumulated
+:   Additional options to pass to the J2ObjC tool.
+
 `--java_debug`
 :   Causes the Java virtual machine of a java test to wait for a connection from a JDWP-compliant debugger (such as jdb) before starting the test. Implies -test_output=streamed.
 
diff --git a/release/index.mdx b/release/index.mdx
index 6fb24547..822c08f5 100644
--- a/release/index.mdx
+++ b/release/index.mdx
@@ -15,7 +15,7 @@ information about Bazel's release model.
 | ----------- | ------------- | -------------- | -------------- |
 | Bazel 10 | Rolling| [Check rolling release page](/release/rolling) | N/A |
 | Bazel 9 | Active| [9.1.0](https://github.com/bazelbuild/bazel/releases/tag/9.1.0) | Dec 2028 |
-| Bazel 8 | Maintenance| [8.7.0](https://github.com/bazelbuild/bazel/releases/tag/8.7.0) | Dec 2027 |
+| Bazel 8 | Maintenance| [8.6.0](https://github.com/bazelbuild/bazel/releases/tag/8.6.0) | Dec 2027 |
 | Bazel 7 | Maintenance| [7.7.1](https://github.com/bazelbuild/bazel/releases/tag/7.7.1) | Dec 2026 |
 | Bazel 6 | Deprecated | [6.6.0](https://github.com/bazelbuild/bazel/releases/tag/6.6.0) | Dec 2025 |
 | Bazel 5 | Deprecated | [5.4.1](https://github.com/bazelbuild/bazel/releases/tag/5.4.1) | Jan 2025 |
diff --git a/rules/lib/builtins/ToolchainContext.mdx b/rules/lib/builtins/ToolchainContext.mdx
index 24326f9a..d792e7e6 100644
--- a/rules/lib/builtins/ToolchainContext.mdx
+++ b/rules/lib/builtins/ToolchainContext.mdx
@@ -2,16 +2,4 @@
 title: 'ToolchainContext'
 ---
 
-Holds toolchains available for a particular exec group. Toolchain targets are accessed by indexing with the toolchain type, as in `ctx.toolchains["//pkg:my_toolchain_type"]`. If the toolchain was optional and no toolchain was resolved, this will return `None`. Accessing toolchains of an aspect or rule via `ctx.toolchains` returns the indexed toolchain as a `ToolchainInfo` provider. While when using aspects, `ToolchainContext` is also used to hold the toolchains of the base target. It can be accessed by `ctx.rule.toolchains["//pkg:my_toolchain_type"]` and it returns the list of providers resulted from applying the aspects on these toolchain targets.
-
-## Members
-
-* [toolchain_types](#toolchain_types)
-
-## toolchain_types
-
-```
-sequence ToolchainContext.toolchain_types()
-```
-
-Returns the resolved toolchain type labels.
\ No newline at end of file
+Holds toolchains available for a particular exec group. Toolchain targets are accessed by indexing with the toolchain type, as in `ctx.toolchains["//pkg:my_toolchain_type"]`. If the toolchain was optional and no toolchain was resolved, this will return `None`. Accessing toolchains of an aspect or rule via `ctx.toolchains` returns the indexed toolchain as a `ToolchainInfo` provider. While when using aspects, `ToolchainContext` is also used to hold the toolchains of the base target. It can be accessed by `ctx.rule.toolchains["//pkg:my_toolchain_type"]` and it returns the list of providers resulted from applying the aspects on these toolchain targets.
\ No newline at end of file
diff --git a/rules/lib/builtins/module_ctx.mdx b/rules/lib/builtins/module_ctx.mdx
index 062d6de4..40a4bb62 100644
--- a/rules/lib/builtins/module_ctx.mdx
+++ b/rules/lib/builtins/module_ctx.mdx
@@ -31,7 +31,7 @@ The context of the module extension containing helper functions and information
 unknown module_ctx.download(url, output='', sha256='', executable=False, allow_fail=False, canonical_id='', auth={}, headers={}, *, integrity='', block=True)
 ```
 
-Downloads a file to the output path for the provided url and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`, as well as `size_bytes`, which contains the size of the downloaded file in bytes as an integer. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
+Downloads a file to the output path for the provided url and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
 
 ### Parameters
 
@@ -54,7 +54,7 @@ Downloads a file to the output path for the provided url and returns a struct co
 struct module_ctx.download_and_extract(url, output='', sha256='', type='', strip_prefix='', allow_fail=False, canonical_id='', auth={}, headers={}, *, integrity='', rename_files={}, strip_components=0)
 ```
 
-Downloads a file to the output path for the provided url, extracts it, and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`, as well as the `size_bytes` of the downloaded file in bytes as an integer. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
+Downloads a file to the output path for the provided url, extracts it, and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
 
 ### Parameters
 
diff --git a/rules/lib/builtins/repository_ctx.mdx b/rules/lib/builtins/repository_ctx.mdx
index de749cac..abb48faf 100644
--- a/rules/lib/builtins/repository_ctx.mdx
+++ b/rules/lib/builtins/repository_ctx.mdx
@@ -58,7 +58,7 @@ Deletes a file or a directory. Returns a bool, indicating whether the file or di
 unknown repository_ctx.download(url, output='', sha256='', executable=False, allow_fail=False, canonical_id='', auth={}, headers={}, *, integrity='', block=True)
 ```
 
-Downloads a file to the output path for the provided url and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`, as well as `size_bytes`, which contains the size of the downloaded file in bytes as an integer. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
+Downloads a file to the output path for the provided url and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
 
 ### Parameters
 
@@ -81,7 +81,7 @@ Downloads a file to the output path for the provided url and returns a struct co
 struct repository_ctx.download_and_extract(url, output='', sha256='', type='', strip_prefix='', allow_fail=False, canonical_id='', auth={}, headers={}, *, integrity='', rename_files={}, strip_components=0)
 ```
 
-Downloads a file to the output path for the provided url, extracts it, and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`, as well as the `size_bytes` of the downloaded file in bytes as an integer. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
+Downloads a file to the output path for the provided url, extracts it, and returns a struct containing `success`, a flag which is `true` if the download completed successfully, and if successful, a hash of the file with the fields `sha256` and `integrity`. If the value of the `success` field is false, the `error` field will be set with a message indicating why the download failed. The message in the `error` field is for debugging purposes only and should not be relied upon as a stable API (the format of the string can change between patch versions of Bazel). When `sha256` or `integrity` is user specified, setting an explicit `canonical_id` is highly recommended. e.g. [`get_default_canonical_id`](/rules/lib/repo/cache#get_default_canonical_id)
 
 ### Parameters
 
diff --git a/rules/lib/fragments.mdx b/rules/lib/fragments.mdx
index bdd63e7b..8b497627 100644
--- a/rules/lib/fragments.mdx
+++ b/rules/lib/fragments.mdx
@@ -10,6 +10,7 @@ Rule implementations can get them using `ctx.fragments.[fragment name]`
 * [bazel_android](/rules/lib/fragments/bazel_android)
 * [coverage](/rules/lib/fragments/coverage)
 * [cpp](/rules/lib/fragments/cpp)
+* [j2objc](/rules/lib/fragments/j2objc)
 * [java](/rules/lib/fragments/java)
 * [objc](/rules/lib/fragments/objc)
 * [platform](/rules/lib/fragments/platform)
diff --git a/rules/lib/overview.mdx b/rules/lib/overview.mdx
index dcd67501..307d2da4 100644
--- a/rules/lib/overview.mdx
+++ b/rules/lib/overview.mdx
@@ -17,6 +17,7 @@ title: 'One-Page Overview'
 * [bazel_android](/rules/lib/fragments/bazel_android)
 * [coverage](/rules/lib/fragments/coverage)
 * [cpp](/rules/lib/fragments/cpp)
+* [j2objc](/rules/lib/fragments/j2objc)
 * [java](/rules/lib/fragments/java)
 * [objc](/rules/lib/fragments/objc)
 * [platform](/rules/lib/fragments/platform)
diff --git a/rules/lib/repo/git.mdx b/rules/lib/repo/git.mdx
index 780915ab..28f2632a 100644
--- a/rules/lib/repo/git.mdx
+++ b/rules/lib/repo/git.mdx
@@ -14,9 +14,9 @@ Rules for cloning external git repositories.
 <pre>
 load("@bazel//tools/build_defs/repo:git.bzl", "git_repository")
 
-git_repository(<a href="#git_repository-name">name</a>, <a href="#git_repository-add_prefix">add_prefix</a>, <a href="#git_repository-branch">branch</a>, <a href="#git_repository-build_file">build_file</a>, <a href="#git_repository-build_file_content">build_file_content</a>, <a href="#git_repository-canonical_id">canonical_id</a>, <a href="#git_repository-commit">commit</a>,
-               <a href="#git_repository-init_submodules">init_submodules</a>, <a href="#git_repository-patch_args">patch_args</a>, <a href="#git_repository-patch_cmds">patch_cmds</a>, <a href="#git_repository-patch_cmds_win">patch_cmds_win</a>, <a href="#git_repository-patch_strip">patch_strip</a>, <a href="#git_repository-patch_tool">patch_tool</a>,
-               <a href="#git_repository-patches">patches</a>, <a href="#git_repository-recursive_init_submodules">recursive_init_submodules</a>, <a href="#git_repository-remote">remote</a>, <a href="#git_repository-remote_module_file_integrity">remote_module_file_integrity</a>,
+git_repository(<a href="#git_repository-name">name</a>, <a href="#git_repository-branch">branch</a>, <a href="#git_repository-build_file">build_file</a>, <a href="#git_repository-build_file_content">build_file_content</a>, <a href="#git_repository-canonical_id">canonical_id</a>, <a href="#git_repository-commit">commit</a>, <a href="#git_repository-init_submodules">init_submodules</a>,
+               <a href="#git_repository-patch_args">patch_args</a>, <a href="#git_repository-patch_cmds">patch_cmds</a>, <a href="#git_repository-patch_cmds_win">patch_cmds_win</a>, <a href="#git_repository-patch_strip">patch_strip</a>, <a href="#git_repository-patch_tool">patch_tool</a>, <a href="#git_repository-patches">patches</a>,
+               <a href="#git_repository-recursive_init_submodules">recursive_init_submodules</a>, <a href="#git_repository-remote">remote</a>, <a href="#git_repository-remote_module_file_integrity">remote_module_file_integrity</a>,
                <a href="#git_repository-remote_module_file_urls">remote_module_file_urls</a>, <a href="#git_repository-remote_patch_strip">remote_patch_strip</a>, <a href="#git_repository-remote_patches">remote_patches</a>, <a href="#git_repository-shallow_since">shallow_since</a>,
                <a href="#git_repository-sparse_checkout_file">sparse_checkout_file</a>, <a href="#git_repository-sparse_checkout_patterns">sparse_checkout_patterns</a>, <a href="#git_repository-strip_prefix">strip_prefix</a>, <a href="#git_repository-tag">tag</a>, <a href="#git_repository-verbose">verbose</a>,
                <a href="#git_repository-workspace_file">workspace_file</a>, <a href="#git_repository-workspace_file_content">workspace_file_content</a>)
@@ -64,24 +64,6 @@ The reasons are:
 
 A unique name for this repository.
 
-</p>
-</td>
-</tr>
-<tr id="git_repository-add_prefix">
-<td><code>add_prefix</code></td>
-<td>
-
-String; optional
-
-<p>
-
-Destination directory relative to the repository directory.
-
-The git repo will be cloned into this directory, after applying `strip_prefix`
-(if any) to the file paths within the repo. For example, file
-`foo-1.2.3/src/foo.h` will be cloned to `bar/src/foo.h` if `add_prefix = "bar"`
-and `strip_prefix = "foo-1.2.3"`.
-
 </p>
 </td>
 </tr>
@@ -443,7 +425,7 @@ This repository rule depends on the following environment variables:
 <pre>
 load("@bazel//tools/build_defs/repo:git.bzl", "new_git_repository")
 
-new_git_repository(<a href="#new_git_repository-name">name</a>, <a href="#new_git_repository-add_prefix">add_prefix</a>, <a href="#new_git_repository-branch">branch</a>, <a href="#new_git_repository-build_file">build_file</a>, <a href="#new_git_repository-build_file_content">build_file_content</a>, <a href="#new_git_repository-canonical_id">canonical_id</a>, <a href="#new_git_repository-commit">commit</a>,
+new_git_repository(<a href="#new_git_repository-name">name</a>, <a href="#new_git_repository-branch">branch</a>, <a href="#new_git_repository-build_file">build_file</a>, <a href="#new_git_repository-build_file_content">build_file_content</a>, <a href="#new_git_repository-canonical_id">canonical_id</a>, <a href="#new_git_repository-commit">commit</a>,
                    <a href="#new_git_repository-init_submodules">init_submodules</a>, <a href="#new_git_repository-patch_args">patch_args</a>, <a href="#new_git_repository-patch_cmds">patch_cmds</a>, <a href="#new_git_repository-patch_cmds_win">patch_cmds_win</a>, <a href="#new_git_repository-patch_strip">patch_strip</a>, <a href="#new_git_repository-patch_tool">patch_tool</a>,
                    <a href="#new_git_repository-patches">patches</a>, <a href="#new_git_repository-recursive_init_submodules">recursive_init_submodules</a>, <a href="#new_git_repository-remote">remote</a>, <a href="#new_git_repository-remote_module_file_integrity">remote_module_file_integrity</a>,
                    <a href="#new_git_repository-remote_module_file_urls">remote_module_file_urls</a>, <a href="#new_git_repository-remote_patch_strip">remote_patch_strip</a>, <a href="#new_git_repository-remote_patches">remote_patches</a>, <a href="#new_git_repository-shallow_since">shallow_since</a>,
@@ -471,24 +453,6 @@ Deprecated - use the drop-in replacement 'git_repository' instead
 
 A unique name for this repository.
 
-</p>
-</td>
-</tr>
-<tr id="new_git_repository-add_prefix">
-<td><code>add_prefix</code></td>
-<td>
-
-String; optional
-
-<p>
-
-Destination directory relative to the repository directory.
-
-The git repo will be cloned into this directory, after applying `strip_prefix`
-(if any) to the file paths within the repo. For example, file
-`foo-1.2.3/src/foo.h` will be cloned to `bar/src/foo.h` if `add_prefix = "bar"`
-and `strip_prefix = "foo-1.2.3"`.
-
 </p>
 </td>
 </tr>
diff --git a/upstream b/upstream
index bca007ec..8736593a 160000
--- a/upstream
+++ b/upstream
@@ -1 +1 @@
-Subproject commit bca007ec74f21464115b9175fa217698302ace74
+Subproject commit 8736593a1498bab4964f307595744f463cad22d3
diff --git a/versions/8.0.1/reference/flag-cheatsheet.mdx b/versions/8.0.1/reference/flag-cheatsheet.mdx
index b543ea51..6c406ea6 100644
--- a/versions/8.0.1/reference/flag-cheatsheet.mdx
+++ b/versions/8.0.1/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.0.1/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.0.1/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -308,7 +308,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -333,7 +333,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -412,7 +412,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -427,7 +427,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -480,7 +480,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.0.1/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.0.1/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -494,7 +494,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.0.1/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/8.1.1/reference/flag-cheatsheet.mdx b/versions/8.1.1/reference/flag-cheatsheet.mdx
index 23bb4e1d..462f987f 100644
--- a/versions/8.1.1/reference/flag-cheatsheet.mdx
+++ b/versions/8.1.1/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.1.1/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.1.1/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -308,7 +308,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -333,7 +333,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -412,7 +412,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -427,7 +427,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -480,7 +480,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.1.1/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.1.1/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -494,7 +494,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.1.1/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/8.2.1/reference/flag-cheatsheet.mdx b/versions/8.2.1/reference/flag-cheatsheet.mdx
index 2d18fc13..d8c5b8ca 100644
--- a/versions/8.2.1/reference/flag-cheatsheet.mdx
+++ b/versions/8.2.1/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.2.1/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.2.1/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -308,7 +308,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -333,7 +333,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -412,7 +412,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -427,7 +427,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -480,7 +480,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.2.1/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.2.1/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -494,7 +494,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.2.1/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/8.3.1/reference/flag-cheatsheet.mdx b/versions/8.3.1/reference/flag-cheatsheet.mdx
index 29c33ea3..615ce048 100644
--- a/versions/8.3.1/reference/flag-cheatsheet.mdx
+++ b/versions/8.3.1/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.3.1/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.3.1/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -308,7 +308,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -333,7 +333,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -412,7 +412,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -427,7 +427,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -480,7 +480,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.3.1/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.3.1/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -494,7 +494,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.3.1/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/8.4.2/reference/flag-cheatsheet.mdx b/versions/8.4.2/reference/flag-cheatsheet.mdx
index dd868759..15d54c29 100644
--- a/versions/8.4.2/reference/flag-cheatsheet.mdx
+++ b/versions/8.4.2/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.4.2/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.4.2/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -308,7 +308,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -333,7 +333,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -412,7 +412,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -427,7 +427,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -480,7 +480,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.4.2/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.4.2/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -494,7 +494,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.4.2/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/8.5.1/reference/flag-cheatsheet.mdx b/versions/8.5.1/reference/flag-cheatsheet.mdx
index 6f7944ca..6aba0ae4 100644
--- a/versions/8.5.1/reference/flag-cheatsheet.mdx
+++ b/versions/8.5.1/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.5.1/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.5.1/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -308,7 +308,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -333,7 +333,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -412,7 +412,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -427,7 +427,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -480,7 +480,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.5.1/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.5.1/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -494,7 +494,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.5.1/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/8.6.0/reference/flag-cheatsheet.mdx b/versions/8.6.0/reference/flag-cheatsheet.mdx
index d2539867..03ddc21c 100644
--- a/versions/8.6.0/reference/flag-cheatsheet.mdx
+++ b/versions/8.6.0/reference/flag-cheatsheet.mdx
@@ -22,7 +22,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -36,7 +36,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -48,7 +48,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -69,7 +69,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -171,7 +171,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -194,7 +194,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.6.0/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/8.6.0/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -227,7 +227,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -259,7 +259,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -271,7 +271,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -285,7 +285,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -311,7 +311,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -337,7 +337,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -354,7 +354,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -369,7 +369,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -386,7 +386,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -417,7 +417,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -432,7 +432,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -445,7 +445,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -459,7 +459,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -473,7 +473,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -485,7 +485,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.6.0/docs/user-manual#show-timestamps">`--show-timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/8.6.0/docs/user-manual#show-timestamps">--show-timestamps</a></code></h3>
     </td>
     <td>
 
@@ -499,7 +499,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/8.6.0/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/9.0.0/reference/flag-cheatsheet.mdx b/versions/9.0.0/reference/flag-cheatsheet.mdx
index 5fbf46bf..97deccdf 100644
--- a/versions/9.0.0/reference/flag-cheatsheet.mdx
+++ b/versions/9.0.0/reference/flag-cheatsheet.mdx
@@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -37,7 +37,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -49,7 +49,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -193,7 +193,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/9.0.0/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/9.0.0/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -257,7 +257,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-filter" data-text="test_filter"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--test_filter">`--test_filter`</a></code></h3>
+    <h3 id="flag-test-filter" data-text="test_filter"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--test_filter">--test_filter</a></code></h3>
     </td>
     <td>
 
@@ -300,7 +300,7 @@ debugging. This flag is often used in conjunction with
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -325,7 +325,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -350,7 +350,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -367,7 +367,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -382,7 +382,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -399,7 +399,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -429,7 +429,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -444,7 +444,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -457,7 +457,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -471,7 +471,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -485,7 +485,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -497,7 +497,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/9.0.0/docs/user-manual#show-timestamps">`--show_timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/9.0.0/docs/user-manual#show-timestamps">--show_timestamps</a></code></h3>
     </td>
     <td>
 
@@ -511,7 +511,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/9.0.0/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>
 
diff --git a/versions/9.1.0/reference/flag-cheatsheet.mdx b/versions/9.1.0/reference/flag-cheatsheet.mdx
index ebfea398..6abfef35 100644
--- a/versions/9.1.0/reference/flag-cheatsheet.mdx
+++ b/versions/9.1.0/reference/flag-cheatsheet.mdx
@@ -22,7 +22,7 @@ The following flags are meant to be set explicitly on the command line.
 
   <tr>
     <td>
-      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--config">`--config`</a></code></h3>
+      <h3 id="flag-config" data-text="config"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--config">--config</a></code></h3>
     </td>
     <td>
 
@@ -36,7 +36,7 @@ be selected with <code>--config=<strong>&lt;group&gt;</strong></code>.
 
   <tr>
     <td>
-      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--keep_going">`--keep_going`</a></code></h3>
+      <h3 id="flag-keep-going" data-text="keep_going"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--keep_going">--keep_going</a></code></h3>
     </td>
     <td>
 
@@ -48,7 +48,7 @@ By default, Bazel fails eagerly.
 
   <tr>
     <td>
-      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_download_outputs">`--remote_download_outputs`</a></code></h3>
+      <h3 id="flag-remote-download-outputs" data-text="remote_download_outputs"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_download_outputs">--remote_download_outputs</a></code></h3>
     </td>
     <td>
 
@@ -69,7 +69,7 @@ and intermediate artifacts that are necessary for local actions.
 
   <tr>
     <td>
-      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--stamp">`--stamp`</a></code></h3>
+      <h3 id="flag-stamp" data-text="stamp"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--stamp">--stamp</a></code></h3>
     </td>
     <td>
 
@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors.
 
   <tr>
     <td>
-       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--announce_rc">`--announce_rc`</a></code></h3>
+       <h3 id="flag-announce-rc" data-text="announce_rc"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--announce_rc">--announce_rc</a></code></h3>
     </td>
     <td>
 
@@ -109,7 +109,7 @@ machine-defined, or project-defined <strong>.bazelrc</strong> files.
 
   <tr>
     <td>
-      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--auto_output_filter">`--auto_output_filter`</a></code></h3>
+      <h3 id="flag-auto-output-filter" data-text="auto_output_filter"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--auto_output_filter">--auto_output_filter</a></code></h3>
     </td>
     <td>
 
@@ -124,7 +124,7 @@ command line. To disable all filtering, set
 
   <tr>
     <td>
-      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--sandbox_debug">`--sandbox_debug`</a></code></h3>
+      <h3 id="flag-sandbox-debug" data-text="sandbox_debug"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--sandbox_debug">--sandbox_debug</a></code></h3>
     </td>
     <td>
 
@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our
 
   <tr>
     <td>
-      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--subcommands">`--subcommands (-s)`</a></code></h3>
+      <h3 id="flag-subcommands" data-text="subcommands"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--subcommands">--subcommands (-s)</a></code></h3>
     </td>
     <td>
 
@@ -171,7 +171,7 @@ a server restart. Toggle these flags with caution.
 
   <tr>
     <td>
-       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--bazelrc">`--bazelrc`</a></code></h3>
+       <h3 id="flag-bazelrc" data-text="bazelrc"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--bazelrc">--bazelrc</a></code></h3>
     </td>
     <td>
 
@@ -194,7 +194,7 @@ the .bazelrc file&gt;</strong></code>.
 
   <tr>
     <td>
-    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/9.1.0/docs/user-manual#host-jvm-args">`--host_jvm_args`</a></code></h3>
+    <h3 id="flag-host-jvm-args" data-text="host_jvm_args"><code><a href="https://bazel.build/versions/9.1.0/docs/user-manual#host-jvm-args">--host_jvm_args</a></code></h3>
     </td>
     <td>
 
@@ -227,7 +227,7 @@ For example, the following limits the Bazel heap size to <strong>3</strong>GB:
 
   <tr>
     <td>
-    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--output_base">`--output_base`</a></code></h3>
+    <h3 id="flag-output-base" data-text="output_base"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--output_base">--output_base</a></code></h3>
     </td>
     <td>
 
@@ -259,7 +259,7 @@ The following flags are related to Bazel test
 
   <tr>
     <td>
-       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--java_debug">`--java_debug`</a></code></h3>
+       <h3 id="flag-java-debug" data-text="java_debug"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--java_debug">--java_debug</a></code></h3>
     </td>
     <td>
 
@@ -271,7 +271,7 @@ Causes Java tests to wait for a debugger connection before being executed.
 
   <tr>
     <td>
-    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--runs_per_test">`--runs_per_test`</a></code></h3>
+    <h3 id="flag-runs-per-test" data-text="runs_per_test"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--runs_per_test">--runs_per_test</a></code></h3>
     </td>
     <td>
 
@@ -285,7 +285,7 @@ flaky tests and see whether a fix causes a test to pass consistently.
 
   <tr>
     <td>
-    <h3 id="flag-test-filter" data-text="test_filter"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--test_filter">`--test_filter`</a></code></h3>
+    <h3 id="flag-test-filter" data-text="test_filter"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--test_filter">--test_filter</a></code></h3>
     </td>
     <td>
 
@@ -302,7 +302,7 @@ debugging. This flag is often used in conjunction with
 
   <tr>
     <td>
-    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--test_output">`--test_output`</a></code></h3>
+    <h3 id="flag-test-output" data-text="test_output"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--test_output">--test_output</a></code></h3>
     </td>
     <td>
 
@@ -328,7 +328,7 @@ The following flags are related to Bazel run.
 
   <tr>
     <td>
-        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--run_under">`--run_under`</a></code></h3>
+        <h3 id="flag-run-under" data-text="run_under"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--run_under">--run_under</a></code></h3>
     </td>
     <td>
 
@@ -354,7 +354,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--disk_cache">`--disk_cache`</a></code></h3>
+       <h3 id="flag-disk-cache" data-text="disk_cache"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--disk_cache">--disk_cache</a></code></h3>
     </td>
     <td>
 
@@ -371,7 +371,7 @@ up Bazel builds by adding
 
   <tr>
     <td>
-    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--jobs">`--jobs`</a></code></h3>
+    <h3 id="flag-jobs" data-text="jobs"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--jobs">--jobs</a></code></h3>
     </td>
     <td>
 
@@ -386,7 +386,7 @@ cluster executes more jobs than you have cores locally.
 
   <tr>
     <td>
-    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--local_resources">`--local_resources`</a></code></h3>
+    <h3 id="flag-local-resources" data-text="local_resources"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--local_resources">--local_resources</a></code></h3>
     </td>
     <td>
 
@@ -403,7 +403,7 @@ Limits how much CPU or RAM is consumed by locally running actions.
 
   <tr>
     <td>
-    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--sandbox_base">`--sandbox_base`</a></code></h3>
+    <h3 id="flag-sandbox-base" data-text="sandbox_base"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--sandbox_base">--sandbox_base</a></code></h3>
     </td>
     <td>
 
@@ -434,7 +434,7 @@ options.
 
   <tr>
     <td>
-       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--flaky_test_attempts">`--flaky_test_attempts`</a></code></h3>
+       <h3 id="flag-flaky-test-attempts" data-text="flaky_test_attempts"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--flaky_test_attempts">--flaky_test_attempts</a></code></h3>
     </td>
     <td>
 
@@ -449,7 +449,7 @@ the test summary.
 
   <tr>
     <td>
-    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_cache">`--remote_cache`</a></code></h3>
+    <h3 id="flag-remote-cache" data-text="remote_cache"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_cache">--remote_cache</a></code></h3>
     </td>
     <td>
 
@@ -462,7 +462,7 @@ speed up Bazel builds. It can be combined with a local disk cache.
 
   <tr>
     <td>
-    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_download_regex">`--remote_download_regex`</a></code></h3>
+    <h3 id="flag-remote-download-regex" data-text="remote_download_regex"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_download_regex">--remote_download_regex</a></code></h3>
     </td>
     <td>
 
@@ -476,7 +476,7 @@ patterns may be specified by repeating this flag.
 
   <tr>
     <td>
-     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_executor">`--remote_executor`</a></code></h3>
+     <h3 id="flag-remote-executor" data-text="remote_executor"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_executor">--remote_executor</a></code></h3>
     </td>
     <td>
 
@@ -490,7 +490,7 @@ a remote execution service. You'll often need to Add
 
   <tr>
     <td>
-     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_instance_name">`--remote_instance_name`</a></code></h3>
+     <h3 id="flag-remote-instance-name" data-text="remote_instance_name"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--remote_instance_name">--remote_instance_name</a></code></h3>
     </td>
     <td>
 
@@ -502,7 +502,7 @@ The value to pass as <code>instance_name</code> in the remote execution API.
 
   <tr>
     <td>
-    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/9.1.0/docs/user-manual#show-timestamps">`--show_timestamps`</a></code></h3>
+    <h3 id="flag-show-timestamps" data-text="show-timestamps"><code><a href="https://bazel.build/versions/9.1.0/docs/user-manual#show-timestamps">--show_timestamps</a></code></h3>
     </td>
     <td>
 
@@ -516,7 +516,7 @@ quickly understand what step took how long.
 
   <tr>
     <td>
-    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--spawn_strategy">`--spawn_strategy`</a></code></h3>
+    <h3 id="flag-spawn-strategy" data-text="spawn_strategy"><code><a href="https://bazel.build/versions/9.1.0/reference/command-line-reference#flag--spawn_strategy">--spawn_strategy</a></code></h3>
     </td>
     <td>