RHDHBUGS-2005 Fixed broken links addendum (#1359) (#1361)

Author: themr0c

assemblies/dynamic-plugins/assembly-extensions-plugins.adoc

@@ -5,7 +5,7 @@ include::{docdir}/artifacts/snip-technology-preview.adoc[]
 
 :context: rhdh-extensions-plugins
 
-{product} ({product-very-short}) includes the Extensions feature which is preinstalled and enabled by default. Extensions provides users with a centralized interface to browse and manage available plugins 
+{product} ({product-very-short}) includes the Extensions feature which is preinstalled and enabled by default. Extensions provides users with a centralized interface to browse and manage available plugins
 
 You can use Extensions to discover plugins that extend {product-very-short} functionality, streamline development workflows, and improve the developer experience.
 
@@ -21,21 +21,21 @@ include::../modules/dynamic-plugins/con-catalog-searching-and-filtering.adoc[lev
 // Viewing a plugin - screenshots added post 1.5 GA, so this section is no longer necessary
 // include::../modules/dynamic-plugins/ref-catalog-plugin.adoc[leveloffset=+2]
 
-// Disabling Extensions 
+// Disabling Extensions
 include::../modules/dynamic-plugins/proc-extensions-disabling.adoc[leveloffset=+1]
 
-// START RHDH 1.7.0
+// START {product-very-short} 1.7.0
 // ==========
 // Managing plugins installation by using Extensions
 include::../modules/dynamic-plugins/con-extensions-managing-plugins.adoc[leveloffset=+1]
 
-// Configuring an RBAC role to manage Extensions 
+// Configuring an RBAC role to manage Extensions
 include::../modules/dynamic-plugins/proc-extensions-configuring-rbac-role.adoc[leveloffset=+2]
 
 // Enabling plugins installation by using Extensions
 include::../modules/dynamic-plugins/proc-extensions-enabling-plugins-installation.adoc[leveloffset=+2]
 
-// Enabling plugins in a RHDH Local installation by using Extensions
+// Enabling plugins in a {product-very-short} Local installation by using Extensions
 include::../modules/dynamic-plugins/proc-extensions-enabling-plugins-installation-rhdh-local.adoc[leveloffset=+2]
 
 // Installing plugins by using Extensions
@@ -48,7 +48,7 @@ include::../modules/dynamic-plugins/proc-extensions-configuring-plugins.adoc[lev
 // include::../modules/dynamic-plugins/con-extensions-troubleshooting-plugins-installation.adoc[leveloffset=+1]
 // ==========
 
-// END RHDH 1.7.0
+// END {product-very-short} 1.7.0
 
 // Operator installation by using plugin extension
 //include::../modules/dynamic-plugins/proc-operator-installing-a-plugin-using-extensions.adoc[leveloffset=+1]
@@ -57,4 +57,4 @@ include::../modules/dynamic-plugins/proc-extensions-configuring-plugins.adoc[lev
 //include::../modules/dynamic-plugins/proc-extensions-managing.adoc[leveloffset=+1]
 
 // Creating the extensions plugin metadata - For 1.6+
-//include::../modules/dynamic-plugins/proc-extensions-creating.adoc[leveloffset=+1]
+//include::../modules/dynamic-plugins/proc-extensions-creating.adoc[leveloffset=+1]

modules/about/ref-customer-support-info.adoc

@@ -1,5 +1,5 @@
 [id="ref-customer-support-info_{context}"]
-= Red Hat Developer Hub support
+= {product} support
 
 If you experience difficulty with a procedure described in this documentation, visit the https://access.redhat.com[Red Hat Customer Portal]. You can use the Red Hat Customer Portal for the following purposes:
 

modules/authentication/proc-authenticationg-with-the-guest-user-on-a-helm-based-installation.adoc

@@ -6,7 +6,7 @@ On a Helm-based installation, you can configure {product-short} to log in as a G
 
 .Prerequisites
 * You {configuring-book-link}[added a custom {product-short} application configuration], and have sufficient permissions to modify it.
-* You {configuring-book-link}#using-the-helm-chart-to-run-rhdh-with-your-custom-configuration[use the {product} Helm chart to run  {product-short}].
+* You {configuring-book-link}#using-the-helm-chart-to-run-rhdh-with-your-custom-configuration[use the {product} Helm chart to run {product-short}].
 
 .Procedure
 * To enable the guest user in your {product-short} custom configuration, {configuring-book-link}#using-the-helm-chart-to-run-rhdh-with-your-custom-configuration[configure your {product} Helm Chart] with following content:

modules/authentication/proc-authenticationg-with-the-guest-user-on-an-operator-based-installation.adoc

@@ -6,7 +6,7 @@ After an Operator-based installation, you can configure {product-short} to log i
 
 .Prerequisites
 * You {configuring-book-link}[added a custom {product-short} application configuration], and have sufficient permissions to modify it.
-* You {configuring-book-link}#using-the-operator-to-run-rhdh-with-your-custom-configurationn[use the {product} Operator to run  {product-short}].
+* You {configuring-book-link}#using-the-operator-to-run-rhdh-with-your-custom-configurationn[use the {product} Operator to run {product-short}].
 
 .Procedure
 * To enable the guest user in your {product-short} custom configuration, {configuring-book-link}#provisioning-your-custom-configuration[edit your {product-short} application configuration] with following content:

modules/authentication/proc-enabling-user-authentication-with-rhbk.adoc

@@ -18,7 +18,7 @@ Save the value for the next step:
 
 .. To register your {product-short} in {rhbk}, in the created realm, {rhbk-docs-link}/html-single/getting_started_guide/index#getting-started-zip-secure-the-first-application[secure the first application], with:
 ... **Client ID**: A distinctive client ID, such as __<{product-very-short}>__.
-... **Valid redirect URIs**: Set to the OIDC handler URL: `https://__<RHDH_URL>__/api/auth/oidc/handler/frame`.
+... **Valid redirect URIs**: Set to the OIDC handler URL: `pass:c,a,q[{my-product-url}/api/auth/oidc/handler/frame]`.
 ... Navigate to the **Credentials** tab and copy the **Client secret**.
 ... Save the values for the next step:
 * **Client ID**

modules/configuring-the-global-header/con-quicklinks-and-starred-items-in-global-header.adoc

@@ -33,15 +33,15 @@ The default configuration includes the following components:
 
 *MenuItemLink entries*: Define sections, titles, icons, and links within the *Quicklinks* matrix. The default configuration includes links to the {product-short} documentation and an {product-very-short} Local, as shown in the following configurations:
 
-[source,yaml]
+[source,yaml,subs="+attributes"]
 ----
 - mountPoint: global.header/application-launcher
   importName: MenuItemLink
   config:
     section: Documentation
     priority: 150
     props:
-      title: Developer Hub
+      title: {product-short}
       icon: developerHub
       link: https://docs.redhat.com/en/documentation/red_hat_developer_hub
 

modules/configuring-the-global-header/proc-enabling-quicklinks-starred-items-after-upgrade.adoc

@@ -28,7 +28,7 @@ Confirm that you listed the `red-hat-developer-hub-backstage-plugin-global-heade
 
 . Add the required components. Under the `mountPoints` section of the plugin, add the components as shown in the following example:
 +
-[source,yaml]
+[source,yaml,subs="+attributes"]
 ----
   mountPoints:
     - mountPoint: application/header
@@ -49,7 +49,7 @@ Confirm that you listed the `red-hat-developer-hub-backstage-plugin-global-heade
         section: Documentation
       priority: 150
       props:
-          title: Developer Hub
+          title: {product-short}
           icon: developerHub
           link: https://docs.redhat.com/en/documentation/red_hat_developer_hub
     - mountPoint: global.header/application-launcher

modules/configuring-the-quickstarts/proc-customize-rhdh-quickstart.adoc

@@ -1,21 +1,21 @@
 [id="customizing-your-product-quickstart_{context}"]
 = Customizing your {product} Quickstart
 
-As an administrator, you can configure the {product} Quickstart plugin to create customized onboarding for your {product-short} users. 
+As an administrator, you can configure the {product} Quickstart plugin to create customized onboarding for your {product-short} users.
 
 .Prerequisites
 You must have administrator permissions.
 
 .Procedure
 . Update your `{my-app-config-file}`, as follows:
 +
-.Example of a customized Quickstart plugin 
-[source,yaml]
+.Example of a customized Quickstart plugin
+[source,yaml,subs="+attributes"]
 ----
 app:
   quickstart:
-    - title: 'Welcome to Developer Hub' # <1>
-      description: 'Learn the basics of navigating the Developer Hub interface' # <2>
+    - title: 'Welcome to {product-short}' # <1>
+      description: 'Learn the basics of navigating the {product-short} interface' # <2>
       icon: 'home' # <3>
       cta:
         text: 'Get Started' # <4>
@@ -37,4 +37,5 @@ app:
 <2> (Required) A brief description of what the step covers.
 <3> Icon identifier (supports Material UI icons).
 <4> CTA button text.
-<5> CTA target URL or route.
+<5> CTA target URL or route.
+

modules/customizing-the-quick-access-card/proc-using-a-dedicated-service-to-provide-data-to-the-quick-access-card.adoc

@@ -15,7 +15,7 @@ When using a dedicated service, you can do the following tasks:
 .Prerequisites
 
 * You have installed the {product} using Helm chart.
-For more information, see xref:{installing-on-ocp-book-link}#assembly-install-rhdh-ocp-helm[{installing-on-ocp-book-title} with the Helm chart].
+For more information, see {installing-on-ocp-book-link}#assembly-install-rhdh-ocp-helm[{installing-on-ocp-book-title} with the Helm chart].
 
 .Procedure
 
@@ -120,7 +120,7 @@ metadata:
 data:
   {my-app-config-file}: |
     app:
-      title: Red Hat Developer Hub
+      title: {product}
     backend:
       csp:
         connect-src:

modules/customizing-the-quick-access-card/proc-using-hosted-json-files-to-provide-data-to-the-quick-access-card.adoc

@@ -9,7 +9,7 @@
 .Prerequisites
 
 * You have installed {product} by using either the Operator or Helm chart.
-See xref:{installing-on-ocp-book-link}#assembly-install-rhdh-ocp[{installing-on-ocp-book-title}].
+See {installing-on-ocp-book-link}#assembly-install-rhdh-ocp[{installing-on-ocp-book-title}].
 
 .Procedure