Incorporated tech changes

Author: pabel-rh

modules/observe/scorecards/proc-authenticating-and-managing-scorecard-plugins.adoc

@@ -18,16 +18,16 @@ p, role:default/scorecard-viewer, catalog.entity.read, read, allow
 See {authorization-book-link}#ref-rbac-permission-policies_title-authorization[Permission policies reference].
 
 ** To use the RBAC Web UI, complete the following steps:
-... In your {product} menu, go to *Settings > Role Based Access Control (RBAC)*.
+... In your {product} menu, go to *Settings > RBAC*.
 ... Select or create the *Role* to which you want to grant access to the Scorecards.
-... To enable read access for the Scorecard plugin, add a policy with the following details:
+... To enable read access for the Scorecard plugin, add a policy with the following details and click *Next*:
 **** *Permission*: `scorecard.metric.read`
 **** *Action*: `read`
 **** *Effect*: `allow`
 
 . Provide users access to specific metrics by their identifiers by using a conditional policy to restrict access, for example, only to the GitHub Open PRs metric (`github.open_prs`) using any of the following ways:
 ** {audit-log-book-link}#managing-authorizations-by-using-the-web-ui[Using the Web UI]. 
-** Using the file as shown in the following code:
+** defining the conditional policies in an `rbac-conditional-policies.yaml` file as shown in the following code:
 +
 [source,yaml]
 ----

modules/observe/scorecards/proc-configuring-github-scorecards-in-rhdh-instance.adoc

@@ -102,7 +102,7 @@ scorecard:
               expression: '>50'
 ----
 +
-`scorecard:plugins:github:open_prs:threshold`:: Lists the custom threshold values for the GitHub metrics.
+`scorecard:plugins:github:open_prs:threshold`:: Lists the default threshold values for the GitHub metrics.
 
 [NOTE]
 ====

modules/observe/scorecards/proc-configuring-jira-scorecards-in-rhdh-instance.adoc

@@ -25,10 +25,10 @@ The following Jira versions are supported:
 ----
 echo -n 'your-atlassian-email:your-jira-api-token' | base64
 ----
-** Jira Data Center: Create and use a Personal Access Token (PAT) directly.
+** Jira datacenter: Create and use a Personal Access Token (PAT) in your Jira datacenter account.
 
 . Configure the Jira Scorecard plugin in your `{product-very-short} dynamic-plugins-config.yaml` using either a direct setup or a proxy setup.
-** Use a direct setup (Recommended for simpler environments): Add the following code to your `{product-very-short} dynamic-plugins-config.yaml`:
+.. Use a direct setup (Recommended for simpler environments): Add the following code to your `{product-very-short} dynamic-plugins-config.yaml`:
 +
 [source,yaml]
 ----
@@ -104,7 +104,7 @@ spec:
 
 where:
 
-`jira/project-key`:: Enter the Jira project key.
+`jira/project-key`:: Required: Enter the Jira project key.
 `jira/component`:: Optional: Enter the Jira component name.
 `jira/label`:: Optional: Enter the Jira label.
 `jira/team`:: Optional: Enter the Jira team ID (not the team title).