diff --git a/Documentation/.vale/Vocab/ogs/accept.txt b/Documentation/.vale/Vocab/ogs/accept.txt
index 009a70bbc018d680cd2cc160bbf3ae9839cc2fe8..f9cfb3cc0d297b2333cef58a2c60b85b1116c57a 100644
--- a/Documentation/.vale/Vocab/ogs/accept.txt
+++ b/Documentation/.vale/Vocab/ogs/accept.txt
@@ -61,6 +61,7 @@ Jacobian
 Johannsen
 Jong
 Jupyter
+Jupytext
 Juwels
 Kinzelbach
 Kitware
@@ -79,6 +80,7 @@ MFront
 Mikelic
 Mises
 MODFLOW
+MTest
 nbconvert
 nbdime
 Netbeans
@@ -133,6 +135,7 @@ TESPy
 Theis
 Thuringia
 Thuringian
+TODO[s?]
 Ucar
 Unlicense
 Unstrut
diff --git a/web/content/docs/benchmarks/small-deformations/ModifiedCamClay/index.md b/web/content/docs/benchmarks/small-deformations/ModifiedCamClay/index.md
index 1101656ecc9e29cf618f24096a534921a90bd396..c2b939723f1fc96b7d68dab1bf6f6dbd4237c9aa 100644
--- a/web/content/docs/benchmarks/small-deformations/ModifiedCamClay/index.md
+++ b/web/content/docs/benchmarks/small-deformations/ModifiedCamClay/index.md
@@ -17,7 +17,7 @@ Five tests are presented:
 {{< data-link >}}
 
 of which the last three have the same test program but use different implementations of the modified Cam clay model.
-The mfront-files can be found at [here](https://gitlab.opengeosys.org/ogs/ogs/-/tree/master/MaterialLib/SolidModels/MFront).
+The MFront-files can be found at [here](https://gitlab.opengeosys.org/ogs/ogs/-/tree/master/MaterialLib/SolidModels/MFront).
 
 ## Problem description
 
diff --git a/web/content/docs/benchmarks/th2m/th2m_strain_dependent_permeability/index.md b/web/content/docs/benchmarks/th2m/th2m_strain_dependent_permeability/index.md
index 208d3122c7773afd13fb2811a088df5a561d23c1..d67964cf3192f1198a9f3e180a53dee6f0ccb5d7 100644
--- a/web/content/docs/benchmarks/th2m/th2m_strain_dependent_permeability/index.md
+++ b/web/content/docs/benchmarks/th2m/th2m_strain_dependent_permeability/index.md
@@ -12,6 +12,6 @@ draft = true
 
 ## Problem description
 
-Todo
+TODO
 
 ## Results and evaluation
diff --git a/web/content/docs/devguide/documentation/jupyter-docs/index.md b/web/content/docs/devguide/documentation/jupyter-docs/index.md
index 82ae9b0526689f9bc59d01c3f1d0433863131c73..672c79a89eb9e3d4c62af13419c0655d06c40210 100644
--- a/web/content/docs/devguide/documentation/jupyter-docs/index.md
+++ b/web/content/docs/devguide/documentation/jupyter-docs/index.md
@@ -14,10 +14,10 @@ parent = "development-workflows"
 
 ## Create a new notebook
 
-Create a new notebook file in `Tests/Data` (either as regular `.ipynb`-files or as Markdown-based notebooks via [jupytext](https://jupytext.readthedocs.io/en/latest)). See examples:
+Create a new notebook file in `Tests/Data` (either as regular `.ipynb`-files or as Markdown-based notebooks via [Jupytext](https://jupytext.readthedocs.io/en/latest)). See examples:
 
 - [SimpleMechanics.ipynb](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/Tests/Data/Mechanics/Linear/SimpleMechanics.ipynb) (regular `.ipynb`-notebook)
-- [Linear_Disc_with_hole.md](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/Tests/Data/Mechanics/Linear/DiscWithHole/Linear_Disc_with_hole.md) (jupytext-based notebook in Markdown)
+- [Linear_Disc_with_hole.md](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/Tests/Data/Mechanics/Linear/DiscWithHole/Linear_Disc_with_hole.md) (Jupytext-based notebook in Markdown)
 
 ## Add web meta information
 
@@ -38,7 +38,7 @@ If the notebook result should appear as a page on the web documentation a frontm
 
 <div class='note'>
 
-In jupytext-based notebooks you can add the frontmatter within the `<!-- #raw -->`- and `<!-- #endraw -->`-markers:
+In Jupytext-based notebooks you can add the frontmatter within the `<!-- #raw -->`- and `<!-- #endraw -->`-markers:
 
 ```md
 <!-- #raw -->
@@ -125,9 +125,9 @@ ctest -R nb -j 4 --output-on-failure
 
 ## Advanced topics
 
-### jupytext usage
+### Jupytext usage
 
-If you use the [execution environment](#execution-environment) [jupytext](https://jupytext.readthedocs.io/en/latest) as already configured and its usage is transparent:
+If you use the [execution environment](#execution-environment) [Jupytext](https://jupytext.readthedocs.io/en/latest) is already configured and its usage is transparent:
 
 - Double-click on a markdown file will open it as a Notebook
 - Upon saving or executing a linked `.ipynb`-file is created in the background which stores outputs
@@ -141,7 +141,7 @@ On the web site or MR web previews on pages generated by a notebook there is a n
 
 - Click the button to launch the notebook in BinderHub.
 - The environment running in BinderHub is defined in [bilke/binder-ogs-requirements at GitHub](https://github.com/bilke/binder-ogs-requirements)
-- When clicking the link it launches a Jupyter Lab instance pre-configured with ogs [via wheel](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/Tests/Data/requirements-ogs.txt#L2), clones the current ogs repo in it and opens the respective notebook ready to run. Please note that startup times may be several minutes and the computing resources are limited (1 core, 2GB RAM). For improved performance we would need to setup own infrastructure. Also currently only works for serial ogs configs.
+- When clicking the link it launches a Jupyter Lab instance pre-configured with ogs [via wheel](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/Tests/Data/requirements-ogs.txt#L2), clones the current ogs repo in it and opens the respective notebook ready to run. Please note that startup times may be several minutes and the computing resources are limited (1 core, 2GB RAM). For improved performance we would need to setup own infrastructure. Also currently only works for serial ogs configurations.
 
 ### PyVista notebooks on headless Linux systems
 
diff --git a/web/content/docs/devguide/documentation/todo/index.md b/web/content/docs/devguide/documentation/todo/index.md
index 38d5ab1ba513a85bea34a91a366ffe0b3bda6a9b..3e6a99f4df7e5e53eff8e9868f704917be950deb 100644
--- a/web/content/docs/devguide/documentation/todo/index.md
+++ b/web/content/docs/devguide/documentation/todo/index.md
@@ -13,7 +13,8 @@ It can be obtained by running script ```todo-check.sh``` from ```/web/content/do
 ## TODOs in userguide/basics
 
 ## TODOs in userguide/blocks
-```
+
+```bash
 blocks/curves.md-19-</div>
 blocks/curves.md-20-
 blocks/curves.md:21:TODO: Add general description
@@ -96,7 +97,8 @@ blocks/processes.md:159:The global non-linear equation system can be solved eith
 ```
 
 ## TODOs in userguide/features
-```
+
+```bash
 features/python_bc.md-31-## Using python boundary condition in project file
 features/python_bc.md-32-
 features/python_bc.md:33:TODO: add description of how to call python bc from the boundary condition tag
@@ -123,4 +125,3 @@ features/mfront.md:110:TODO: add content
 ```
 
 ## TODOs in userguide/troubleshooting
-
diff --git a/web/content/docs/devguide/getting-started/build-configuration/index.md b/web/content/docs/devguide/getting-started/build-configuration/index.md
index 57fccab4fb388c1fc20ca67916a1f2d422b05c9d..f0dda1acd38c73e8882000337553fd887342985a 100644
--- a/web/content/docs/devguide/getting-started/build-configuration/index.md
+++ b/web/content/docs/devguide/getting-started/build-configuration/index.md
@@ -146,7 +146,7 @@ CC=mpicc CXX=mpic++ cmake ../ogs -G Ninja -DCMAKE_BUILD_TYPE=Release -DOGS_USE_P
 
 <div class='win'>
 
-CMake comes with a graphical tool called **cmake-gui**. You can find it in the **Windows Start Menu**. First you need to set the source and build directory. Then click **Configure**. Now choose the generator to be used (e.g. **Visual Studio {{< dataFile "versions.minimum_version.msvc.number" >}} {{< dataFile "versions.minimum_version.msvc.year" >}}** for Visual Studio {{< dataFile "versions.minimum_version.msvc.year" >}}). Now choose your desired configuration options by toggling the corresponding checkboxes. Click **Configure** again. Click **Configure** often enough until the **Generate**-button becomes visible. Pressing **Generate** will finally generate the project files inside the chosen build directory.
+CMake comes with a graphical tool called `cmake-gui`. You can find it in the **Windows Start Menu**. First you need to set the source and build directory. Then click **Configure**. Now choose the generator to be used (e.g. **Visual Studio {{< dataFile "versions.minimum_version.msvc.number" >}} {{< dataFile "versions.minimum_version.msvc.year" >}}** for Visual Studio {{< dataFile "versions.minimum_version.msvc.year" >}}). Now choose your desired configuration options by toggling the corresponding checkboxes. Click **Configure** again. Click **Configure** often enough until the **Generate**-button becomes visible. Pressing **Generate** will finally generate the project files inside the chosen build directory.
 
 </div>
 
diff --git a/web/content/docs/devguide/getting-started/build-configuration_for_MPI_PETSc/configure_for_mpi_and_petsc.md b/web/content/docs/devguide/getting-started/build-configuration_for_MPI_PETSc/configure_for_mpi_and_petsc.md
index 5774336d10bbd6af81b3c61698317c764202da2e..36bad0db9561ee845dd5f0ca63dd76e900c49cbe 100644
--- a/web/content/docs/devguide/getting-started/build-configuration_for_MPI_PETSc/configure_for_mpi_and_petsc.md
+++ b/web/content/docs/devguide/getting-started/build-configuration_for_MPI_PETSc/configure_for_mpi_and_petsc.md
@@ -88,7 +88,7 @@ cmake --build --preset release-petsc
 ```
 
 The ```release-petsc``` preset is based on the ```release``` preset.
-It can be customized by passing additional variable with ```-D``` flags to cmake command.
+It can be customized by passing additional variable with ```-D``` flags to `cmake` command.
 
 If you want to install PETSc yourself, please see Section [Install PETSc](#install-petsc-manually).
 
@@ -134,7 +134,7 @@ Please note, that the PETSc package is usually build in release mode independent
 
 <div class='win'>
 
-PESTSc is recommended to use on Linux.
+PETSc is recommended to use on Linux.
 On Windows, it only runs on UNIX emulator Cygwin.
 A detailed description about how to use PETSc on Windows is available on this PETSc site: <https://petsc.org/release/install/windows/>.
 
diff --git a/web/content/docs/devguide/packages/python-env/index.md b/web/content/docs/devguide/packages/python-env/index.md
index 887d241a9f08785919293eef789d81c4170ab8e3..e703e3c6d1984c9cf8d3178fa9735a46d3da577a 100644
--- a/web/content/docs/devguide/packages/python-env/index.md
+++ b/web/content/docs/devguide/packages/python-env/index.md
@@ -31,7 +31,7 @@ To manually add Python packages run the following inside your build-directory:
 .venv/bin/pip install python-package-name
 ```
 
-To activate the environment run `source .venv/bin/activate` inside your build directory. If you have the [direnv](https://direnv.net)-tool installed and setup the virtual environment will be activated automatically upon changing into the build directory.
+To activate the environment run `source .venv/bin/activate` inside your build directory. If you have the [`direnv`](https://direnv.net)-tool installed and setup the virtual environment will be activated automatically upon changing into the build directory.
 
 ### Pip & Benchmarks
 
diff --git a/web/content/docs/devguide/testing/gitlab-ci/index.md b/web/content/docs/devguide/testing/gitlab-ci/index.md
index e7fce01fba588c69166e92e109660815b7f2ac3b..3c53257279a1e1c405974b88310f33d714f64ec3 100644
--- a/web/content/docs/devguide/testing/gitlab-ci/index.md
+++ b/web/content/docs/devguide/testing/gitlab-ci/index.md
@@ -68,7 +68,7 @@ You can change the pipeline by editing the `.gitlab-ci.yml` and `scripts/ci/jobs
 These variables in `.gitlab-ci.yml` modify the pipeline:
 
 - `BUILD_TESTS`: Set this to `false` to disable unit tests.
-- `BUILD_CTEST`: Set this to `false` to disable ctest (benchmark) tests.
+- `BUILD_CTEST`: Set this to `false` to disable CTest (benchmark) tests.
 - `CTEST_ARGS`: Supply additional arguments to the `ctest`-command to select which benchmarks are run, e.g.:
   - `-R nb` would select all notebook-based tests and would disable all other benchmarks
   - `-LE large` would exclude all tests with label `large`
diff --git a/web/content/docs/processes/heat-transport/HEAT_TRANSPORT_BHE/index.md b/web/content/docs/processes/heat-transport/HEAT_TRANSPORT_BHE/index.md
index 2b0da0505103957f51215da6e3b9907fa9d46588..c09af614b4fd9d9bdee0fcab0c2bc92af72e620e 100644
--- a/web/content/docs/processes/heat-transport/HEAT_TRANSPORT_BHE/index.md
+++ b/web/content/docs/processes/heat-transport/HEAT_TRANSPORT_BHE/index.md
@@ -37,10 +37,10 @@ Here, $\Lambda_s$ denotes the tensor of thermal hydrodynamic dispersion and $H_s
 
 In the configuration of `HEAT_TRANSPORT_BHE` process, it is generally configured as follows.
 
-* < name >: should be `HeatTransportBHE`.
-* < type >: should be `HEAT_TRANSPORT_BHE`.
-* < integration_order >: It is the order of the integration method for element-wise integration, normally set to 2.
-* < process_variables >: The primary variables of the `HEAT_TRANSPORT_BHE` process are `temperature_soil` and `temperature_BHE1`. For multiple boreholes, the name `temperature_BHE2`, `temperature_BHE3` etc can be added.
+* `<name>`: should be `HeatTransportBHE`.
+* `<type>`: should be `HEAT_TRANSPORT_BHE`.
+* `<integration_order>`: It is the order of the integration method for element-wise integration, normally set to 2.
+* `<process_variables>`: The primary variables of the `HEAT_TRANSPORT_BHE` process are `temperature_soil` and `temperature_BHE1`. For multiple boreholes, the name `temperature_BHE2`, `temperature_BHE3` etc can be added.
 
 ```xml
 <name>HeatTransportBHE</name>
diff --git a/web/content/docs/processes/heat-transport/Heat_Transport_BHE_PipelineNetwork/index.md b/web/content/docs/processes/heat-transport/Heat_Transport_BHE_PipelineNetwork/index.md
index 2547d625465fb6bb531d1f1fd66599735aa92df9..892c825e854b67c149505b8528a474f6513a5fd5 100644
--- a/web/content/docs/processes/heat-transport/Heat_Transport_BHE_PipelineNetwork/index.md
+++ b/web/content/docs/processes/heat-transport/Heat_Transport_BHE_PipelineNetwork/index.md
@@ -172,7 +172,7 @@ The work flow of the PipeNetwork feature is illustrated in Figure 2. To explicit
 
 ### BHE data container
 
-In order to use the PipeNetwork feature, the pre-built and saved TESPy network model in the above section is required. A CSV file `bhe_network.csv` which containing all the OGS-TESPy transferred BHE's information needs to be created. The PipeNetwork feature will access this CSV file to initialize the exchange data container between OGS and TESPy during the simulation. All BHEs have to be included in this CSV file. Please take notice that all BHE names located in the data_index column have to be identical with the BHE names defined in the corresponding TESPy network model.
+In order to use the PipeNetwork feature, the pre-built and saved TESPy network model in the above section is required. A CSV file `bhe_network.csv` which contains all the OGS-TESPy transferred BHE information needs to be created. The PipeNetwork feature will access this CSV file to initialize the exchange data container between OGS and TESPy during the simulation. All BHEs have to be included in this CSV file. Please take notice that all BHE names located in the `data_index` column have to be identical with the BHE names defined in the corresponding TESPy network model.
 
 ```bash
 data_index;BHE_id;Tin_val;Tout_val;Tout_node_id;flowrate
diff --git a/web/content/docs/tools/preprocessing/createQuadraticMesh/index.md b/web/content/docs/tools/preprocessing/createQuadraticMesh/index.md
index c3bd8a4cb9efeb0e40f2f8f73c857cf4b07087ac..f04e2806ef4bea9e3fb0819984336b7707d88351 100644
--- a/web/content/docs/tools/preprocessing/createQuadraticMesh/index.md
+++ b/web/content/docs/tools/preprocessing/createQuadraticMesh/index.md
@@ -5,19 +5,21 @@ author = "Julian Heinze"
 +++
 
 ## Description
+
 This tool converts a linear mesh to a mesh of quadratic order.
 The order of a mesh is equal to the highest order of elements within the mesh.
 The quadratic order mesh allows shape functions of quadratic order to be considered in the finite element methods of the simulation.
-More detailed information about the differences between a linear and quadratic mesh elements can be found in the [VTK book by kitware](https://kitware.github.io/vtk-examples/site/VTKBook/05Chapter5/).
+More detailed information about the differences between a linear and quadratic mesh elements can be found in the [VTK book by Kitware](https://kitware.github.io/vtk-examples/site/VTKBook/05Chapter5/).
 
 ## Usage
+
 ```bash
-USAGE: 
+USAGE:
    createQuadraticMesh  [-c] -o <string> -i <string> [--] [--version]
                             [-h]
 
 
-Where: 
+Where:
    -c,  --add-centre-node
      add centre node
 
@@ -37,8 +39,8 @@ Where:
      Displays usage information and exits.
 ```
 
-## Example:
+## Example
 
 ```bash
 createQuadraticMesh -i input_mesh.vtu -o quadratic_mesh.vtu
-```
\ No newline at end of file
+```
diff --git a/web/content/docs/userguide/basics/project_file_intro.md b/web/content/docs/userguide/basics/project_file_intro.md
index ab5eb26af99d0b6d88e5a919efac2a0e477626e0..e2bd36ea02c0fc1f89a42442ed8bf90960532d94 100644
--- a/web/content/docs/userguide/basics/project_file_intro.md
+++ b/web/content/docs/userguide/basics/project_file_intro.md
@@ -8,7 +8,7 @@ weight = 3
 The main input taken by OpenGeoSys is a path to a project file. This file has a ".prj" extension and describes all aspects of
 the simulation that OpenGeoSys is expected to execute.
 
-The syntax of the project file follows the syntax of a typical xml file and can be edited with any editor capable of working
+The syntax of the project file follows the syntax of a typical XML file and can be edited with any editor capable of working
 with this kind of files.
 
 The structure of the project file is relatively flexible: as long as the semantics of the file is intact, the main blocks can be
@@ -18,14 +18,14 @@ Depending on the scope of the simulation, the content of the project file will d
 
 <div class="note">
 Please note, that this page is not a complete description of the XML standard. It only provides some information to interact
-with and understand OpenGeoSys "*.prj" files. More meta-information on xml can be found here: <a href="https://www.w3.org/standards/xml/">XML Standard</a>. <!-- TODO: Consider giving a direct link to an xml-tutorial. -->
+with and understand OpenGeoSys "*.prj" files. More meta-information on XML can be found here: <a href="https://www.w3.org/standards/xml/">XML Standard</a>. <!-- TODO: Consider giving a direct link to an xml-tutorial. -->
 </div>
 
 The XML files structure follows an abstract idea of a tree: i.e., here one starts from the roots and continues up to the
 leaves. As such the main tag within an XML file is called root. In OpenGeoSys project files the root tag looks like this: `<
 OpenGeoSysProject> </OpenGeoSysProject>`. Between opening and closing tags all the project relevant information is contained.
 Everything between those tags follows a hierarchical structure. There will be thematic blocks that cover specific aspects of
-the simulation. They define for example mesh files, or a process used in the simulation. The following xml-snippet shows a
+the simulation. They define for example mesh files, or a process used in the simulation. The following XML-snippet shows a
 small structure containing the two elementary blocks, which are empty for now:
 
 ```xml
diff --git a/web/content/docs/userguide/basics/working_with_project_files.md b/web/content/docs/userguide/basics/working_with_project_files.md
index 1b1bef1b9df0adeb240f29aa7005fdde1cf88d4f..ea5c745041019c025f4897614687e3bb68ee70b2 100644
--- a/web/content/docs/userguide/basics/working_with_project_files.md
+++ b/web/content/docs/userguide/basics/working_with_project_files.md
@@ -21,7 +21,7 @@ It was published in this state to make existing content available to users and h
 ## Setting up a project file
 
 The best starting point for setting your own project with OGS is to browse a catalogue of benchmarks (either at documentation
-page or gitlab).
+page or GitLab).
 
 ## Creating a new project file
 
diff --git a/web/content/docs/userguide/blocks/linear_solvers.md b/web/content/docs/userguide/blocks/linear_solvers.md
index 9272a9a016b82a2cfb60d4e26dbe72c0b15b33cf..637de4fda695ce40d2b007511260f50dd3e92474 100644
--- a/web/content/docs/userguide/blocks/linear_solvers.md
+++ b/web/content/docs/userguide/blocks/linear_solvers.md
@@ -20,12 +20,12 @@ It was published in this state to make existing content available to users and h
 </div>
 
 An important parameter defined for each iterative linear solver is the "error tolerance" (direct solvers don't use the tolerance settings).
-Combined with "abstols" from section [Time loop](/docs/userguide/blocks/time_loop/) it defines the acceptable level of error in the obtained result.
+Combined with `abstols` from section [Time loop](/docs/userguide/blocks/time_loop/) it defines the acceptable level of error in the obtained result.
 Those two parameters are interconnected with each other. Setting either of them too tightly will result in an error message referring to problems, implying that a smaller time step needs to be set up. If the settings are too loose, results may be erroneous.
 As the variables are interconnected, it is possible to avoid error when one of the tolerances is set too low, by setting the other one a bit too high.
 
-Generally, the error tolerance of a linear solver should always be tighter than "abstols".
-Unlike "abstol", "error tolerance" is not specific to "process variables" and is defined as one value.
+Generally, the error tolerance of a linear solver should always be tighter than `abstols`.
+Unlike `abstol`, "error tolerance" is not specific to "process variables" and is defined as one value.
 For most cases value below $10^{-10}$ is recommended.
 
 <!-- TODO: The text above is not completely clear. It needs re-wording and additional clarifications. -->
diff --git a/web/content/docs/userguide/blocks/processes.md b/web/content/docs/userguide/blocks/processes.md
index 10928872ed54de5cede5841b32ff8aa318804fe1..1023697987e4ad3c049091a172208df884fe1b10 100644
--- a/web/content/docs/userguide/blocks/processes.md
+++ b/web/content/docs/userguide/blocks/processes.md
@@ -90,7 +90,7 @@ For the process variables listed above, relative error tolerances can be defined
 The order can differ based on the order in which the processes are defined and on dimensionality of the process (e.g., number
 of components in displacement, or number of chemical constituents).
 Keep in mind that some process variables have more than one value like displacement in the example above.
-In such a case, a matching number of reltols has to be defined. <!-- TODO: Explain the matching number. -->
+In such a case, a matching number of `reltols` has to be defined. <!-- TODO: Explain the matching number. -->
 
 <!-- TODO: Explain the relative tolerance. -->
 
@@ -100,13 +100,13 @@ Constitutive relation can be one of the [existing relations](/docs/userguide/blo
 in OpenGeoSys or it can be defined by user using [MFront](/docs/userguide/features/mfront/).
 They are used with one of the following mechanical processes:
 
-* Hydro Mechanics
-* Phase Field
-* Richards Mechanics
+* Hydro-Mechanics
+* Phase-Field
+* Richards-Mechanics
 * Small Deformation
-* Thermo Mechanics
-* Thermo Hydro Mechanics
-* Thermo Richards Mechanics
+* Thermo-Mechanics
+* Thermo-Hydro-Mechanics
+* Thermo-Richards-Mechanics
 * TH2M
 
 To define constitutive relation, tags `<constitutive_relation> </constitutive_relation>` are used.
diff --git a/web/content/docs/userguide/features/python_bc.md b/web/content/docs/userguide/features/python_bc.md
index 44335f73dec82fb736b55c9ab381bfbd0568e417..f7a101996f7773c4a65f1dd7dde90889d103b81c 100644
--- a/web/content/docs/userguide/features/python_bc.md
+++ b/web/content/docs/userguide/features/python_bc.md
@@ -73,10 +73,10 @@ OpenGeoSys will obtain values for a Dirichlet boundary condition by calling the
 The following variables are always passed as an input to the Dirichlet boundary condition method (in brackets the default
 variable name used in examples) is given:
 
-- time (t),
-- spatial coordinates (coords),
-- node id (node_id),
-- primary variables (primary_vars).
+- time (`t`),
+- spatial coordinates (`coords`),
+- node id (`node_id`),
+- primary variables (`primary_vars`).
 
 #### Output
 
@@ -97,9 +97,9 @@ OpenGeoSys will obtain values for a Neumann boundary condition by calling the me
 
 The following variables are always passed as an input to the Dirichlet boundary condition method (in brackets the default variable name used in examples is given):
 
-- time (t),
-- spatial coordinates (coords),
-- primary variables (primary_vars).
+- time (`t`),
+- spatial coordinates (`coords`),
+- primary variables (`primary_vars`).
 
 The order in which those variables are provided is important.
 
diff --git a/web/content/docs/userguide/troubleshooting/general/index.md b/web/content/docs/userguide/troubleshooting/general/index.md
index 58ff5fe1a8f354695fb41238a7209266bd2a37d7..3bb491d71bfc0d4b6fd35b3eb2b73a1bc33dcd35 100644
--- a/web/content/docs/userguide/troubleshooting/general/index.md
+++ b/web/content/docs/userguide/troubleshooting/general/index.md
@@ -10,7 +10,7 @@ toc = true
 
 ## Data Explorer
 
-### XSDError: Loaded schema file is invalid
+### `XSDError`: Loaded schema file is invalid
 
 You may encountering the following error (or similar) on opening `.gml`, `.cnd`, `std` or `.prj` files in the Data Explorer or
 file conversion tools (e.g. `OGSFileConverter`):