Use correct GCP links.
@@ -65,11 +65,11 @@ If your build or tests fail, it's likely due to the following:
* **Required build or test tools are not installed in the default container.**
Builds using the `rbe_ubuntu1604` config run by default inside an
- [`rbe-ubuntu16-04`](https://pantheon.corp.google.com/marketplace/details/google/rbe-ubuntu16-04)
+ [`rbe-ubuntu16-04`](https://console.cloud.google.com/marketplace/details/google/rbe-ubuntu16-04)
container, which includes tools common to many Bazel builds. However, if
your rules require tools not present in the default container, you must
create a custom container based on the
- [`rbe-ubuntu16-04`](https://pantheon.corp.google.com/marketplace/details/google/rbe-ubuntu16-04)
+ [`rbe-ubuntu16-04`](https://console.cloud.google.com/marketplace/details/google/rbe-ubuntu16-04)
container and include those tools as described later in this document.
* **Build or test targets are using rules that are incompatible with remote
@@ -102,7 +102,7 @@ gcloud docker -- pull gcr.io/cloud-marketplace/google/rbe-ubuntu16-04@sha256:<sh
```
Replace `<sha256-checksum>` with the SHA256 checksum value for
-[the latest container](https://pantheon.corp.google.com/gcr/images/cloud-marketplace/GLOBAL/google/rbe-ubuntu16-04).
+[the latest container](https://console.cloud.google.com/gcr/images/cloud-marketplace/GLOBAL/google/rbe-ubuntu16-04).
### Building the `rbe-ubuntu16-04` container from source
