fixed leftovers

Author: themr0c

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

@@ -33,4 +33,4 @@ image::rhdh-plugins-reference/deployment_summary.png[Deployment summary]
 [role="_additional-resources"]
 .Additional resources
 
-* For more information on installing dynamic plugins, see link:{installing-and-viewing-plugins-book-link}[{installing-and-viewing-plugins-book-title}].
+* For more information on installing dynamic plugins, see {installing-and-viewing-plugins-book-link}[{installing-and-viewing-plugins-book-title}].

artifacts/rhdh-plugins-reference/argocd/argocd-plugin-user.adoc

@@ -31,4 +31,4 @@ image::rhdh-plugins-reference/deployment_summary.png[Deployment summary]
 [role="_additional-resources"]
 .Additional resources
 
-* link:{installing-and-viewing-plugins-book-link}[{installing-and-viewing-plugins-book-title}].
+* {installing-and-viewing-plugins-book-link}[{installing-and-viewing-plugins-book-title}].

modules/installation/proc-install-rhdh-operator-airgapped-full.adoc

@@ -14,7 +14,7 @@ If your network has access to the registry through a bastion host, you can use t
 * You have installed the GNU `sed` command line text editor.
 * You have installed `umoci` CLI tool.
 * You have an active `oc registry`, `podman`, or `skopeo` session to the `registry.redhat.io` {company-name} Ecosystem Catalog. For more information, see link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
-* You have installed the `opm` CLI tool. For more information, see link:{ocp-docs-link}/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
+* You have installed the `opm` CLI tool. For more information, see {ocp-docs-link}/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
 
 .Procedure
 . Download the mirroring script to disk by running the following command:

modules/observe/proc-forward-audit-log-splunk.adoc

@@ -65,7 +65,7 @@ metadata:
   namespace: openshift-logging
 ----
 
-For more information, see link:{ocp-docs-link}/html-single/logging/index#logging-create-clf_configuring-log-forwarding[Creating a log forwarder].
+For more information, see {ocp-docs-link}/html-single/logging/index#logging-create-clf_configuring-log-forwarding[Creating a log forwarder].
 --
 . Define the following `ClusterLogForwarder` configuration using OpenShift web console or OpenShift CLI:
 .. Specify the `log-collector` as `serviceAccount` in the YAML file:
@@ -94,7 +94,7 @@ inputs:
         maxRecordsPerSecond: 100
 ----
 
-For more information, see link:{ocp-docs-link}/html-single/logging/index#cluster-logging-collector-log-forward-logs-from-application-pods_configuring-log-forwarding[Forwarding application logs from specific pods].
+For more information, see {ocp-docs-link}/html-single/logging/index#cluster-logging-collector-log-forward-logs-from-application-pods_configuring-log-forwarding[Forwarding application logs from specific pods].
 --
 .. Configure outputs to specify where the captured logs are sent. In this step, focus on the `splunk` type. You can either use `tls.insecureSkipVerify` option if the Splunk endpoint uses self-signed TLS certificates (not recommended) or provide the certificate chain using a Secret.
 +