codefresh-io · NimRegev · Mar 1, 2023 · Mar 1, 2023
@@ -105,4 +105,4 @@ We are working to enhance our access control model by adding another layer to pr
 * A more granular permission model for dynamic resources that are non-GitOps controlled, but created from a GitOps-controlled entity, for example, workflows
 
 ### What to read next
-[Codefresh architecture]({{site.baseurl}}/_docs/getting-started/architecture/)
+[Codefresh architecture]({{site.baseurl}}/docs/getting-started/architecture/)
@@ -216,5 +216,5 @@ For a Git provider and a hybrid runtime, select the authentication mechanism: Co
 >Hosted runtimes can have either Codefresh or PAT token authentication mechanisms. Custom provider authentication is not supported.
 
 1. In the Codefresh UI, go to [Authentication](https://g.codefresh.io/2.0/account-settings/authentication?providerName=github){:target="\_blank"}.
-1. Select the runtime, and click ![](/images/administration/users/icon-Edit.png?display=inline-block) **Edit**. 
+1. Select the runtime, and click the **Edit** icon. 
 1. Select the OAuth authentication provider account.
@@ -1,7 +1,7 @@
 ---
 title: "Codefresh IP addresses"
 description: " "
-canonical_url: 'https://codefresh.io/docs/docs/administration/account-user-management/platform-ip-addresses/'
+canonical_url: 'https://codefresh.io/docs/docs/administration/platform-ip-addresses/'
 group: administration
 toc: true
 

@@ -157,6 +157,4 @@ steps:
 {% endraw %}
 {% endhighlight %}
 
-To fully automate this pipeline, set a [cron trigger]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/cron-triggers/) for this pipeline. The cron-trigger is responsible for running this pipeline, (and therefore synchronizing the teams), in a fully automated manner. 
-This way you can synchronize your teams every day/week/hour depending on you cron trigger setup.
 
@@ -665,7 +665,7 @@ max-width="70%"
 A rollout is initiated when there is an Argo CD sync due to a change in the desired state.  
 Visualize ongoing and completed rollouts by deployments in **Services**. 
 
-> To view and manage a rollout, you must have an Argo `rollout` resource defined for your application, and [install Argo Rollouts in the cluster]({site.baseurl}}/docs/deployment/install-argo-rollouts).  
+> To view and manage a rollout, you must have an Argo `rollout` resource defined for your application, and [install Argo Rollouts in the cluster]({{site.baseurl}}/docs/deployment/install-argo-rollouts/).  
 
 For detailed information on Argo Rollouts, see [Argo Rollouts documentation](https://argoproj.github.io/argo-rollouts/){:target="\_blank"}.
 

@@ -1,7 +1,7 @@
 ---
 title: "Images in Codefresh"
 description: ""
-canonical_url: 'https://codefresh.io/docs/docs/deployments/gitops/images/'
+canonical_url: 'https://codefresh.io/docs/dashboards/images/'
 group: deployment
 toc: true
 ---

@@ -1,7 +1,7 @@
 ---
 title: "Create and commit resources for application"
 description: ""
-canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quickstart/create-app-specs/'
+canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quick-start/create-app-specs/'
 group: getting-started
 sub-group: quick-start
 toc: true

@@ -1,7 +1,7 @@
 ---
 title: "Update image tag for application"
 description: ""
-canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quickstart/create-rollout/'
+canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quick-start/create-rollout/'
 group: getting-started
 sub-group: quick-start
 toc: true

@@ -1,7 +1,7 @@
 ---
 title: "Provision a hosted runtime"
 description: ""
-canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quickstart/install-hosted/'
+canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quick-start/install-hosted/'
 group: getting-started
 sub-group: quick-start
 toc: true

@@ -1,7 +1,7 @@
 ---
 title: "Install a hybrid runtime"
 description: ""
-canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quickstart/runtime/'
+canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quick-start/runtime/'
 group: getting-started
 sub-group: quick-start
 toc: true

@@ -1,7 +1,7 @@
 ---
 title: "Prepare for hybrid runtime installation"
 description: ""
-canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quickstart/verify-requirements/'
+canonical_url: 'https://codefresh.io/docs/docs/quick-start/gitops-quick-start/verify-requirements/'
 group: getting-started
 sub-group: quick-start
 toc: true

@@ -237,7 +237,7 @@ All you need to do is to configure the browser to trust the URL and receive cont
 
 The Activity Log is a quick way to monitor notifications for runtime events such as upgrades. A pull-down panel in the Codefresh toolbar, the Activity Log shows ongoing, success, and error notifications, sorted by date, starting with today's date.
 
-1. In the Codefresh UI, on the top-right of the toolbar, select ![](/images/pipeline/monitoring/pipeline-activity-log-toolbar.png?display=inline-block) **Activity Log**.
+1. In the Codefresh UI, on the top-right of the toolbar, select **Activity Log**.
 1. To see notifications for provisioned runtimes, filter by **Runtime**.
 
   {% include image.html

@@ -1195,7 +1195,7 @@ Logs are displayed if the resource has logs:
 * For online viewing, you have free-text search and line-wrap functionalities. 
 * For offline viewing and analysis, you can download the complete log into a text file.   
 
-For details, see [Current State Tree view]({{site.baseurl}}/docs/deployment/applications-dashboard/view-modes-for-application-resources/).
+For details, see [Current State Tree view]({{site.baseurl}}/docs/deployment/applications-dashboard/#select-view-mode-for-the-applications-dashboard).
 
 #### Application rollout visualization 
 In addition to installing Argo Rollouts in your cluster, visualize Argo Rollout history and progress directly in the Applications (deployment) dashboard. Visualize rollouts from multiple clusters and runtimes in a single centralized location through the Deployment tab.