diff --git a/modules/quickstart-opentelemetry.adoc b/modules/quickstart-opentelemetry.adoc
index a21ba9acbda7..9096c2c08abf 100644
--- a/modules/quickstart-opentelemetry.adoc
+++ b/modules/quickstart-opentelemetry.adoc
@@ -8,11 +8,13 @@ include::snippets/technology-preview.adoc[]
 To configure OTLP ingestion and enable the OpenTelemetry data model, follow these steps:
 
 .Prerequisites
-* Cluster administrator permissions
+* You have access to an {ocp-product-title} cluster with `cluster-admin` permissions.
+* You installed the {oc-first}.
+* You have access to a supported object store. For example, AWS S3, Google Cloud Storage, {azure-short}, Swift, Minio, or {rh-storage}.
 
 .Procedure
 
-. Install the {clo}, {loki-op}, and {coo-first} from OperatorHub.
+. Install the `{clo}`, `{loki-op}`, and `{coo-first}` from OperatorHub.
 
 . Create a `LokiStack` custom resource (CR) in the `openshift-logging` namespace:
 +
@@ -54,7 +56,7 @@ $ oc create sa collector -n openshift-logging
 +
 [source,terminal]
 ----
-$ oc adm policy add-cluster-role-to-user logging-collector-logs-writer -z collector
+$ oc adm policy add-cluster-role-to-user logging-collector-logs-writer -z collector -n openshift-logging
 ----
 +
 [NOTE]
@@ -66,22 +68,17 @@ The `ClusterRole` resource is created automatically during the Cluster Logging O
 +
 [source,terminal]
 ----
-$ oc project openshift-logging
+$ oc adm policy add-cluster-role-to-user collect-application-logs -z collector -n openshift-logging
 ----
 +
 [source,terminal]
 ----
-$ oc adm policy add-cluster-role-to-user collect-application-logs -z collector
+$ oc adm policy add-cluster-role-to-user collect-audit-logs -z collector -n openshift-logging
 ----
 +
 [source,terminal]
 ----
-$ oc adm policy add-cluster-role-to-user collect-audit-logs -z collector
-----
-+
-[source,terminal]
-----
-$ oc adm policy add-cluster-role-to-user collect-infrastructure-logs -z collector
+$ oc adm policy add-cluster-role-to-user collect-infrastructure-logs -z collector -n openshift-logging
 ----
 +
 [NOTE]