diff --git a/.github/workflows/link-checker.config.json b/.github/workflows/link-checker.config.json
index 1fb12de241..09e5b99d32 100644
--- a/.github/workflows/link-checker.config.json
+++ b/.github/workflows/link-checker.config.json
@@ -3,10 +3,10 @@
     { "pattern": "^http://localhost:7007" },
     { "pattern": "^https://pkgs.devel.redhat.com" },
     { "pattern": "^https://gitlab.cee.redhat.com" },
+    { "pattern": "^https://docs\\.google\\.com" },
     { "pattern": "^https://docs.redhat.com" },
     { "pattern": "^https://developers.redhat.com" },
-    { "pattern": "^https://devservices.dpp.openshift.com" },
-    { "pattern": "^https://prow\\.ci\\.openshift\\.org" }
+    { "pattern": "^https://devservices.dpp.openshift.com" }
   ],
   "retryOn429": true,
   "retry-after": "30s",
diff --git a/docs/e2e-tests/CI.md b/docs/e2e-tests/CI.md
index 5b3ed60201..badc598e13 100644
--- a/docs/e2e-tests/CI.md
+++ b/docs/e2e-tests/CI.md
@@ -55,7 +55,7 @@ If the initial automatically triggered tests fail, OpenShift-CI will add a comme
 - **Environment:** Runs on ephemeral OpenShift clusters managed by Hive. Kubernetes jobs use ephemeral EKS and AKS clusters on spot instances managed by [Mapt](https://github.com/redhat-developer/mapt). GKE uses a long-running cluster.
 - **Configurations:**
   - Tests are executed on both **RBAC** (Role-Based Access Control) and **non-RBAC** namespaces. Different sets of tests are executed for both the **non-RBAC RHDH instance** and the **RBAC RHDH instance**, each deployed in separate namespaces.
-- **Access:** In order to access the environment, you can run the bash at `.ci/pipelines/ocp-cluster-claim-login.sh`. You will be prompted the prow url (the url from the openshift agent, which looks like https://prow.ci.openshift.org/...). Once you have claimed a cluster, this script will forward the cluster web console url along with the credentials.
+- **Access:** In order to access the environment, you can run the bash at `.ci/pipelines/ocp-cluster-claim-login.sh`. You will be prompted for the Prow URL (the URL from the OpenShift agent, which looks like https://prow.ci.openshift.org/...). Once you have claimed a cluster, this script will forward the cluster web console URL along with the credentials.
 - **Steps:**
   1. **Detection:** OpenShift-CI detects the PR event.
   2. **Environment Setup:** The test environment is set up using the `openshift-ci-tests.sh` script (see the [High-Level Overview](#high-level-overview-of-openshift-ci-testssh)).