diff --git a/docs/admin/developer/agama/recommended-practices.md b/docs/admin/developer/agama/agama-best-practices.md
similarity index 100%
rename from docs/admin/developer/agama/recommended-practices.md
rename to docs/admin/developer/agama/agama-best-practices.md
diff --git a/docs/admin/developer/agama/faq.md b/docs/admin/developer/agama/faq.md
index 412b763cd67..f379dd5f636 100644
--- a/docs/admin/developer/agama/faq.md
+++ b/docs/admin/developer/agama/faq.md
@@ -180,4 +180,4 @@ You can assign this value to a variable at the top of your loop declaration. See
 
 ### Can Agama code be called from Java?
 
-No. These two languages are supposed to play roles that should not be mixed, check [here](./recommended-practices.md#about-flow-design).
+No. These two languages are supposed to play roles that should not be mixed, check [here](./agama-best-practices#about-flow-design).
diff --git a/docs/admin/developer/agama/jans-agama-engine.md b/docs/admin/developer/agama/jans-agama-engine.md
index be307f9ce31..650ecbcfb97 100644
--- a/docs/admin/developer/agama/jans-agama-engine.md
+++ b/docs/admin/developer/agama/jans-agama-engine.md
@@ -260,7 +260,7 @@ As seen in the examples Agama engine can deal with Java exceptions, however, thi
 
 [Agama types](../../../agama/language-reference.md#data-types) do not match Java types. This means passing a "native" Agama value as parameter in a method `Call` requires some form of compatibility with the target (Java) type in the method signature.
 
-An argument (Agama value) is compatible with a method parameter if it can be "converted" successfully. As we'll see, conversion feels pretty natural in practice. If this process fails a `java.lang.IllegalArgumentException` is thrown and the flow will crash unless the exception is caught. Note however the recommended practice is to let flows [crash](./recommended-practices.md#about-crashes).
+An argument (Agama value) is compatible with a method parameter if it can be "converted" successfully. As we'll see, conversion feels pretty natural in practice. If this process fails a `java.lang.IllegalArgumentException` is thrown and the flow will crash unless the exception is caught. Note however the recommended practice is to let flows [crash](./agama-best-practices#about-crashes).
 
 The following lists some of the most common successful conversions:
 
@@ -353,4 +353,4 @@ We consider the following to be remarkable:
 
 ### OOP prose warning
 
-See the recommended [practices](./recommended-practices.md#oop-prose-warning) to learn more about this topic.
+See the recommended [practices](./agama-best-practices#oop-prose-warning) to learn more about this topic.
diff --git a/mkdocs.yml b/mkdocs.yml
index 5eb87e7b9c5..760705a90bc 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -283,7 +283,7 @@ nav:
       - Agama engine: admin/developer/agama/jans-agama-engine.md
       - Navigation, UI pages and assets: admin/developer/agama/flows-navigation-ui.md
       - Projects deployment: admin/developer/agama/projects-deployment.md
-      - Recommended practices:  admin/developer/agama/recommended-practices.md
+      - Agama Best Practices:  admin/developer/agama/agama-best-practices.md
       - Advanced usages: admin/developer/agama/advanced-usages.md
       - Engine and bridge configurations: admin/developer/agama/engine-bridge-config.md
       - FAQ: admin/developer/agama/faq.md