RHDHBUGS-2005 - Fixed broken links (redhat-developer#1348)

I will merge now and adress fixes in followup pull requests.

Author: themr0c

modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc

@@ -37,7 +37,7 @@ annotations:
   ...
   # The label that Argo CD uses to fetch all the applications. The format to be used is label.key=label.value. For example, rht-gitops.com/janus-argocd=quarkus-app.
 
-  argocd/app-selector: '${ARGOCD_LABEL_SELECTOR}' 
+  argocd/app-selector: '${ARGOCD_LABEL_SELECTOR}'
 ----
 
 * (Optional) Add the following annotation to the entity’s `catalog-info.yaml` file to switch between Argo CD instances as shown in the following example:
@@ -49,7 +49,7 @@ annotations:
    ...
     # The Argo CD instance name used in `app-config.yaml`.
 
-    argocd/instance-name: '${ARGOCD_INSTANCE}' 
+    argocd/instance-name: '${ARGOCD_INSTANCE}'
 ----
 
 +
@@ -81,7 +81,7 @@ The optional Argo CD Rollouts feature enhances Kubernetes by providing advanced
 
 .Prerequisites
 
-* The Backstage Kubernetes plugin (`@backstage/plugin-kubernetes`) is installed and configured. 
+* The Backstage Kubernetes plugin (`@backstage/plugin-kubernetes`) is installed and configured.
 
 ** To install and configure Kubernetes plugin in Backstage, see link:https://backstage.io/docs/features/kubernetes/installation/[Installaltion] and link:https://backstage.io/docs/features/kubernetes/configuration/[Configuration] guide.
 
@@ -213,7 +213,7 @@ If using the label selector annotation (backstage.io/kubernetes-label-selector),
 
 . Open {Product} interface and navigate to the entity you configured.
 
-. Select the *CD* tab and then select the *GitOps application*. The side panel opens. 
+. Select the *CD* tab and then select the *GitOps application*. The side panel opens.
 
 . In the *Resources* table of the side panel, verify that the following resources are displayed:
 
@@ -231,6 +231,5 @@ If using the label selector annotation (backstage.io/kubernetes-label-selector),
 [role="_additional-resources"]
 .Additional resources
 
-* The package path, scope, and name of the {company-name} ArgoCD plugin has changed since 1.2. For more information, see link:{release-notes-book-url}#removed-functionality-rhidp-4293[Breaking Changes] in the _{release-notes-book-title}_.
 
-* For more information on installing dynamic plugins, see link:{installing-and-viewing-plugins-book-url}[{installing-and-viewing-plugins-book-title}].
+* link:{installing-and-viewing-plugins-book-link}[{installing-and-viewing-plugins-book-title}]

modules/dynamic-plugins/ref-configuring-the-keycloak-plugin.adoc

@@ -146,7 +146,16 @@ PromQL supports arithmetic operations, comparison operators, logical/set operati
 Additionally, the results can be visualized using Grafana.
 ====
 
-== Exporting Metrics
+// === Use Case Example
+
+// Imagine your Keycloak instance is under-provisioned (e.g., low CPU/RAM limits), and the plugin is configured to send many parallel API requests.
+// This could cause request timeouts or throttling. The metrics described above can help detect such behavior early, allowing administrators to:
+
+// - Tune the plugin configuration (e.g., reduce parallelism)
+// - Increase resources on the Keycloak server
+// - Investigate network or permission issues
+
+=== Exporting Metrics
 
 You can export metrics using any OpenTelemetry-compatible backend, such as *Prometheus*.