diff --git a/Documentation/mainpage.dox.in b/Documentation/mainpage.dox.in
index 95f6a2779d4388d019696344f88e7daa57eb0af0..d5a1c5be665f91e6fc1c96ebdbd9a76fd6ddee28 100644
--- a/Documentation/mainpage.dox.in
+++ b/Documentation/mainpage.dox.in
@@ -33,7 +33,7 @@
  * - Selected benchmarks: https://opengeosys.org/docs/benchmarks
  * - Developer guide: https://opengeosys.org/docs/devguide
  * - Data Explorer (GUI) manual:
- * https://gitlab.opengeosys.org/ogs/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build
+ * https://gitlab.opengeosys.org/ogs/documentation/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build
  * - Discussion forum: https://discourse.opengeosys.org
  *
  * \section internal_modules Internal Modules
diff --git a/web/config/_default/config.toml b/web/config/_default/config.toml
index 7aed0b8e5aed5b3e0d5ae376004260c76361a4c4..47cbe5bf97c947b845d41abd82de45988de0f9da 100644
--- a/web/config/_default/config.toml
+++ b/web/config/_default/config.toml
@@ -108,7 +108,7 @@ weight = 5
 # docs
 [[menu.docs]]
 name = "Data Explorer Manual"
-url = "https://gitlab.opengeosys.org/ogs/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build"
+url = "https://gitlab.opengeosys.org/ogs/documentation/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build"
 post = "Manual for the graphical user interface for OpenGeoSys, the Data Explorer."
 [menu.docs.params]
 category = "Advanced"
diff --git a/web/content/docs/tools/getting-started/overview/index.md b/web/content/docs/tools/getting-started/overview/index.md
index 1455187314ff96081652fef2d74ffa70a487f0e5..07cd2448565277959c6ee9cc65c5b171570dee58 100644
--- a/web/content/docs/tools/getting-started/overview/index.md
+++ b/web/content/docs/tools/getting-started/overview/index.md
@@ -16,7 +16,7 @@ category = "Advanced"
 
 Here is an overview of the currently available command line tools, that might help you to construct your OpenGeoSys model. GUI-based tools are available too:
 
-- OpenGeoSys Data Explorer -- [Manual](https://gitlab.opengeosys.org/ogs/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build) / [Download](/releases)
+- OpenGeoSys Data Explorer -- [Manual](https://gitlab.opengeosys.org/ogs/documentation/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build) / [Download](/releases)
 - [GINA by BGR](https://teambeam.bgr.de/my/drive/folder/68)
 
 ----
diff --git a/web/content/docs/tools/preprocessing/IntegrateBoreholesIntoMesh/index.md b/web/content/docs/tools/preprocessing/IntegrateBoreholesIntoMesh/index.md
index 4115b60e71c293c013aff973a2f3b851a2509523..1b35810fed095f8869dfa8e7a3c7ef9e1f4c65da 100644
--- a/web/content/docs/tools/preprocessing/IntegrateBoreholesIntoMesh/index.md
+++ b/web/content/docs/tools/preprocessing/IntegrateBoreholesIntoMesh/index.md
@@ -6,18 +6,18 @@ author = "Julian Heinze"
 
 ## Description
 This tool is used to integrate line elements representing boreholes into a pre-existing 3D mesh.
-Corresponding nodes matching the (x,y)-coordinates given in the gml-file are found in the mesh and connected from top to bottom via line elements. 
-Each borehole (i.e. all points at a given (x,y)-location but at different depths) is assigned a unique material ID. 
+Corresponding nodes matching the (x,y)-coordinates given in the gml-file are found in the mesh and connected from top to bottom via line elements.
+Each borehole (i.e. all points at a given (x,y)-location but at different depths) is assigned a unique material ID.
 Vertical limits of boreholes can be specified via Material IDs and/or elevation.
 Points that do not match any mesh nodes or are located outside the mesh are ignored.
 ## Usage
 ```bash
     IntegrateBoreholesIntoMesh  -i <input file name> -o <output file name>
-                                 -g <geometry file name> [--min-id <a number>] 
-                                 [--max-id <a number>] [--min-elevation <a number>] 
+                                 -g <geometry file name> [--min-id <a number>]
+                                 [--max-id <a number>] [--min-elevation <a number>]
                                  [--max-elevation <a number>] [--] [--version] [-h]
 
-Where: 
+Where:
    -i <input file name>,  --input <input file name>
      (required)  Name of the input mesh (*.vtu)
 
@@ -51,7 +51,7 @@ Where:
 
 ## Example:
 In this example we apply the tool to integrate boreholes into a mesh.
-For this purpose we need to generate a .gml-file that holds the information about the x-y-coordinates for these boreholes. 
+For this purpose we need to generate a .gml-file that holds the information about the x-y-coordinates for these boreholes.
 The .gml-file is given as:
 
 ```bash
@@ -65,17 +65,17 @@ The .gml-file is given as:
  </points>
 </OpenGeoSysGLI>
 ```
-It is mandatory that the x-y-coordinates of the boreholes are aligned with nodes of the input mesh. 
+It is mandatory that the x-y-coordinates of the boreholes are aligned with nodes of the input mesh.
 Also they must be given with same precision as the mesh nodes, otherwise the tool will not find the nodes.
 
 ```bash
 IntegrateBoreholesIntoMesh -i input_3Dmesh.vtu -o boreholes_3Dmesh.vtu -g boreholes_xy.gml --min-id 2 --max-id 4
 ```
 
-**_NOTE:_** 
-If some boreholes are given at the beginning of the meshing process, it is recommended to use the OpenGeoSys DataExplorer -- [Manual](https://gitlab.opengeosys.org/ogs/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build) / [Download](/releases).
+**_NOTE:_**
+If some boreholes are given at the beginning of the meshing process, it is recommended to use the OpenGeoSys DataExplorer -- [Manual](https://gitlab.opengeosys.org/ogs/documentation/data_explorer_manual/-/jobs/artifacts/master/raw/ogsde-man.pdf?job=build) / [Download](/releases).
 At first, the nodes for boreholes can be integrated into the mesh, when the mesh is generated from a geometry.
-For this purpose, the boreholes and the boundaries of the geometry need to be imported in DataExplorer. 
+For this purpose, the boreholes and the boundaries of the geometry need to be imported in DataExplorer.
 Then this mesh can be used to create a 3D mesh, either with the DataExplorer or with [createLayeredMeshfromRaster](../../preprocessing/createLayeredMeshFromRasters/index.md), which then can be used for integrating boreholes.
 This procedure is useful because the mesh is generated in a way that the coordinates of the boreholes are nodes in the mesh.
 Otherwise the borehole's coordinates need to be adjusted according to a existing mesh.
@@ -84,5 +84,5 @@ This process is schematically depicted in Fig.1, below.
  <img src = schematic.png width = "100%" height = "100%">
 </p>
 <p align = "center">
-Fig.1 A schematic to visualize the methods of the tool. It does not refer to the upper example. 
+Fig.1 A schematic to visualize the methods of the tool. It does not refer to the upper example.
 </p>