fix: 3 build todo patterns

content/en/docs/components/pipelines/legacy-v1/installation/standalone-deployment.md

@@ -284,10 +284,10 @@ bases:
 MountVolume.SetUp failed for volume "gcp-credentials-user-gcp-sa" : secret "user-gcp-sa" not found
 ```
 
-You should remove `use_gcp_secret` usages as documented in [Authenticating Pipelines to GCP](/docs/distributions/gke/pipelines/authentication-pipelines/#authoring-pipelines-to-use-workload-identity).
+You should remove `use_gcp_secret` usages as documented in [Authenticating Pipelines to GCP](https://www.kubeflow.org/docs/distributions/gke/pipelines/authentication-pipelines/#authoring-pipelines-to-use-workload-identity).
 
 
 ## What's next
 
-* [Connecting to Kubeflow Pipelines standalone on Google Cloud using the SDK](/docs/distributions/gke/pipelines/authentication-sdk/#connecting-to-kubeflow-pipelines-standalone-or-ai-platform-pipelines)
-* [Authenticating Pipelines to GCP](/docs/distributions/gke/pipelines/authentication-pipelines/#authoring-pipelines-to-use-workload-identity) if you want to use GCP services in Kubeflow Pipelines.
+* [Connecting to Kubeflow Pipelines standalone on Google Cloud using the SDK](https://www.kubeflow.org/docs/distributions/gke/pipelines/authentication-sdk/#connecting-to-kubeflow-pipelines-standalone-or-ai-platform-pipelines)
+* [Authenticating Pipelines to GCP](https://www.kubeflow.org/docs/distributions/gke/pipelines/authentication-pipelines/#authoring-pipelines-to-use-workload-identity) if you want to use GCP services in Kubeflow Pipelines.

content/en/docs/components/pipelines/legacy-v1/installation/upgrade.md

@@ -14,7 +14,7 @@ This page introduces notices and breaking changes you need to know when upgradin
 
 For upgrade instructions, refer to distribution specific documentations:
 
-* [Upgrading Kubeflow Pipelines on Google Cloud](/docs/distributions/gke/pipelines/upgrade/)
+* [Upgrading Kubeflow Pipelines on Google Cloud](https://www.kubeflow.org/docs/distributions/gke/pipelines/upgrade/)
 
 ## Upgrading to v2.0
 

content/en/docs/components/training/user-guides/mpi.md

@@ -28,7 +28,7 @@ cd mpi-operator
 kubectl apply -f deploy/v2beta1/mpi-operator.yaml
 ```
 
-Alternatively, follow the [getting started guide](https://www.kubeflow.org/docs/started/getting-started/) to deploy Kubeflow.
+Alternatively, follow the [getting started guide](https://www.kubeflow.org/docs/started/installing-kubeflow/) to deploy Kubeflow.
 
 An alpha version of MPI support was introduced with Kubeflow 0.2.0. You must be using a version of Kubeflow newer than 0.2.0.
 

content/en/docs/started/support.md

@@ -112,9 +112,8 @@ You can ask questions and make suggestions in the following places:
 * **Kubeflow documentation** for overviews and how-to guides. In particular,
   refer to the following documents when troubleshooting a problem:
 
-  * [Kubeflow installation and setup](/docs/started/getting-started/)
+  * [Kubeflow installation and setup](/docs/started/installing-kubeflow/)
   * [Kubeflow components](/docs/components/)
-  * [Further setup and troubleshooting](/docs/other-guides/)
 
 * **Kubeflow issue trackers** for known issues, questions, and feature requests.
   Search the open issues to see if someone else has already logged the problem 

netlify.toml

@@ -28,11 +28,7 @@ package = "netlify-plugin-checklinks"
     # If a link contains these patterns it will not fail the build, but will be reported as a TODO in the build log.
   todoPatterns = [
     # These are referenced by autogenerated files:
-
-    "public/docs/distributions/gke/",
     "public/docs/examples/shared-resources",
-    "public/docs/started/getting-started",
-    "public/docs/other-guides",
   ]
 
 [context.deploy-preview.environment]