diff --git a/docs/.utils/transifex_utils.py b/docs/.utils/transifex_utils.py
index 9b356ab88..5a1b3fb44 100644
--- a/docs/.utils/transifex_utils.py
+++ b/docs/.utils/transifex_utils.py
@@ -28,7 +28,7 @@ def create_transifex_config():
             # Get relative path of file
             relative_path = os.path.relpath(file, start=root)
 
-            tx_slug = slugify(relative_path)
+            tx_slug = slugify(os.path.splitext(relative_path)[0])
 
             if tx_slug:
                 print(f"Found file with tx_slug defined: {relative_path}, {tx_slug}")
diff --git a/docs/background_info/extended_models_optimization.md b/docs/background_info/extended_models_optimization.md
index 96f01c21c..11f9eee33 100644
--- a/docs/background_info/extended_models_optimization.md
+++ b/docs/background_info/extended_models_optimization.md
@@ -1,6 +1,6 @@
 If a model or topic contains extended classes, the inclusive base classes are implemented in the physical database. The users only want to see, what is relevant for them and mostly work on the most extended instance of the topics/classes. Model Baker detects the ***irrelevant*** tables and offers optimization strategies to the users on ***smart1intehritance*** implementations.
 
-In the [workflow wizard](../../user_guide/import_workflow/#optimize-qgis-project-if-extended) you can choose the optimization [strategy]([corresponding chapter](../../background_info/extended_models_optimization/#strategies) and receive a nicely prepared layertree and forms.
+In the [workflow wizard](../../user_guide/import_workflow/#optimize-qgis-project-if-extended) you can choose the optimization [strategy](../../background_info/extended_models_optimization/#strategies) and receive a nicely prepared layertree and forms.
 
 But what is done in the backend?