Applied changes

Author: pabel-rh

modules/customizing-the-appearance/proc-customize-rhdh-sidebar-menuitems.adoc

@@ -9,12 +9,12 @@ The sidebar menu in {product} consists of two main parts:
 
 .Procedure
 
-. Customize the main menu items using the following steps:
+Customize the main menu items using the following steps:
 +
 --
-.. Open the `app-config-rhdh.yaml` file.
-.. To customize the order and parent-child relationships for the main menu items, use the `dynamicPlugins.frontend.default.main-menu-items.menuItems` field.
-.. For dynamic plugin menu items, use the `dynamicPlugins.frontend.<package_name>.menuItems` field.
+. Open the `app-config-rhdh.yaml` file.
+. To customize the order and parent-child relationships for the main menu items, use the `dynamicPlugins.frontend.default.main-menu-items.menuItems` field.
+. For dynamic plugin menu items, use the `dynamicPlugins.frontend.<package_name>.menuItems` field.
 
 .Example `app-config-rhdh.yaml` file
 [source,yaml]

modules/customizing-the-home-page/proc-defining-the-layout-of-the-product-home-page.adoc

@@ -12,8 +12,8 @@
 ** position (x and y)
 
 .Procedure
-* Configure your {product-short} `app-config.yaml` configuration file by choosing one of the following options:
-** Use the full space on smaller windows and half of the space on larger windows as follows:
+. Configure your {product-short} `app-config.yaml` configuration file by choosing one of the following options:
+.. Use the full space on smaller windows and half of the space on larger windows as follows:
 
 [source,yaml]
 ----
@@ -36,7 +36,7 @@ dynamicPlugins:
               debugContent: a placeholder
 ----
 
-** Show the cards side by side by defining the `x` parameter as follows:
+.. Show the cards side by side by defining the `x` parameter as follows:
 
 [source,yaml]
 ----
@@ -73,7 +73,7 @@ dynamicPlugins:
 ----
 However, you can see a second card below this card by default.
 
-* Show the cards in three columns by defining the `x` parameter as follows:
+. Show the cards in three columns by defining the `x` parameter as follows:
 
 [source,yaml]
 ----

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

@@ -6,15 +6,15 @@
 [id="using-a-dedicated-service-to-provide-data-to-the-quick-access-card_{context}"]
 = Using a dedicated service to provide data to the Quick access card
 
-When using a dedicated service, you can do the following:
+When using a dedicated service, you can do the following tasks:
 
 * Use the same service to provide the data to all configurable {product-short} pages or use a different service for each page.
 * Use the https://github.com/redhat-developer/red-hat-developer-hub-customization-provider[`red-hat-developer-hub-customization-provider`] as an example service, which provides data for both the Home and Tech Radar pages. The `red-hat-developer-hub-customization-provider` service provides the same data as default {product-short} data. You can fork the `red-hat-developer-hub-customization-provider` service repository from GitHub and modify it with your own data, if required.
 * Deploy the `red-hat-developer-hub-customization-provider` service and the {product-short} Helm chart on the same cluster.
 
 .Prerequisites
 
-* You have installed the {product} using Helm Chart.
+* You have installed the {product} using Helm chart.
 For more information, see xref:{installing-on-ocp-book-url}#assembly-install-rhdh-ocp-helm[{installing-on-ocp-book-title} with the Helm chart].
 
 .Procedure
@@ -28,12 +28,12 @@ To use a separate service to provide the Home page data, complete the following
 To use the `red-hat-developer-hub-customization-provider` service, add the URL for the https://github.com/redhat-developer/red-hat-developer-hub-customization-provider[red-hat-developer-hub-customization-provider] repository or your fork of the repository containing your customizations.
 --
 
-. On the *General* tab, enter *red-hat-developer-hub-customization-provider* in the *Name* field and click *Create*.
-. On the *Advanced Options* tab, copy the value from the *Target Port*.
+. On the *General* tab, enter `red-hat-developer-hub-customization-provider` in the *Name* field and click *Create*.
+. On the *Advanced Options* tab, copy the value from *Target Port*.
 +
 [NOTE]
 ====
-The *Target Port* automatically generates a Kubernetes or {ocp-short} service to communicate with.
+*Target Port* automatically generates a Kubernetes or {ocp-short} service to communicate with.
 ====
 +
 . Add the following code to the `app-config-rhdh.yaml` file:
@@ -45,12 +45,12 @@ proxy:
     # Other Proxies
     # customize developer hub instance
     '/developer-hub':
-      target: ${HOMEPAGE_DATA_URL}
+      target: ${HOMEPAGE_DATA_URL} <1>
       changeOrigin: true
       # Change to "false" in case of using self-hosted cluster with a self-signed certificate
       secure: true
 ----
-where `HOMEPAGE_DATA_URL` is defined as `pass:c[http://<SERVICE_NAME>:8080]`, for example, `pass:c[http://rhdh-customization-provider:8080]`.
+<1> `pass:c[http://<SERVICE_NAME>:8080]`, for example, `pass:c[http://rhdh-customization-provider:8080]`.
 +
 [NOTE]
 ====
@@ -62,11 +62,11 @@ The `red-hat-developer-hub-customization-provider` service contains the 8080 por
 . Delete the {product-short} pod to ensure that the new configurations are loaded correctly.
 
 .Verification
-* To view the service, navigate to the *Administrator* perspective in the {ocp-short} web console and click *Networking* > *Service*.
+* To view the service, go to the *Administrator* perspective in the {ocp-short} web console and click *Networking* > *Service*.
 +
 [NOTE]
 ====
-You can also view the *Service Resources* in the Topology view.
+You can also view *Service Resources* in the Topology view.
 ====
 
 * Ensure that the provided API URL for the Home page returns the data in JSON format as shown in the following example:
@@ -109,7 +109,7 @@ You can also view the *Service Resources* in the Topology view.
 If the request call fails or is not configured, the {product-short} instance falls back to the default local data.
 ====
 
-* If the images or icons do not load, then allowlist them by adding your image or icon host URLs to the content security policy’s (csp) `img-src` in your custom ConfigMap as follows:
+* If the images or icons do not load, then allowlist them by adding your image or icon host URLs to the content security policy (csp) `img-src` in your custom ConfigMap as shown in the following example:
 
 [source,yaml]
 ----

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

@@ -14,8 +14,6 @@ See xref:{installing-on-ocp-book-url}#assembly-install-rhdh-ocp[{installing-on-o
 .Procedure
 
 * To access the data from the JSON files, add the following code to the {product-short} `app-config.yaml` configuration file:
-
-* Add the following code to the `app-config.yaml` file:
 +
 [source,yaml]
 ----

modules/customizing-the-tech-radar-page/proc-customize-rhdh-tech-radar-page.adoc

@@ -48,7 +48,7 @@ When using a dedicated service, you can do the following:
 
 .Prerequisites
 
-* You have installed the {product} using Helm Chart.
+* You have installed the {product} using Helm chart.
 For more information, see xref:{installing-on-ocp-book-url}#assembly-install-rhdh-ocp-helm[{installing-on-ocp-book-title} with the Helm chart].
 
 .Procedure