Docs: Rewrite Bazel pages to clarify intended user: Tutorials, part7
PiperOrigin-RevId: 363992464
diff --git a/site/docs/tutorial/java.md b/site/docs/tutorial/java.md
index 120c9b9..bb47db0 100644
--- a/site/docs/tutorial/java.md
+++ b/site/docs/tutorial/java.md
@@ -128,15 +128,15 @@
### Build the project
-Let's build your sample project. Change into the `java-tutorial` directory
-and run the following command:
+To build your sample project, navigate to the `java-tutorial` directory
+and run:
```
bazel build //:ProjectRunner
```
-Notice the target label - the `//` part is the location of our `BUILD` file
-relative to the root of the workspace (in this case, the root itself), and
-`ProjectRunner` is what we named that target in the `BUILD` file. (You will
+In the target label, the `//` part is the location of the `BUILD` file
+relative to the root of the workspace (in this case, the root itself),
+and `ProjectRunner` is the target name in the `BUILD` file. (You will
learn about target labels in more detail at the end of this tutorial.)
Bazel produces output similar to the following:
@@ -165,8 +165,9 @@
Bazel uses those statements to create the project's dependency graph, which
enables accurate incremental builds.
-Let's visualize our sample project's dependencies. First, generate a text
-representation of the dependency graph (run the command at the workspace root):
+To visualize the sample project's dependencies, you can generate a text
+representation of the dependency graph by running this command at the
+workspace root:
```
bazel query --notool_deps --noimplicit_deps "deps(//:ProjectRunner)" --output graph
@@ -184,8 +185,8 @@
-Now that you have set up your workspace, built your project, and examined its
-dependencies, let's add some complexity.
+After you set up your workspace, build your project, and examine its
+dependencies, then you can add some complexity.
## Refine your Bazel build
@@ -196,7 +197,7 @@
### Specify multiple build targets
-Let's split our sample project build into two targets. Replace the contents of
+You can split the sample project build into two targets. Replace the contents of
the `java-tutorial/BUILD` file with the following:
```python
@@ -217,7 +218,7 @@
`ProjectRunner` binary. The `deps` attribute in `java_binary` tells Bazel that
the `greeter` library is required to build the `ProjectRunner` binary.
-Let's build this new version of our project. Run the following command:
+To build this new version of the project, run the following command:
```
bazel build //:ProjectRunner
@@ -277,8 +278,8 @@
-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
+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
`//BUILD` using the `visibility` attribute. This is because by default targets
are only visible to other targets in the same `BUILD` file. (Bazel uses target
visibility to prevent issues such as libraries containing implementation details
@@ -295,8 +296,8 @@
)
```
-Let's now build the new package. Run the following command at the root of the
-workspace:
+Now you can build the new package by running the following command at the root
+of the workspace:
```
bazel build //src/main/java/com/example/cmdline:runner
