Confirm the default number of primary shards for application and operations indices equals data node count

modules/cluster-logging-about-elasticsearch.adoc

@@ -11,6 +11,11 @@ Elasticsearch subdivides each index into multiple pieces called _shards_, which
 You can configure Elasticsearch to make copies of the shards, called _replicas_. Elasticsearch also spreads these replicas across
 the Elasticsearch nodes. The *ClusterLogging* Custom Resource allows you to specify the replication policy in the Custom Resource Definition (CRD) to provide data redundancy and resilience to failure.
 
+[NOTE]
+====
+The number of primary shards for the index templates is equal to the number of Elasticsearch data nodes.
+====
+
 The Cluster Logging Operator and companion Elasticsearch Operator ensure that each Elasticsearch node is deployed using a unique Deployment that includes its own storage volume.
 You can use a Cluster Logging Custom Resource (CR) to increase the number of Elasticsearch nodes.
 Refer to

modules/cluster-logging-deploy-subscription.adoc

@@ -325,6 +325,8 @@ elasticsearch-cdm-x6kdekli-1   1/1     1            1           18h
 elasticsearch-cdm-x6kdekli-2   0/1     1            0           6m49s
 elasticsearch-cdm-x6kdekli-3   0/1     1            0           6m44s
 ----
+
+The number of primary shards for the index templates is equal to the number of Elasticsearch data nodes.
 ====
 
 .. Click *Create*. This creates the Cluster Logging Custom Resource and Elasticsearch Custom Resource, which you

modules/cluster-logging-elasticsearch-ha.adoc

@@ -20,6 +20,10 @@ Logs might be unavailable or lost in the event a node is down or fails.
 Use this mode when you are more concerned with performance than safety, or have
 implemented your own disk/PVC backup/restore strategy.
 
+[NOTE]
+====
+The number of primary shards for the index templates is equal to the number of Elasticsearch data nodes.
+====
 
 .Prerequisites