Fixed broken links to user manual in docs
The user manual filename has been renamed from `bazel-user-manual.html` to `user-manual.html`.
Closes #4662.
PiperOrigin-RevId: 187877241
diff --git a/site/docs/bazel-overview.md b/site/docs/bazel-overview.md
index 207ddc7..6755f85 100644
--- a/site/docs/bazel-overview.md
+++ b/site/docs/bazel-overview.md
@@ -99,15 +99,15 @@
Since all previous build work is cached, Bazel can identify and reuse cached
artifacts and only rebuild or retest what's changed. To further enforce
-correctness, you can set up Bazel to run builds and tests [hermetically](https://docs.bazel.build/versions/master/bazel-user-manual.html#sandboxing)
-through sandboxing, minimizing skew and maximizing [reproducibility](https://docs.bazel.build/versions/master/bazel-user-manual.html#correctness).
+correctness, you can set up Bazel to run builds and tests [hermetically](https://docs.bazel.build/versions/master/user-manual.html#sandboxing)
+through sandboxing, minimizing skew and maximizing [reproducibility](https://docs.bazel.build/versions/master/user-manual.html#correctness).
## What is the action graph?
The action graph represents the build artifacts, the relationships between them,
and the build actions that Bazel will perform. Thanks to this graph, Bazel can
-[track](https://docs.bazel.build/versions/master/bazel-user-manual.html#build-consistency-and-incremental-builds)
+[track](https://docs.bazel.build/versions/master/user-manual.html#build-consistency-and-incremental-builds)
changes to file content as well as changes to actions, such as build or test
commands, and know what build work has previously been done. The graph also
enables you to easily [trace dependencies](https://docs.bazel.build/versions/master/query-how-to.html)
diff --git a/site/docs/best-practices.md b/site/docs/best-practices.md
index 04a9ee7..b53a8d6 100644
--- a/site/docs/best-practices.md
+++ b/site/docs/best-practices.md
@@ -87,7 +87,7 @@
## `.bazelrc`
For project-specific options, use the configuration file `_your-workspace_/tools/bazel.rc` (see
-[bazelrc format](https://docs.bazel.build/bazel-user-manual.html#bazelrc)).
+[bazelrc format](https://docs.bazel.build/user-manual.html#bazelrc)).
For options that you **do not** want to check into source control, create the configuration file
`_your-workspace_/.bazelrc` and add `.bazelrc` to your `.gitignore`. Note that this file has a
diff --git a/site/docs/tutorial/android-app.md b/site/docs/tutorial/android-app.md
index f016628..20db3e2 100644
--- a/site/docs/tutorial/android-app.md
+++ b/site/docs/tutorial/android-app.md
@@ -315,7 +315,7 @@
bazel build //android:android
```
-The [`build`](../bazel-user-manual.html#build) subcommand instructs Bazel to
+The [`build`](../user-manual.html#build) subcommand instructs Bazel to
build the target that follows. The target is specified as the name of a build
rule inside a `BUILD` file, with along with the package path relative to
your workspace directory. Note that you can sometimes omit the package path
@@ -367,7 +367,7 @@
You can now deploy the app to a connected Android device or emulator from the
command line using the
-[`bazel mobile-install`](../bazel-user-manual.html#mobile-install)
+[`bazel mobile-install`](../user-manual.html#mobile-install)
command. This command uses the Android Debug Bridge (`adb`) to communicate with
the device. You must set up your device to use `adb` following the instructions
in
@@ -383,7 +383,7 @@
```
Note that the `mobile-install` subcommand also supports the
-[`--incremental`](../bazel-user-manual.html#mobile-install)
+[`--incremental`](../user-manual.html#mobile-install)
flag that can be used to deploy only those parts of the app that have changed
since the last deployment.
