Incorporated some of the test day comments

Author: pabel-rh

artifacts/snip-developer-preview.adoc renamed to modules/developer-lightspeed/artifacts/snip-developer-preview.adoc

@@ -19,7 +19,7 @@ If rules are ordered incorrectly, a less restrictive rule can prevent stricter r
 === Correct Ordering Example
 
 Order the rules from the most restrictive value range to the least restrictive to ensure logical flow.
-+
+
 [source,yaml]
 ----
 # Correct Example: Order from most restrictive (Success) to least restrictive (Error)

modules/observe/scorecards/con-best-practices-for-threshold-rules.adoc

@@ -8,7 +8,7 @@ To override the default thresholds set by a metric provider, you must update you
 The custom configuration completely replaces the provider's defaults. If you omit a threshold category (such as `success`), that category is not assigned.
 
 The following configuration defines a `success` threshold as 10 or fewer issues, which applies to all components using the `jira.open_issues` metric unless explicitly overridden by an entity annotation.
-+
+
 [source,yaml]
 ----
 scorecard:

modules/observe/scorecards/con-set-global-standards-for-metric-thresholds.adoc

@@ -7,4 +7,4 @@ include::{docdir}/artifacts/snip-developer-preview.adoc[]
 
 The Scorecard plugin offers comprehensive, customizable insights into the health, security posture, and compliance of your components, services, and APIs. It centralizes Key Performance Indicators (KPIs) within {product} ({product-very-short}), so you do not have to consult multiple external systems.
 
-image::rhdh/scorecard-sample.png[]
+image::rhdh/scorecard-sample.png[]

modules/observe/scorecards/con-understand-scorecard-plugins.adoc

@@ -39,13 +39,13 @@ plugins:
       jira:
         baseUrl: ${JIRA_BASE_URL}
         token: ${JIRA_TOKEN}
-        product: datacenter # Change to 'cloud' if using Jira Cloud
+        product: _<jira_product>_
 ----
 where:
 
 `baseUrl`:: Enter the Jira URL.
 `token`:: Enter the Jira token (Base64 string for Cloud, PAT for Data Center). The Jira token must be added as a secret file in your {configuring-book-link}#provisioning-your-custom-configuration[`{product} app-config.yaml` file].
-`product`:: Enter the supported product: `cloud` or `datacenter`.
+`product`:: Enter the supported product: `cloud` or `datacenter`. (`cloud` is the preferred option)
 
 .. Use a proxy setup: In your `{product-very-short} dynamic-plugins-config.yaml`, add the following code:
 +

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

@@ -9,7 +9,7 @@ You can override individual threshold rules for a specific component by using an
 
 The annotation key follows a strict structure:
 `scorecard.io/{providerId}.thresholds.rules.{thresholdKey}: '{expression}'`
-+
+
 [cols="1,2,2,2", options="header"]
 |===
 | Element | Description | Example Annotation | Example Value
@@ -33,7 +33,7 @@ The annotation key follows a strict structure:
 .Example: Entity Annotation Override
 
 The following example describes the entity overriding only the `warning` and `error` rules for the `jira.open_issues` metric. The `success` rule falls back to the value defined in the global `{product-very-short} app-config.yaml` file.
-+
+
 [source,yaml]
 ----
 # catalog-info.yaml