Merge pull request #73739 from abrennan89/OBSDOCS-804

OBSDOCS-804: Update description for LokiStack tenant field

Author: abrennan89

modules/create-lokistack-cr-cli.adoc

@@ -37,14 +37,15 @@ spec:
       type: s3 # <3>
   storageClassName: <storage_class_name> # <4>
   tenants:
-    mode: openshift-logging
+    mode: openshift-logging # <5>
 ----
 <1> Specify the deployment size. In the {logging} 5.8 and later versions, the supported size options for production instances of Loki are `1x.extra-small`, `1x.small`, or `1x.medium`.
 <2> Specify the name of your log store secret.
 <3> Specify the type of your log store secret.
 <4> Specify the name of a storage class for temporary storage. For best performance, specify a storage class that allocates block storage. Available storage classes for your cluster can be listed by using the `oc get storageclasses` command.
+<5> LokiStack defaults to running in multi-tenant mode, which cannot be modified. One tenant is provided for each log type: audit, infrastructure, and application logs. This enables access control for individual users and user groups to different log streams.
 
-. Apply the `LokiStack` CR:
+. Apply the `LokiStack` CR by running the following command:
 +
 [source,terminal]
 ----

modules/create-lokistack-cr-console.adoc

@@ -40,10 +40,11 @@ spec:
       type: s3 # <4>
   storageClassName: <storage_class_name> # <5>
   tenants:
-    mode: openshift-logging
+    mode: openshift-logging # <6>
 ----
 <1> Use the name `logging-loki`.
 <2> Specify the deployment size. In the {logging} 5.8 and later versions, the supported size options for production instances of Loki are `1x.extra-small`, `1x.small`, or `1x.medium`.
 <3> Specify the secret used for your log storage.
 <4> Specify the corresponding storage type.
 <5> Enter the name of a storage class for temporary storage. For best performance, specify a storage class that allocates block storage. Available storage classes for your cluster can be listed by using the `oc get storageclasses` command.
+<6> LokiStack defaults to running in multi-tenant mode, which cannot be modified. One tenant is provided for each log type: audit, infrastructure, and application logs. This enables access control for individual users and user groups to different log streams.