Bazel DevSite: Fix more broken links.
These are just the worst offenders (404s). There are several missing anchors yet to be fixed.
PiperOrigin-RevId: 430276249
diff --git a/site/en/docs/aquery.md b/site/en/docs/aquery.md
index 21c5b9c..2ccac13 100644
--- a/site/en/docs/aquery.md
+++ b/site/en/docs/aquery.md
@@ -304,7 +304,7 @@
`AspectClass` could be the name of the Aspect class (for native Aspects) or
`bzl_file%aspect_name` (for Starlark Aspects). `AspectDescriptor` are
sorted in topological order of the
-[dependency graph](rules/aspects#aspect_basics).
+[dependency graph](/rules/aspects#aspect_basics).
### Linking with the JSON profile {:#linking-with-json-profile}
diff --git a/site/en/docs/mobile-install.md b/site/en/docs/mobile-install.md
index 7191555..630cf3e 100644
--- a/site/en/docs/mobile-install.md
+++ b/site/en/docs/mobile-install.md
@@ -190,7 +190,7 @@
The following numbers were computed for a few Google products:
-<img src="/assets/mobile-install-performance.svg"/>
+<img src="/docs/images/mobile-install-performance.svg"/>
This, of course, depends on the nature of the change: recompilation after
changing a base library takes more time.
diff --git a/site/en/faq.md b/site/en/faq.md
index 8c0b090..65ce679 100644
--- a/site/en/faq.md
+++ b/site/en/faq.md
@@ -154,7 +154,7 @@
Bazel returns a non-zero exit code if the build or test invocation fails, and this should be enough for basic CI integration. Since Bazel does not need clean builds for correctness, the CI system should not be configured to clean before starting a build/test run.
-Further details on exit codes are in the [User Guide](/docs/user-guide).
+Further details on exit codes are in the [User Manual](/docs/user-manual).
## What future features can we expect in Bazel?
diff --git a/site/en/rules/rules.md b/site/en/rules/rules.md
index f8c5cf6..a375648 100644
--- a/site/en/rules/rules.md
+++ b/site/en/rules/rules.md
@@ -756,7 +756,7 @@
In addition to default outputs, there are *output groups*, which are collections
of output files that may be requested together. These can be requested with
-[`--output_groups`](/rules/command-line-reference#flag--output_groups). For
+[`--output_groups`](/reference/command-line-reference#flag--output_groups). For
example, if a target `//pkg:mytarget` is of a rule type that has a `debug_files`
output group, these files can be built by running `bazel build //pkg:mytarget
--output_groups=debug_files`. Since non-predeclared outputs don't have labels,
diff --git a/site/en/start/bazel-vision.md b/site/en/start/bazel-vision.md
index 77a8890..36de246 100644
--- a/site/en/start/bazel-vision.md
+++ b/site/en/start/bazel-vision.md
@@ -80,7 +80,7 @@
language (such as Maven for Java), and support incremental migration paths
from other widely-used build systems.
1. The rules need to be **extensible and interoperable**, following
- ["Bazel sandwich"](https://bazel.build/designs/2016/08/04/extensibility-for-native-rules.html)
+ ["Bazel sandwich"](https://github.com/bazelbuild/bazel-website/blob/master/designs/_posts/2016-08-04-extensibility-for-native-rules.md)
principles.
1. The rules need to be **remote-execution ready**. In practice, this means
**configurable using the [toolchains](/docs/toolchains) mechanism**.
diff --git a/site/en/tutorials/java.md b/site/en/tutorials/java.md
index 0018c63..83a60f9 100644
--- a/site/en/tutorials/java.md
+++ b/site/en/tutorials/java.md
@@ -180,7 +180,7 @@
As you can see, the project has a single target that build two source files with
no additional dependencies:
-
+
After you set up your workspace, build your project, and examine its
dependencies, then you can add some complexity.
@@ -244,7 +244,7 @@
same inputs as it did before, but the structure of the build is different:
+/docs/images/tutorial_java_02.svg)
You've now built the project with two targets. The `ProjectRunner` target builds
two source files and depends on one other target (`:greeter`), which builds
@@ -273,7 +273,7 @@
the target label `//:greeter`) - Bazel knows this through the `deps` attribute.
Take a look at the dependency graph:
-
+
However, for the build to succeed, you must explicitly give the `runner` target
in `//src/main/java/com/example/cmdline/BUILD` visibility to targets in
