diff --git a/modules/cluster-logging-updating-logging.adoc b/modules/cluster-logging-updating-logging.adoc
index 36a1bc0212c0..1dcdf1c2b1ff 100644
--- a/modules/cluster-logging-updating-logging.adoc
+++ b/modules/cluster-logging-updating-logging.adoc
@@ -149,7 +149,7 @@ elasticsearch-rollover-infra   */15 * * * *   False     0        <none>
 $ oc exec -c elasticsearch <any_es_pod_in_the_cluster> -- indices
 ----
 +
-You should see the `app-0000x`, `infra-0000x`, `audit-0000x`, `.security` indices.
+Verify that the output includes the `app-00000x`, `infra-00000x`, `audit-00000x`, `.security` indices.
 +
 .Sample output with indices in a green status
 [%collapsible]
@@ -198,7 +198,7 @@ green  open   audit-000001
 $ oc get ds fluentd -o json | grep fluentd-init
 ----
 +
-You should see a `fluentd-init` container:
+Verify that the output includes a `fluentd-init` container:
 +
 [source,terminal]
 ----
@@ -212,7 +212,7 @@ You should see a `fluentd-init` container:
 $ oc get kibana kibana -o json
 ----
 +
-You should see a Kibana pod with the `ready` status:
+Verify that the output includes a Kibana pod with the `ready` status:
 +
 .Sample output with a ready Kibana pod
 [%collapsible]
@@ -270,9 +270,8 @@ cronjob.batch/elasticsearch-rollover-audit
 cronjob.batch/elasticsearch-rollover-infra
 ----
 +
-You should see the `elasticsearch-delete-\*` and `elasticsearch-rollover-*` indices.
+Verify that the output includes the `elasticsearch-delete-\*` and `elasticsearch-rollover-*` indices.
 
 .Post-update tasks
 
 If you use the Log Forwarding API to forward logs, after the Elasticsearch Operator and Cluster Logging Operator are fully updated to 4.6, you must replace your `LogForwarding` custom resource (CR) with a `ClusterLogForwarder` CR.
-