Updated Managing Access and Consumer group guides as per agreed style discussions (#563)

* Updated Managing Access and Consumer group guides as per agreed style discussions.

* Completed style updates to Access and Consumer guides.

* Implemented reviewer's feedback.

Author: AedinC

docs/kafka/access-mgmt-kafka/README.adoc

@@ -83,7 +83,7 @@ ifdef::context[:parent-context: {context}]
 
 // Purpose statement for the assembly
 [role="_abstract"]
-As an owner of a Kafka instance in {product-kafka}, you can manage the level of access that other user accounts and service accounts have to your instance. You can allow or deny access to your instance for specific accounts or for all accounts in your organization. You can also allow other users or service accounts to manage the level of access to your instance for you.
+As an owner of a Kafka instance in {product-long-kafka}, you can manage the level of access that other user accounts and service accounts have to your instance. You can allow or deny access to your instance for specific accounts or for all accounts in your organization. You can also allow other users or service accounts to manage the level of access to your instance for you.
 
 You can manage access for only the Kafka instances that you create or for instances that the owner has enabled you to access and alter.
 
@@ -93,7 +93,7 @@ You can manage access for only the Kafka instances that you create or for instan
 == Access management in {product-kafka}
 
 [role="_abstract"]
-{product-kafka} uses Access Control Lists (ACLs) provided by Kafka that enable you to manage how other user accounts and service accounts are permitted to access the Kafka resources that you create. You can manage access for only the Kafka instances that you create or for instances that the owner has enabled you to access and alter.
+{product-long-kafka} uses Access Control Lists (ACLs) provided by Apache Kafka that enable you to manage how other user accounts and service accounts are permitted to access the Kafka resources that you create. You can manage access for only the Kafka instances that you create or for instances that the owner has enabled you to access and alter.
 
 An account in {product-kafka} is either a user account or a service account. A user account enables users in your organization to access your resources. A service account enables your application or tool to connect securely to your instance and access your resources.
 
@@ -232,31 +232,31 @@ https://kafka.apache.org/documentation/#security_authz_primitives[Authorization
 == Setting account permissions in a Kafka instance in {product-kafka}
 
 [role="_abstract"]
-In {product-kafka}, you can create Access Control Lists (ACLs) in your Kafka instances and set permissions for how other user accounts or service accounts can interact with an instance and its resources. You can manage access for only the Kafka instances that you create or for the instances that the owner has enabled you to access and alter.
+In {product-long-kafka}, you can create Access Control Lists (ACLs) in your Kafka instances and set permissions for how other user accounts or service accounts can interact with an instance and its resources. You can manage access for only the Kafka instances that you create or for the instances that the owner has enabled you to access and alter.
 
 .Prerequisites
-* You've created a Kafka instance and the instance is in *Ready* state.
+* You've created a Kafka instance and the instance is in the *Ready* state.
 * The user account or service account that you're setting permissions for has been created in the organization.
 
 .Procedure
-. In the {product-kafka} web console, go to *Streams for Apache Kafka* > *Kafka Instances* and click the name of the Kafka instance that you want to set permissions for.
+. On the {service-url-kafka}[Kafka Instances^] page of the {product-kafka} web console, click the name of the Kafka instance that you want to set permissions for.
 . Click the *Access* tab to view the current ACL permissions for this instance.
 . Use this *Access* page to set permissions for a new account, add permissions to an existing account, or delete account permissions in this instance.
 +
 * To set permissions for a new account in this instance, follow these steps:
 
 .. Click *Manage access*.
-.. In the *Account* drop-down menu, select the new user account or service account that you want to set permissions for. You can also select *All accounts* to set permissions for all user accounts and service accounts in the organization.
+.. In the *Account* list, select the new user account or service account that you want to set permissions for. You can also select *All accounts* to set permissions for all user accounts and service accounts in the organization.
 +
-If you don't see users in the drop-down list, ask your organization administrator to grant access to view other user accounts. For more information, see {base-url}{access-mgmt-url-kafka}#proc-user-account-access_managing-access[Allowing users to view other user accounts].
+If you don't see users in the *Account* list, ask your organization administrator to grant access to view other user accounts. For more information, see {base-url}{access-mgmt-url-kafka}#proc-user-account-access_managing-access[Allowing users to view other user accounts].
 .. Click *Next*.
 +
 --
 The *Review existing permissions* section lists any permission settings in this instance that are already defined for all accounts in the organization and for the same account that you previously selected, if applicable. You can delete existing permissions now if needed, or you can wait to delete existing permissions later from the main *Access* page.
 
 If you previously selected a specific account, you can delete only permission entries that apply to individual accounts. If you previously selected *All accounts*, you can delete only permission entries that apply to all accounts.
 --
-.. Under *Assign Permissions*, use the drop-down menu to select and define the permissions for the specified account or all accounts for a resource type, such as a topic.
+.. Under *Assign Permissions*, use the list to select and define the permissions for the specified account or all accounts for a resource type, such as a topic.
 +
 --
 The following permission options are available:
@@ -314,7 +314,7 @@ The *Review existing permissions* section lists any permission settings in this
 
 If you selected a permission entry that applies to a specific account, you can delete only permission entries that apply to individual accounts. If you selected a permission entry that applies to all accounts, you can delete only permission entries that apply to all accounts.
 --
-.. Under *Assign Permissions*, use the drop-down menu to select and define the permissions for the specified account or all accounts for a resource type, such as a topic. You can click *Add permission* to add permissions individually, or you can select from the predefined permission options as described previously.
+.. Under *Assign Permissions*, use the list to select and define the permissions for the specified account or all accounts for a resource type, such as a topic. You can click *Add permission* to add permissions individually, or you can select from the predefined permission options as described previously.
 .. Click *Save* to finish.
 
 * To delete existing account permissions in this instance, use the following options:
@@ -323,7 +323,7 @@ If you selected a permission entry that applies to a specific account, you can d
  ** For the account that you want to delete, select the options icon (three vertical dots) for that entry and click *Delete*.
 
 +
-IMPORTANT: If you delete a user account or service account, you should also delete any ACL permissions associated with that account. If you don't delete unused ACL permissions, then a future account with the same ID of a previously deleted account could inherit the ACL permissions and have automatic access to a Kafka instance.
+IMPORTANT: If you delete a user account or service account, you must also delete any ACL permissions associated with that account. If you don't delete unused ACL permissions, then a future account with the same ID of a previously deleted account could inherit the ACL permissions and have automatic access to a Kafka instance.
 
 
 [role="_additional-resources"]
@@ -334,12 +334,12 @@ IMPORTANT: If you delete a user account or service account, you should also dele
 == Example account access scenarios in {product-kafka}
 
 [role="_abstract"]
-The following example Access Control Lists (ACLs) illustrate common scenarios for managing the level of access for user accounts or service accounts in {product-kafka}. Some examples differ from the predefined permissions in {product-kafka} to demonstrate various possible ACL scenarios. Use these examples as a guide for your own ACLs.
+The following example Access Control Lists (ACLs) illustrate common scenarios for managing the level of access for user accounts or service accounts in {product-long-kafka}. Some examples differ from the predefined permissions in {product-kafka} to demonstrate various possible ACL scenarios. Use these examples as a guide for your own ACLs.
 
 Access for a new service account in a Kafka instance::
 +
 --
-I’ve created a new service account and I want to allow it to create and delete topics in the instance, to produce and consume messages in any topic in the instance, and to use any consumer group and any producer.
+You’ve created a new service account and you want to allow it to create and delete topics in the instance, to produce and consume messages in any topic in the instance, and to use any consumer group and any producer.
 
 .Example ACL permissions
 [cols="25%,22%,23%,15%,15%"]
@@ -367,7 +367,7 @@ h|Operation
 Access for all accounts in a Kafka instance::
 +
 --
-I want this Kafka instance to be fully accessible to all accounts in the organization. I want any user to be able to read all topics, write to all topics, use any consumer group, and use any producer.
+You want this Kafka instance to be fully accessible to all accounts in the organization. You want any user to be able to read all topics, write to all topics, use any consumer group, and use any producer.
 
 .Example ACL permissions
 [cols="25%,22%,23%,15%,15%"]
@@ -395,7 +395,7 @@ h|Operations
 Access for a specific user in a Kafka instance::
 +
 --
-I want this Kafka instance to be fully accessible to a specific user. I don't know which topics or consumer groups the user will use, so I want the user to be able to read any topic, write to any topic, and join any consumer group in the instance.
+You want this Kafka instance to be fully accessible to a specific user. You don't know which topics or consumer groups the user will use, so you want the user to be able to read any topic, write to any topic, and join any consumer group in the instance.
 
 .Example ACL permissions
 [cols="25%,22%,23%,15%,15%"]
@@ -423,7 +423,7 @@ h|Operations
 Access for a specific producer to write to a topic::
 +
 --
-I want to allow a user account with a producer that is associated with a specific `transactional.id` value to produce messages to a specific topic in this Kafka instance.
+You want to allow a user account with a producer that is associated with a specific `transactional.id` value to produce messages to a specific topic in this Kafka instance.
 
 .Example ACL permissions
 [cols="25%,22%,23%,15%,15%"]
@@ -451,7 +451,7 @@ h|Operations
 Access for specific consumer groups to consume from a topic::
 +
 --
-I want to allow a service account with consumers from consumer groups whose names start with `app` to consume messages from a specific topic in this Kafka instance.
+You want to allow a service account with consumers from consumer groups whose names start with `app` to consume messages from a specific topic in this Kafka instance.
 
 .Example ACL permissions
 [cols="25%,22%,23%,15%,15%"]
@@ -479,7 +479,7 @@ h|Operations
 Access for a specific user to manage all permissions in the ACL of a Kafka instance::
 +
 --
-I want to allow a user account to manage all permissions in the ACL for this Kafka instance. I've removed all other permissions from this instance so that the new authorized user can define the new ACL as needed.
+You want to allow a user account to manage all permissions in the ACL for this Kafka instance. You've removed all other permissions from this instance so that the new authorized user can define the new ACL as needed.
 
 .Example ACL permissions
 [cols="25%,22%,23%,15%,15%"]
@@ -511,35 +511,35 @@ h|Operations
 As an organization administrator, you can use Role-Based Access Control (RBAC) to allow users to view other users in an organization.
 
 You set up access by assigning a predefined role called `User Access principal viewer` to a user group.
-By assigning the role, users within the group are able to do the following:
+By assigning the role, users within the group are able to perform the following actions:
 
-* View and select other users when changing owners and managing access to Kafka instances in the web console
-* Specify user names when using the `rhoas` CLI for {product-long-kafka}
+* View and select other users when changing owners and managing access to Kafka instances in the {service-url-kafka}[Openshift Streams for Apache Kafka] web console.
+* Specify user names when using the `rhoas` CLI for {product-long-kafka}.
 
 .Prerequisites
-* You're logged into the {org-name} web console as an organization administrator.
+* You're logged into the {cloud-console-url}[Red Hat Hybrid Cloud Console] as an organization administrator.
 * A user group contains the users to assign the role to.
 
 NOTE: If you want to add the `User Access principal viewer` role to a single user, create a new group for that user only.
 
 ifndef::community[]
-For more information on setting up user access in the web console, see the link:https://access.redhat.com/documentation/en-us/red_hat_hybrid_cloud_console/[_User Access Configuration Guide for Role-based Access Control (RBAC)_^].
+For more information on setting up user access in the Red Hat Hybrid Cloud Console, see the link:https://access.redhat.com/documentation/en-us/red_hat_hybrid_cloud_console/[User Access Configuration Guide for Role-based Access Control (RBAC)^].
 endif::[]
 
 .Procedure
 
 . In the upper-right corner of the {product-kafka} web console, select the gear icon, and click *Settings* > *User Access* > *Groups*
 . Click the name of the user group.
-. From the *Roles* tab, click *Add role* and select `User Access principal viewer` to add the role to the group.
+. From the *Roles* tab, click *Add role* and select `User Access principal viewer`.
 . Click *Add to group* to add the role to the group.
 +
 The role is added to the list of selected roles on the *Roles* tab.
 
 [role="_additional-resources"]
 .Additional resources
-* {base-url}{getting-started-url-kafka}[_Getting started with {product-long-kafka}_^]
-* {base-url}{getting-started-rhoas-cli-url-kafka}[_Getting started with the `rhoas` CLI for {product-long-kafka}_^]
-* {base-url-cli}{command-ref-url-cli}[_CLI command reference (rhoas)_^]
+* {base-url}{getting-started-url-kafka}[Getting started with {product-long-kafka}^]
+* {base-url}{getting-started-rhoas-cli-url-kafka}[Getting started with the `rhoas` CLI for {product-long-kafka}^]
+* {base-url-cli}{command-ref-url-cli}[CLI command reference (rhoas)^]
 
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]