Incorporated engineering feedback.

Signed-off-by: John Wilkins <jowilkin@redhat.com>

Author: johnwilkins

modules/creating-the-lokistack.adoc

@@ -51,7 +51,7 @@ spec:
 +
 [IMPORTANT]
 ====
-If there is no retention period defined on the object storage bucket or in the `LokiStack` CR, then the logs are not pruned and they stay in the object storage forever, which might fill up the storage.
+If there is no retention period defined on the object storage bucket or in the `LokiStack` CR, then the logs are not pruned and they stay in the object storage forever, which might fill up the storage. For cloud-hosted object storage, configuring a bucket lifecycle policy is recommended over relying solely on LokiStack retention, as lifecycle policies reduce API costs associated with object deletion.
 ====
 
 . Apply the `LokiStack` CR by running the following command:
@@ -63,7 +63,16 @@ $ oc apply -f <filename>.yaml
 
 .Verification
 
-* Verify that the LokiStack pods are running:
+* Verify that the LokiStack is ready by running the following command:
++
+[source,terminal]
+----
+$ oc get lokistack logging-loki -n openshift-logging -o jsonpath='{.status.conditions[?(@.type=="Ready")].message}'
+----
++
+The output should show `All components ready`.
+
+* To verify individual components, check that the LokiStack pods are running by running the following command:
 +
 [source,terminal]
 ----