diff --git a/modules/cluster-logging-deploy-console.adoc b/modules/cluster-logging-deploy-console.adoc
index f9c6801ab805..6c6e38ddd28d 100644
--- a/modules/cluster-logging-deploy-console.adoc
+++ b/modules/cluster-logging-deploy-console.adoc
@@ -194,7 +194,7 @@ spec:
     elasticsearch:
       nodeCount: 3 <5>
       storage:
-        storageClassName: "<storage-class-name>" <6>
+        storageClassName: "<storage_class_name>" <6>
         size: 200G
         resources: <7>
           requests:
@@ -224,7 +224,6 @@ However, an unmanaged deployment does not receive updates until OpenShift Loggin
 <3> Settings for configuring Elasticsearch. Using the CR, you can configure shard replication policy and persistent storage.
 <4> Specify the length of time that Elasticsearch should retain each log source. Enter an integer and a time designation: weeks(w), hours(h/H), minutes(m) and seconds(s). For example, `7d` for seven days. Logs older than the `maxAge` are deleted. You must specify a retention policy for each log source or the Elasticsearch indices will not be created for that source.
 <5> Specify the number of Elasticsearch nodes. See the note that follows this list.
-<6> Enter the name of an existing storage class for Elasticsearch storage. For best performance, specify a storage class that allocates block storage. If you do not specify a storage class, {product-title} deploys OpenShift Logging with ephemeral storage only.
 <6> Enter the name of an existing storage class for Elasticsearch storage. For best performance, specify a storage class that allocates block storage. If you do not specify a storage class, {product-title} deploys cluster logging with ephemeral storage only.
 <7> Specify the CPU and memory requests for Elasticsearch as needed. If you leave these values blank, the Elasticsearch Operator sets default values that should be sufficient for most deployments. The default values are `16G` for the memory request and `1` for the CPU request.
 <8> Specify the CPU and memory requests for the Elasticsearch proxy as needed. If you leave these values blank, the Elasticsearch Operator sets default values that should be sufficient for most deployments. The default values are `256Mi` for the memory request and `100m` for the CPU request.