Rename content files to their desired name

content/community/contribute/community-contribute-to-precice.md → content/community/contribute/contribute-to-precice.md

@@ -222,7 +222,7 @@ The content of the tutorials is sourced from the develop branch of the tutorials
 1. Trigger the [update submodules workflow](https://github.com/precice/precice.github.io/actions/workflows/update-submodules.yml) and, after it completes, create a new branch and pull request (this may also happen automatically, or someone from the preCICE team may have to do it for you).
 2. Edit the [`_config.yml` file](https://github.com/precice/precice.github.io/blob/master/_config.yml) to append the directory name of your tutorial under `subprojects:`.
 3. Edit the [tutorials sidebar](https://github.com/precice/precice.github.io/blob/master/_data/sidebars/tutorial_sidebar.yml) to add your tutorial permalink (defined in the heading of the `README.md` you created) to a fitting place, next to a similar tutorial.
-4. Edit the [tutorials landing page](https://github.com/precice/precice.github.io/blob/master/content/tutorials/tutorials.md) to add your tutorial to the overview.
+4. Edit the [tutorials landing page](https://github.com/precice/precice.github.io/blob/master/content/tutorials/overview.md) to add your tutorial to the overview.
 
 After your PR gets reviewed, approved, and merged, the website will be built automatically, and your tutorial will appear online in a couple of minutes.
 

content/docs/couple-your-code/advanced/couple-your-code-moving-or-changing-meshes.md → content/docs/couple-your-code/advanced/moving-or-changing-meshes.md

@@ -15,7 +15,7 @@ Examples of this method are the [perpendicular flap tutorials](tutorials-perpend
 
 ## Just-in-time data mapping
 
-Instead of defining a static mesh during initialization, coordinates can be provided at runtime to read and write data at the provided coordinates using so-called [just-in-time data mappings](couple-your-code-just-in-time-mapping.md). This feature has particularly been developed for mesh-particle coupling, where one participant has a static mesh and the other participant has time-dependent coupling locations. However, it might be useful in other scenarios as well.
+Instead of defining a static mesh during initialization, coordinates can be provided at runtime to read and write data at the provided coordinates using so-called [just-in-time data mappings](couple-your-code-just-in-time-mapping.html). This feature has particularly been developed for mesh-particle coupling, where one participant has a static mesh and the other participant has time-dependent coupling locations. However, it might be useful in other scenarios as well.
 
 ## Mapping inside adapter
 

content/docs/installation/bindings/installation-bindings-julia.md → content/docs/installation/bindings/julia.md

@@ -7,7 +7,7 @@ summary: "Use add PreCICE to install the Julia language bindings from the offici
 
 ## The versioning scheme
 
-The versioning scheme of the Julia bindings is the major and minor preCICE version which the bindings are tested with, followed by the version of the Julia bindings. This differs from the [matlab](installation-bindings-python.md) and [python](installation-bindings-python.md) bindings due to the [Julia versioning guidelines](https://pkgdocs.julialang.org/v1/toml-files/#The-version-field), which only allow major, minor, and patch versions.
+The versioning scheme of the Julia bindings is the major and minor preCICE version which the bindings are tested with, followed by the version of the Julia bindings. This differs from the [matlab](installation-bindings-matlab.html) and [python](installation-bindings-python.html) bindings due to the [Julia versioning guidelines](https://pkgdocs.julialang.org/v1/toml-files/#The-version-field), which only allow major, minor, and patch versions.
 
 Example: version `1` of the Julia bindings for preCICE version `2.4.0` is `2.4.1`