commit 4b16e02aabf08b154cb2258930e76a59a741206f
author Peter Laird <laird_peter@yahoo.com> Thu Oct 12 16:44:19 2017 +0200
committer Marcel Hlopko <hlopko@google.com> Fri Oct 13 13:51:53 2017 +0200
tree 1f55b6494ab3a6faad7f7620561dba6fb8e17c62
parent faf2db22277bd0b074a0a8c5cd4533a735eff31a

Clarify the direction of visibility in the tutorial

The original text makes it sound like greeter target needs visibility to the runner target. It is the other way around.

Closes #3866.

PiperOrigin-RevId: 171958509

site/docs/tutorial/java.md

diff --git a/site/docs/tutorial/java.md b/site/docs/tutorial/java.md
index 0c5cafb..e273776 100644
--- a/site/docs/tutorial/java.md
+++ b/site/docs/tutorial/java.md
@@ -279,8 +279,8 @@
 
 ![Dependency graph of the target 'runner'](/assets/tutorial_java_03.svg)
 
-However, for the build to succeed, you must make the `runner` target in
-`//src/main/java/com/example/cmdline/BUILD` explicitly visible 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