Docs: Code font updates for Bazel files part 1
PiperOrigin-RevId: 375101044
diff --git a/site/docs/android-instrumentation-test.md b/site/docs/android-instrumentation-test.md
index df282de..34a6226 100644
--- a/site/docs/android-instrumentation-test.md
+++ b/site/docs/android-instrumentation-test.md
@@ -94,7 +94,7 @@
-### `BUILD` file
+### BUILD file
The graph translates into a `BUILD` file like this:
@@ -187,7 +187,7 @@
</manifest>
```
-### `WORKSPACE` dependencies
+### WORKSPACE dependencies
In order to use this rule, your project needs to depend on these external
repositories:
diff --git a/site/docs/android-ndk.md b/site/docs/android-ndk.md
index c7baa2a..9dc82d3 100644
--- a/site/docs/android-ndk.md
+++ b/site/docs/android-ndk.md
@@ -34,7 +34,7 @@
)
```
-For more information on the `android_ndk_repository` rule, see its the [Build
+For more information on the `android_ndk_repository` rule, see the [Build
Encyclopedia entry](be/android.html#android_ndk_repository).
## Quick start
@@ -42,7 +42,7 @@
To build C++ for Android, simply add `cc_library` dependencies to your
`android_binary` or `android_library` rules.
-For example, given the following BUILD file for an Android app:
+For example, given the following `BUILD` file for an Android app:
```python
# In <project>/app/src/main/BUILD.bazel
@@ -68,7 +68,7 @@
)
```
-This BUILD file results in the following target graph:
+This `BUILD` file results in the following target graph:
<img src="/assets/android_ndk.png" alt="Build graph of Android project with cc_library dependencies" width="600px"/>
@@ -107,7 +107,7 @@
repository](https://github.com/bazelbuild/examples/tree/master/android/ndk).
In the `BUILD.bazel` file, three targets are defined with the `android_binary`,
-`android_library` and `cc_library` rules.
+`android_library`, and `cc_library` rules.
The `android_binary` top-level target builds the APK.
@@ -269,8 +269,8 @@
register_toolchains("@androidndk//:all")
```
-Registering these toolchains tells Bazel to look for them in the NDK BUILD file
-(for NDK 20) when resolving architecture and operating system constraints:
+Registering these toolchains tells Bazel to look for them in the NDK `BUILD`
+file (for NDK 20) when resolving architecture and operating system constraints:
```python
toolchain(
diff --git a/site/docs/bazel-and-cpp.md b/site/docs/bazel-and-cpp.md
index 11ce1e5..00951f1 100644
--- a/site/docs/bazel-and-cpp.md
+++ b/site/docs/bazel-and-cpp.md
@@ -29,7 +29,7 @@
Follow the guidelines below when creating your BUILD files:
-* Each BUILD file should contain one [`cc_library`](be/c-cpp.html#cc_library)
+* Each `BUILD` file should contain one [`cc_library`](be/c-cpp.html#cc_library)
rule target per compilation unit in the directory.
* You should granularize your C++ libraries as much as
diff --git a/site/docs/bazel-and-java.md b/site/docs/bazel-and-java.md
index 83edeba..949fd82 100644
--- a/site/docs/bazel-and-java.md
+++ b/site/docs/bazel-and-java.md
@@ -94,12 +94,12 @@
### BUILD files
-Follow these guidelines when creating your BUILD files:
+Follow these guidelines when creating your `BUILD` files:
-* Use one BUILD file per directory containing Java sources, because this
+* Use one `BUILD` file per directory containing Java sources, because this
improves build performance.
-* Every BUILD file should contain one `java_library` rule that looks like
+* Every `BUILD` file should contain one `java_library` rule that looks like
this:
```python
@@ -111,7 +111,7 @@
```
* The name of the library should be the name of the directory containing the
- BUILD file. This makes the label of the library shorter, that is use
+ `BUILD` file. This makes the label of the library shorter, that is use
`"//package"` instead of `"//package:package"`.
* The sources should be a non-recursive [`glob`](be/functions.html#glob) of
diff --git a/site/docs/bep-examples.md b/site/docs/bep-examples.md
index b92e6e6..f9419fa 100644
--- a/site/docs/bep-examples.md
+++ b/site/docs/bep-examples.md
@@ -11,7 +11,7 @@
before looking at the specification.
Consider a simple Bazel workspace that consists of two empty shell scripts
-`foo.sh` and `foo_test.sh` and the following BUILD file:
+`foo.sh` and `foo_test.sh` and the following `BUILD` file:
```bash
sh_library(
