Ihor's and some minor changeS

Author: pabel-rh

assemblies/assembly-configuring-scorecards-in-rhdh.adoc

@@ -4,9 +4,8 @@
 = Configuring Scorecards to view metrics in your {product} instance
 :context: assembly-configuring-scorecards-in-rhdh
 
-You can configure metrics and scoring capabilities from various data sources for software components in the {product-very-short} catalog.
+You can configure one of the following Scorecards in your {product-very-short} instance using metrics and scoring capabilities from various data sources for software components in the {product-very-short} catalog:
 
-You can configure either of the following Scorecards in your {product-very-short} instance:
 * GitHub Scorecards
 * Jira Scorecards
 

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

@@ -5,6 +5,7 @@
 
 To view project tracking data from Atlassian Jira in your {product-very-short} instance, configure Jira Scorecards.
 The following Jira versions are supported:
+
 * Jira Cloud: API version 3
 * Jira Data Center: API version 2
 
@@ -19,13 +20,13 @@ The following Jira versions are supported:
 == Procedure
 
 . Create a Jira configuration token using one of the following methods, depending on your Jira product:
-** Jira Cloud: Create a personal token. You must then create a `Base64-encoded` string using the following plain text format: `your-atlassian-email:your-jira-api-token`.
+** Jira Cloud: https://id.atlassian.com/manage-profile/security/api-tokens[Create a personal token]. You must then create a `Base64-encoded` string using the following plain text format: `your-atlassian-email:your-jira-api-token`.
 +
 [source,bash]
 ----
 echo -n 'your-atlassian-email:your-jira-api-token' | base64
 ----
-** Jira datacenter: Create and use a Personal Access Token (PAT) in your Jira datacenter account.
+** Jira datacenter: Create and use a Personal Access Token (PAT) in your Jira datacenter account. For more information, see the https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html[Atlassian] documentation.
 
 . 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`:
@@ -41,7 +42,6 @@ plugins:
         token: ${JIRA_TOKEN}
         product: datacenter # Change to 'cloud' if using Jira Cloud
 ----
-+
 where:
 `baseUrl`:: Enter the Jira URL.
 `token`:: Enter the Jira token (Base64 string for Cloud, PAT for Data Center).
@@ -101,9 +101,7 @@ spec:
   system: examples
   providesApis: [example-grpc-api]
 ----
-
 where:
-
 `jira/project-key`:: Required: Enter the Jira project key.
 `jira/component`:: Optional: Enter the Jira component name.
 `jira/label`:: Optional: Enter the Jira label.
@@ -141,9 +139,7 @@ scorecard:
           mandatoryFilter: Type = Task AND Resolution = Resolved
           customFilter: priority in ("Critical", "Blocker")
 ----
-
 where:
-
 `mandatoryFilter`:: Optional: Replaces the default filter (`type = Bug and resolution = Unresolved`).
 `customFilter`:: Optional: Specifies a global custom filter. The entity annotation `jira/custom-filter` overrides this value.
 

modules/observe/scorecards/ref-override-rules-to-configure-entity-specific-thresholds.adoc

@@ -3,8 +3,6 @@
 [id="ref-override-rules-to-configure-entity-specific-thresholds_{context}"]
 = Threshold rules to metrics for your Scorecard plugin
 
-:_mod-docs-content-type: CONCEPT
-
 You can override individual threshold rules for a specific component by using annotations in its `catalog-info.yaml` file. These annotations are merged with the existing global rules defined in your `{product-very-short} app-config.yaml` file.
 
 .Annotation Format Reference