[blaze-core-fixit] Update Bazel docs and examples links to main or HEAD.
RELNOTES: None
PiperOrigin-RevId: 379499545
diff --git a/site/docs/configurable-attributes.md b/site/docs/configurable-attributes.md
index 8d3dbe1..3cfb941 100644
--- a/site/docs/configurable-attributes.md
+++ b/site/docs/configurable-attributes.md
@@ -93,7 +93,7 @@
under a target. For example, `genrule`'s `tools` changes `--cpu` to the CPU of
the machine running Bazel (which, thanks to cross-compilation, may be different
than the CPU the target is built for). This is known as a
-[configuration transition](https://docs.bazel.build/versions/master/glossary.html#transition).
+[configuration transition](https://docs.bazel.build/versions/main/glossary.html#transition).
Given
@@ -212,7 +212,7 @@
)
```
-Behavior is the same as for [built-in flags](#built-in-flags). See [here](https://github.com/bazelbuild/examples/tree/master/rules/starlark_configurations/select_on_build_setting)
+Behavior is the same as for [built-in flags](#built-in-flags). See [here](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/select_on_build_setting)
for a working example.
[`--define`](command-line-reference.html#flag--define)
@@ -634,10 +634,10 @@
## <a name="query"></a>Bazel query and cquery
Bazel [`query`](query-how-to.html) operates over Bazel's
-[loading phase](https://docs.bazel.build/versions/master/glossary.html#loading-phase).
+[loading phase](https://docs.bazel.build/versions/main/glossary.html#loading-phase).
This means it doesn't know what command line flags a target uses since those
flags aren't evaluated until later in the build (in the
-[analysis phase](https://docs.bazel.build/versions/master/glossary.html#analysis-phase)).
+[analysis phase](https://docs.bazel.build/versions/main/glossary.html#analysis-phase)).
So it can't determine which `select()` branches are chosen.
Bazel [`cquery`](cquery.html) operates after Bazel's analysis phase, so it has
