Incorporating comments for GitOps 1.15 published docs build

Author: Dhruv-Soni11

argo_rollouts/using-cluster-scoped-rollouts-instance-to-manage-rollouts-resources.adoc

@@ -2,7 +2,7 @@
 include::_attributes/common-attributes.adoc[]
 [id="using-cluster-scoped-argo-rollouts-instance-to-manage-rollouts-resources"]
 = Using a cluster-scoped Argo Rollouts instance to manage rollout resources
-context: using-cluster-scoped-argo-rollouts-instance-to-manage-rollouts-resources
+:context: using-cluster-scoped-argo-rollouts-instance-to-manage-rollouts-resources
 
 toc::[]
 

argocd_application_sets/managing-app-sets-in-non-control-plane-namespaces.adoc

@@ -38,5 +38,5 @@ include::modules/gitops-allowing-scm-providers.adoc[leveloffset=+1]
 * link:https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/#the-applicationset-resource[The `ApplicationSet` resource]
 * link:https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Appset-Any-Namespace/[ApplicationSet in any namespace]
 * xref:../argocd_instance/argo-cd-cr-component-properties.adoc#argo-cd-cr-component-properties[Argo CD custom resource and component properties]
-* link:https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-SCM-Provider/#scm-provider-generator[SCM Provider Generator]
-* link:https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-Pull-Request/#pull-request-generator[Pull Request Generator]
+* link:https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-SCM-Provider/[SCM Provider Generator]
+* link:https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-Pull-Request/[Pull Request Generator]

gitops_cli_argocd/argocd-gitops-cli-reference.adoc

@@ -29,5 +29,5 @@ include::modules/gitops-argocd-cli-utility-commands.adoc[leveloffset=+1]
 * xref:../gitops_cli_argocd/configuring-argocd-gitops-cli.adoc#configuring-argocd-gitops-cli[Configuring the {gitops-shortname} CLI]
 * xref:../gitops_cli_argocd/logging-in-to-argocd-server-in-default-mode.adoc#logging-in-to-argocd-server-in-default-mode[Logging in to the Argo CD server in the default mode]
 * link:https://github.com/redhat-developer/gitops-operator/blob/7ac4b2ce179c167b39be259b8d9be37dc280f689/docs/OpenShift%20GitOps%20CLI%20User%20Guide.md#login-related-commands[OpenShift {gitops-shortname} CLI User Guide]
-* link:https://argo-cd.readthedocs.io/en/release-{upstream-ver}/user-guide/commands/argocd/[`argocd` command reference]
+* link:https://argo-cd.readthedocs.io/en/stable/user-guide/commands/argocd/[`argocd` Command Reference]
 //update the upstream version attribute value for every release

installing_gitops/installing-openshift-gitops.adoc

@@ -14,7 +14,7 @@ toc::[]
 * You have access to the {OCP} web console.
 * You are logged in as a user with the `cluster-admin` role.
 * You are logged in to the {OCP} cluster as an administrator.
-* Your cluster has the link:https://docs.openshift.com/container-platform/latest/installing/cluster-capabilities.html#marketplace-operator_cluster-capabilities[Marketplace capability] enabled or the Red Hat Operator catalog source configured manually.
+* Your cluster has the link:https://docs.openshift.com/container-platform/latest/installing/overview/cluster-capabilities.html#marketplace-operator_cluster-capabilities[Marketplace capability] enabled or the Red Hat Operator catalog source configured manually.
 
 [WARNING]
 ====

modules/gitops-creating-a-new-client-using-keycloak.adoc

@@ -73,7 +73,7 @@ spec:
       rootCA: ""
 ----
 
-* Optional: Customize the `spec.sso.keycloak` field to add the route name for the `keycloak` provider in the `ArgoCD` CR. Use this feature to support advanced routing use cases, such as balancing incoming traffic load among multiple link:https://docs.openshift.com/container-platform/latest/networking/ingress-sharding.html#nw-ingress-sharding_ingress-sharding[Ingress Controller shards].
+* Optional: Customize the `spec.sso.keycloak` field to add the route name for the `keycloak` provider in the `ArgoCD` CR. Use this feature to support advanced routing use cases, such as balancing incoming traffic load among multiple link:https://docs.openshift.com/container-platform/latest/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html#nw-ingress-sharding_configuring-ingress-cluster-traffic-ingress-controller[Ingress Controller sharding].
 +
 ** Add a `host` parameter in the `ArgoCD` CR by using the following example YAML:
 +
@@ -146,7 +146,7 @@ status:
 ----
 <1> Specifies the name of the route.
 <2> Specifies the name of the host key.
-
++
 [NOTE]
 ====
 The Keycloak instance takes 2-3 minutes to install and run.

observability/logging/viewing-argo-cd-logs.adoc

@@ -14,4 +14,4 @@ include::modules/gitops-storing-and-retrieving-argo-cd-logs.adoc[leveloffset=+1]
 [role="_additional-resources"]
 [id="additional-resources_{context}"]
 == Additional resources
-* link:https://docs.openshift.com/container-platform/latest/observability/logging/cluster-logging-deploying.html#cluster-logging-deploy-console_cluster-logging-deploying[Installing the {logging-title} using the web console]
+* link:https://docs.openshift.com/container-platform/4.16/observability/logging/cluster-logging-deploying.html#logging-loki-gui-install_cluster-logging-deploying[Installing the {logging-title} using the web console]