Update rule documentation to use booleans for boolean values.

RELNOTES: None.
PiperOrigin-RevId: 688859329
Change-Id: If9869a85a183a6a46c6f6f6454d60f8c7f26e205

java/common/rules/java_binary.bzl

diff --git a/java/common/rules/java_binary.bzl b/java/common/rules/java_binary.bzl
index 5b8b107..8e0ce02 100644
--- a/java/common/rules/java_binary.bzl
+++ b/java/common/rules/java_binary.bzl
@@ -170,7 +170,7 @@
 is the <code>name</code> attribute of this java_binary rule. In this case,
 the linker will remove any code it thinks is unused from the resulting binary,
 which means any C++ code accessed only via JNI may not be linked in unless
-that <code>cc_library</code> target specifies <code>alwayslink = 1</code>.</li>
+that <code>cc_library</code> target specifies <code>alwayslink = True</code>.</li>
 </ul>
 
 <p>When using any launcher other than the default JDK launcher, the format

java/common/rules/java_library.bzl

diff --git a/java/common/rules/java_library.bzl b/java/common/rules/java_library.bzl
index 9c04fe7..cc6b749 100644
--- a/java/common/rules/java_library.bzl
+++ b/java/common/rules/java_library.bzl
@@ -214,7 +214,7 @@
 of such libraries are the IDE APIs for IDE plug-ins or <code>tools.jar</code> for anything
 running on a standard JDK.
 <p>
-  Note that <code>neverlink = 1</code> does not prevent the compiler from inlining material
+  Note that <code>neverlink = True</code> does not prevent the compiler from inlining material
   from this library into compilation targets that depend on it, as permitted by the Java
   Language Specification (e.g., <code>static final</code> constants of <code>String</code>
   or of primitive types). The preferred use case is therefore when the runtime library is