Docs: Fix headings of Bazel site pages, Part 1
PiperOrigin-RevId: 352816385
diff --git a/site/docs/aquery.html b/site/docs/aquery.html
index a45f9b0..78be60c 100644
--- a/site/docs/aquery.html
+++ b/site/docs/aquery.html
@@ -2,11 +2,9 @@
layout: documentation
title: Aquery (action graph query)
---
-<h1>Aquery (Action Graph Query)</h1>
+<h1>Action Graph Query (aquery)</h1>
-<h2 id='overview'>Overview</h2>
-
<p>
The <code>aquery</code> command allows you to query for actions in your build graph.
It operates on the post-analysis Configured Target Graph and exposes
@@ -79,7 +77,7 @@
$ bazel aquery 'inputs(".*cpp", deps(//src/target_a))'
</pre>
-<h2 id='functions'>Aquery functions</h2>
+<h2 id='functions'>aquery functions</h2>
<p>There are currently 3 <code>aquery</code> functions:</p>
<ul>
@@ -372,7 +370,7 @@
<h2 id='known-issues'>Known issues</h2>
-<h3 id='shared-actions'>Handling Shared Actions</h3>
+<h3 id='shared-actions'>Handling shared actions</h3>
<p>
Sometimes actions are
diff --git a/site/docs/build-event-protocol.md b/site/docs/build-event-protocol.md
index 3ece3d2..90246dc 100644
--- a/site/docs/build-event-protocol.md
+++ b/site/docs/build-event-protocol.md
@@ -42,7 +42,7 @@
payload might not be the expected type, but could be an `Aborted` message e.g.
if the build aborted prematurely.
-### Build Event graph
+### Build event graph
All build events form a directed acyclic graph through their parent and child
relationship. Every build event except for the initial build event has one or
diff --git a/site/docs/build-ref.html b/site/docs/build-ref.html
index 3eba968..7df9047 100644
--- a/site/docs/build-ref.html
+++ b/site/docs/build-ref.html
@@ -15,7 +15,7 @@
of related source files and one BUILD file. The BUILD file specifies what
software outputs can be built from the source.
</p>
-<h2 id="packages_targets">Workspace, packages and targets</h2>
+<h2 id="packages_targets">Workspace, packages, and targets</h2>
<h3 id="workspace">Workspace</h3>
<p>A <em>workspace</em> is a directory on your filesystem that contains the
@@ -542,7 +542,7 @@
loading (yet): you don't need to use <code>exports_files</code> to make
a <code>.bzl</code> file visible.
-<h2 id="funcs">Types of build rule</h2>
+<h2 id="funcs">Types of build rules</h2>
<p>
The majority of build rules come in families, grouped together by
diff --git a/site/docs/cquery.html b/site/docs/cquery.html
index b68584c..ded6f2f 100644
--- a/site/docs/cquery.html
+++ b/site/docs/cquery.html
@@ -2,9 +2,8 @@
layout: documentation
title: Cquery (configurable query)
---
-<h1>Cquery (Configurable Query)</h1>
+<h1> Configurable query (cquery)</h1>
-<h2 id='overview'>Overview</h2>
<p>
<code>cquery</code> is a variant
@@ -256,7 +255,7 @@
available during a build.
</p>
-<h3>Cquery options</h3>
+<h3>'cquery' options</h3>
<h4 id="universe_scope-comma-separated-list"><code>--universe_scope</code> (comma-separated list)</h4>
diff --git a/site/docs/guide.md b/site/docs/guide.md
index 79349d2..76b36cb 100644
--- a/site/docs/guide.md
+++ b/site/docs/guide.md
@@ -979,7 +979,7 @@
long-running commands such as builds, your script will have to wait for those
commands to complete before it can continue.
-### Notes about Server Mode
+### Notes about server mode
By default, Bazel uses a long-running [server process](#client/server) as an
optimization. When running Bazel in a script, don't forget to call `shutdown`
diff --git a/site/docs/migrate-maven.md b/site/docs/migrate-maven.md
index 4fae44d..2219ef3 100644
--- a/site/docs/migrate-maven.md
+++ b/site/docs/migrate-maven.md
@@ -200,7 +200,7 @@
)
```
-### <a name="3-build"></a>3. Create more BUILD files (Optional)
+### <a name="3-build"></a>3. Create more BUILD files (optional)
Bazel does work with just one BUILD file, as you saw after completing your first
build. You should still consider breaking the build into smaller chunks by
diff --git a/site/docs/mobile-install.md b/site/docs/mobile-install.md
index 70b54b7..76bab4b 100644
--- a/site/docs/mobile-install.md
+++ b/site/docs/mobile-install.md
@@ -125,7 +125,7 @@
installation will be, but the slower app startup becomes, because the dynamic
linker has to do more work. The sweet spot is usually between 10 and 50 shards.
-### Incremental File Transfer
+### Incremental file transfer
After building the app, the next step is to install it, preferably with the
least effort possible. Installation consists of the following steps:
@@ -151,7 +151,7 @@
have safeguarded against this by computing the checksum of the files on the
device, but this was deemed to be not worth the increase in installation time.
-### The Stub Application
+### The Stub application
The stub application is where the magic to load the dexes, native code and
Android resources from the on-device `mobile-install` directory happens.
diff --git a/site/docs/multiplex-worker.md b/site/docs/multiplex-worker.md
index b09ea79..72a395e 100644
--- a/site/docs/multiplex-worker.md
+++ b/site/docs/multiplex-worker.md
@@ -62,7 +62,7 @@
`supports-workers`, if both are set. A ruleset is encouraged to use multiplex
workers if possible, to improve performance.
-### WARNING
+### Warning about rare bug
Due to a rare bug, multiplex workers are currently unstable. Occasionally,
Bazel hangs indefinitely at the execution phase. If you see this behavior,
