Clarify documentation about sh_binary naming.
RELNOTES: None.
PiperOrigin-RevId: 358293994
diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/sh/BazelShBinaryRule.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/sh/BazelShBinaryRule.java
index 153b695..07c1f8b 100644
--- a/src/main/java/com/google/devtools/build/lib/bazel/rules/sh/BazelShBinaryRule.java
+++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/sh/BazelShBinaryRule.java
@@ -54,7 +54,7 @@
(<code>sh_binary</code> is a misnomer: its outputs aren't necessarily binaries.) This rule ensures
that all dependencies are built, and appear in the <code>runfiles</code> area at execution time.
We recommend that you name your <code>sh_binary()</code> rules after the name of the script minus
- the extension (e.g. <code>.sh</code>); do not give the rule and the file the same name.
+ the extension (e.g. <code>.sh</code>); the rule name and the file name must be distinct.
</p>
<h4 id="sh_binary_examples">Example</h4>
