Fix broken links (codefresh-io#1175)

Author: NimRegev

_docs/administration/administration-overview.md

@@ -54,4 +54,4 @@ Users in a Codefresh account can personalize settings such as notifications, dat
 {% if page.layout == "argohub" %}
 They can also securely manage Git Personal Access Tokens (PATs) to control access to repositories, and protect sensitive information.
 {% endif %}
-See [User settings]({{site.baseurl}}/=/docs/administration/user-self-management/).
+See [User settings]({{site.baseurl}}/docs/administration/user-self-management/).

_docs/deployments/gitops/applications-dashboard.md

@@ -370,7 +370,7 @@ Every resource has a context menu that opens on clicking the three dots on the r
 
 {{site.data.callout.callout_tip}}
 **TIP**   
-If you have deep links configured for applications/resources for Hybrid GitOps Runtimes, these are also displayed in the context menu. To configure deep links in Codefresh, see [(Hybrid GitOps) Configure Deep Links to applications & resources]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-configure-deep-links-to-applications--resources).
+If you have deep links configured for applications/resources for Hybrid GitOps Runtimes, these are also displayed in the context menu. To configure deep links in Codefresh, see [(Hybrid GitOps) Configure Deep Links to applications & resources]({{site.baseurl}}/docs/installation/gitops/manage-runtimes/#configure-deep-links-to-applications--resources).
 {{site.data.callout.end}}
 
 

_docs/getting-started/gitops-codefresh.md

@@ -51,8 +51,7 @@ Codefresh offers two models for GitOps deployments:
 * Hybrid GitOps, which is a customer-managed version of Argo CD. The  Hybrid GitOps runtime is hosted on the customer cluster and managed by the customer.  
   The Hybrid GitOps offering retains runtimes within the customer infrastructure to comply your security rewhile giving you the power of Argo CD with Codefresh’s CI and CD tools, to help achieve continuous integration and continuous delivery goals.
 
-Review [GitOps runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).  
-For installation, see [Hosted GitOps setup]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/) and [Hybrid GitOps installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/).
+Review [GitOps runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/) and [Hybrid GitOps installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).
 
 ## Argo CD applications
 

_docs/installation/gitops/gitops-runtime.md

@@ -78,7 +78,7 @@ You can install the Hybrid GitOps Runtime via Helm using one of two options, tai
 Within the same account, you can install one Hybrid GitOps Runtime per cluster.  
 To install additional Hybrid GitOps Runtimes in the same account, each Runtime must be installed on a different cluster. Every Runtime within the same account must have a unique name.
 
-See [Installing additional GitOps Runtimes from the Codefresh UI]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation#install-additional-gitops-runtimes-in-account), or using [Terraform]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/install-gitops-runtime-via-terraform).
+See [Installing additional GitOps Runtimes from the Codefresh UI]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation#install-additional-gitops-runtimes-in-account), or using [Terraform]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#install-gitops-runtime-via-terraform).
 
 <!--- ## Hosted GitOps
 The SaaS version of GitOps, Hosted GitOps has Argo CD installed in the Codefresh cluster.

_posts/2022-08-15-august-gitops.md

@@ -100,7 +100,7 @@ max-width="60%"
 {: .table .table-bordered .table-hover}
 | Item    | Description     |
 | ----------  |  -------- |
-| `CF_HOST`       | Deprecated from v 0.0.460 and higher in CI integrations. Recommend using `CF_RUNTIME_NAME` instead. See [CI integrations argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/ci-argument-reference/)  . |
+| `CF_HOST`       | Deprecated from v 0.0.460 and higher in CI integrations. Recommend using `CF_RUNTIME_NAME` instead. See [CI integrations argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-argument-reference/)  . |
 | `GHCR_GITHUB_TOKEN_AUTHENTICATION`       | New value for `CF_CONTAINER_REGISTRY_INTEGRATION` argument. Can be selected for GitHub Container (GHCR) registries even when you don’t have a GHCR integration in Codefresh. See [GitHub Action-Codefresh integration settings]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/github-actions/#github-action-gitops-integration-settings).|
 
 ## Bug fixes