Fix some typos in RHDH documentation adocs (redhat-developer#872)

Co-authored-by: Jordan White <[email protected]>

Author: jordanpagewhite

artifacts/rhdh-plugins-reference/tekton/tekton-plugin-admin.adoc

@@ -6,7 +6,7 @@ You can use the Tekton plugin to visualize the results of CI/CD pipeline runs on
 [[installing-tekton-plugin]]
 == Installation
 
-.Prerequsites
+.Prerequisites
 * You have installed and configured the `@backstage/plugin-kubernetes` and `@backstage/plugin-kubernetes-backend` dynamic plugins.
 //For more information about installing dynamic plugins, see xref:rhdh-installing-dynamic-plugins[].
 //Cannot xref across titles. Convert xref to a link.
@@ -140,4 +140,4 @@ global:
       - package: ./dynamic-plugins/dist/backstage-community-plugin-tekton
         disabled: false
 ----
---
+--

artifacts/rhdh-plugins-reference/tekton/tekton-plugin-readme.adoc

@@ -8,7 +8,7 @@ You can use the Tekton plugin to visualize the results of CI/CD pipeline runs on
 [[installing-tekton-plugin]]
 === Installation
 
-.Prerequsites
+.Prerequisites
 * You have installed and configured the `@backstage/plugin-kubernetes` and `@backstage/plugin-kubernetes-backend` dynamic plugins.
 //For more information about installing dynamic plugins, see xref:rhdh-installing-dynamic-plugins[].
 //Cannot xref across titles. Convert xref to a link.

artifacts/rhdh-plugins-reference/topology/topology-plugin-readme.adoc

@@ -191,7 +191,7 @@ You can use the https://raw.githubusercontent.com/backstage/community-plugins/ma
 ====
 --
 
-* The following annotation is added to the entity's `catalog-info.yaml` file to identify whether an entitiy contains the Kubernetes resources:
+* The following annotation is added to the entity's `catalog-info.yaml` file to identify whether an entity contains the Kubernetes resources:
 +
 --
 [source,yaml]

modules/configuring/proc-using-the-operator-to-run-rhdh-with-your-custom-configuration.adoc

@@ -148,7 +148,7 @@ spec:
 ----
 ====
 +
-.Inject the envvironment variables in the `{my-product-secrets}` and `{my-product-database-secrets}` secrets
+.Inject the environment variables in the `{my-product-secrets}` and `{my-product-database-secrets}` secrets
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----

modules/customizing-techdocs/proc-techdocs-using-odf-storage.adoc

@@ -28,7 +28,7 @@ spec:
 +
 [NOTE]
 ====
-Creating the {product-short} `ObjectBucketClaim` CR automatically creates both the {product-short} `ObjectBucketClaim` config map and secret. The config map and secret have the same name as the `ObjetBucketClaim` CR.
+Creating the {product-short} `ObjectBucketClaim` CR automatically creates both the {product-short} `ObjectBucketClaim` config map and secret. The config map and secret have the same name as the `ObjectBucketClaim` CR.
 ====
 
 After you create the `ObjectBucketClaim` CR, you can use the information stored in the config map and secret to make the information accessible to the {product-short} container as environment variables. Depending on the method that you used to install {product-short}, you add the access information to either the {product} Helm chart or Operator configuration.

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

@@ -113,7 +113,7 @@ dynamicPlugins:
 ----
 
 
-<1> The `default.` prefix identifes an item as a main menu item. You can add the `default.` prefix to both individual menu items or parent menu group configuration, such as `default.<menu_group_parent_item_name>` in the previous example.
+<1> The `default.` prefix identifies an item as a main menu item. You can add the `default.` prefix to both individual menu items or parent menu group configuration, such as `default.<menu_group_parent_item_name>` in the previous example.
 
 [NOTE]
 ====

modules/installation/proc-rhdh-deploy-aks-helm.adoc

@@ -16,7 +16,7 @@ You can deploy your {product-short} application on {aks-name} ({aks-short}) to a
 
 .Comparison of {aks-short} specifics with the base {product-short} deployment
 
-* *Permissions issue*: {product-short} containers might encounter permission-related errors, such as `Permission denied` when attempting certain operations. This error can be addresssed by adjusting the `fsGroup` in the `PodSpec.securityContext`.
+* *Permissions issue*: {product-short} containers might encounter permission-related errors, such as `Permission denied` when attempting certain operations. This error can be addressed by adjusting the `fsGroup` in the `PodSpec.securityContext`.
 
 * *Ingress configuration*: In AKS, configuring ingress is essential for accessing the installed {product-short} instance. Accessing the {product-short} instance requires enabling the Routing add-on, an NGINX-based Ingress Controller, using the following command:
 +

modules/installation/proc-rhdh-deploy-eks-operator.adoc

@@ -6,7 +6,7 @@
 
 The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
 
-.Additonal resources
+.Additional resources
 * For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
 
 == Installing the {product-short} Operator with the OLM framework