diff --git a/scripts/ci/jobs/web.yml b/scripts/ci/jobs/web.yml
index e44008364bf5b30734433911498f986532cd5886..c17667f004d6c6071d13a8de004c7c654b83f1a7 100644
--- a/scripts/ci/jobs/web.yml
+++ b/scripts/ci/jobs/web.yml
@@ -12,7 +12,7 @@ web url checker:
     - >
       urlchecker check --retry-count 5 --file-types .pandoc,.md
       --white-listed-files releases/*
-      --white-listed-urls https://jenkins.opengeosys.org/job/ufz/job/ogs-container-maker/job/master/build,http://yourproxy.example.com,https://apt.kitware.com/ubuntu/,https://github.com/YOUR-USERNAME/ogs,https://jenkins.opengeosys.org/github-webhook/,http://localhost:1313,https://github.com/ufz/ogs/pull/\$1,http://www.opengeosys.org/images/xsd/OpenGeoSysXXX.xsd,https://\`-protocol
+      --white-listed-urls https://jenkins.opengeosys.org/job/ufz/job/ogs-container-maker/job/master/build,http://yourproxy.example.com,https://apt.kitware.com/ubuntu/,https://github.com/YOUR-USERNAME/ogs,https://jenkins.opengeosys.org/github-webhook/,http://localhost:1313,https://github.com/ufz/ogs/pull/\$1,http://www.opengeosys.org/images/xsd/OpenGeoSysXXX.xsd,https://\`-protocol,https://gitlab.opengeosys.org/ogs/ogs/-/merge_requests/new,https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/_out/images?job=container
       content
 
 preview web site:
diff --git a/web/content/_index.pandoc b/web/content/_index.pandoc
index d94e5d411c596759b2230c720ad714d9defacde2..3c1a8e91e34de41a02b51e76bfa4ab7013ecab4a 100644
--- a/web/content/_index.pandoc
+++ b/web/content/_index.pandoc
@@ -107,7 +107,7 @@ features:
         Implement your new feature and [let the CI system](/docs/devguide/development-workflows/continuous-integration) run sophisticated tests automatically for you incorporating multiple computing platforms, a magnitude of software configurations and a whole array of CPU intensive complex test simulation runs.
     - headline: Get help from core developers
       textline: |
-        Once your feature is ready the [code review process](/docs/devguide/development-workflows/code-reviews/) starts. A helpful [core developer](https://gitlab.opengeosys.org/ogs/ogs/-/graphs/gitlab-ci) checks the proposed change for general acceptance and may give hints for improvement (of e.g. the computational performance or the code structure). Once the iterative feedback loop between you, code reviewer(s) and the automated test system satisfies all aspects the proposed change is merged into the main development line.
+        Once your feature is ready the [code review process](/docs/devguide/development-workflows/code-reviews/) starts. A helpful [core developer](https://gitlab.opengeosys.org/ogs/ogs/-/graphs/master) checks the proposed change for general acceptance and may give hints for improvement (of e.g. the computational performance or the code structure). Once the iterative feedback loop between you, code reviewer(s) and the automated test system satisfies all aspects the proposed change is merged into the main development line.
   visual:
     permalink: "/features/OGS-Software-Engineering-Small.png"
     alt: Dev workflow
diff --git a/web/content/docs/benchmarks/liquid-flow/buildup_test.pandoc b/web/content/docs/benchmarks/liquid-flow/buildup_test.pandoc
index c653911c9a2666fb382c5ca84f91620d5e9cba69..0819f6f010f50fbaca19611f62d022fd21fbb2fb 100644
--- a/web/content/docs/benchmarks/liquid-flow/buildup_test.pandoc
+++ b/web/content/docs/benchmarks/liquid-flow/buildup_test.pandoc
@@ -89,7 +89,7 @@ The pressure buildup test is comparable to a pumping recovery test as
 the extraction rate is first kept constant at $Q$, and then becomes zero
 at $t=t_p$. This benchmark then adopts the same assumptions as in the
 [Theis'
-problem](https://benchmarks.opengeosys.org/docs/benchmarks/liquid-flow/liquid-flow-theis-problem/).
+problem](https://www.opengeosys.org/docs/benchmarks/liquid-flow/liquid-flow-theis-problem/).
 The analytical solution of the pressure difference $\Delta p$ with
 respect to the initial pressure $p_0$ is the sum of two Theis curves:
 one starting at $t=0$ and another starting at $t=t_p$ but with an
diff --git a/web/content/docs/devguide/testing/gitlab-ci.pandoc b/web/content/docs/devguide/testing/gitlab-ci.pandoc
index 64626dfc91dd0d22f1c0aed356b6bcb5f6c8b2d5..cfbe252be8f35a497b3fb2a58b822b97ccc98a7b 100644
--- a/web/content/docs/devguide/testing/gitlab-ci.pandoc
+++ b/web/content/docs/devguide/testing/gitlab-ci.pandoc
@@ -13,7 +13,7 @@ weight = 1022
 
 [GitLab CI](https://docs.gitlab.com/ee/ci/) is a powerful [Continuous Integration](../../development-workflows/continuous-integration) system integrated into GitLab.
 
-The tasks of the CI system are configured in [scripts inside the OGS source code](https://gitlab.opengeosys.org/ogs/ogs/-/tree/gitlab-ci/scripts/ci). The entrypoint is defined in [.gitlab-ci.yml](https://gitlab.opengeosys.org/ogs/ogs/-/blob/gitlab-ci/.gitlab-ci.yml). Scripting and versioning the configuration together with the source code is very powerful, e.g. if you introduce a new OGS CMake configuration in a merge request even the change of the CI jobs configuration or jobs environment (Docker container definition) can be part of the merge request.
+The tasks of the CI system are configured in [scripts inside the OGS source code](https://gitlab.opengeosys.org/ogs/ogs/-/tree/master/scripts/ci). The entrypoint is defined in [.gitlab-ci.yml](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/.gitlab-ci.yml). Scripting and versioning the configuration together with the source code is very powerful, e.g. if you introduce a new OGS CMake configuration in a merge request even the change of the CI jobs configuration or jobs environment (Docker container definition) can be part of the merge request.
 
 ## GitLab Pipeline
 
diff --git a/web/content/docs/userguide/basics/container.pandoc b/web/content/docs/userguide/basics/container.pandoc
index f10c1902fe23f22422f776a0d09f47c88c2b5fff..b50a39e67564dad7ba802bd057217f178a7a66c7 100644
--- a/web/content/docs/userguide/basics/container.pandoc
+++ b/web/content/docs/userguide/basics/container.pandoc
@@ -25,7 +25,7 @@ Simply download an image from the [releases]({{< ref "/releases" >}}) page.
 
 #### Option: Download image from the latest master-branch build
 
-Simply download an image from the [latest master-branch build](https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/_out/images/?job=images) page.
+Simply download an image from the [latest master-branch build](https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/_out/images?job=container) page.
 
 ### Run OGS inside a Container (called from outside)
 
diff --git a/web/content/ogs-5/index.pandoc b/web/content/ogs-5/index.pandoc
index 23a19f54c197b2f5c3a558c87faa25ad2766f5c8..68af22293e232eb6bfc05d6e0242cd017451b4ad 100644
--- a/web/content/ogs-5/index.pandoc
+++ b/web/content/ogs-5/index.pandoc
@@ -37,7 +37,7 @@ On Windows you may have to install the appropriate Visual Studio Redistributable
 
 ### Development builds
 
-You can get the latest OpenGeoSys-5 (with recent bug-fixes) version from our [Jenkins CI system](https://jenkins.opengeosys.org/job/ufz/job/ogs5/job/master/). Binaries for Windows (64-Bit) and Linux are provided for the OGS FEM-simulator under *"Last successful Artifacts"*.
+TODO: You can get the latest OpenGeoSys-5 (with recent bug-fixes) version from the CI system. Binaries for Windows (64-Bit) and Linux are provided for the OGS FEM-simulator under *"Last successful Artifacts"*.
 
 ### Source code