diff --git a/docs/reference/docs/bulk.asciidoc b/docs/reference/docs/bulk.asciidoc
index 830586fb01d67..cf9c32858ff9a 100644
--- a/docs/reference/docs/bulk.asciidoc
+++ b/docs/reference/docs/bulk.asciidoc
@@ -137,7 +137,7 @@ $ curl -s -H "Content-Type: application/x-ndjson" -XPOST localhost:9200/_bulk --
 
 [discrete]
 [[bulk-optimistic-concurrency-control]]
-===== Optimistic Concurrency Control
+===== Optimistic concurrency control
 
 Each `index` and `delete` action within a bulk API call may include the
 `if_seq_no` and `if_primary_term` parameters in their respective action
@@ -168,7 +168,7 @@ appropriate backing index for the stream.
 
 [discrete]
 [[bulk-wait-for-active-shards]]
-===== Wait For Active Shards
+===== Wait for active shards
 
 When making bulk calls, you can set the `wait_for_active_shards`
 parameter to require a minimum number of shard copies to be active
diff --git a/docs/reference/indices/create-index.asciidoc b/docs/reference/indices/create-index.asciidoc
index 4d29734ebf52c..b28f51a23a71f 100644
--- a/docs/reference/indices/create-index.asciidoc
+++ b/docs/reference/indices/create-index.asciidoc
@@ -156,7 +156,7 @@ PUT /test
 --------------------------------------------------
 
 [[create-index-wait-for-active-shards]]
-===== Wait For active shards
+===== Wait for active shards
 
 By default, index creation will only return a response to the client when the primary copies of
 each shard have been started, or the request times out. The index creation response will indicate
diff --git a/docs/reference/indices/open-close.asciidoc b/docs/reference/indices/open-close.asciidoc
index 27036cb1129b9..1490d3895d442 100644
--- a/docs/reference/indices/open-close.asciidoc
+++ b/docs/reference/indices/open-close.asciidoc
@@ -66,7 +66,7 @@ and then the previous write index can be closed.
 // end::closed-index[]
 
 [[open-index-api-wait-for-active-shards]]
-===== Wait For active shards
+===== Wait for active shards
 
 // tag::wait-for-active-shards[]