Fix URLs and titles

Author: ConnorLand

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/_index.md

@@ -14,7 +14,7 @@ Microflows run in the runtime server and can therefore not be used in offline ap
 
 This page is a summary of the elements which make up a microflow, together with their visual representation within the microflow. It also covers [keyboard support](#keyboard) when editing microflows.
 
-For the properties of the microflow itself, see [Microflow Properties](/refguide/microflow/). For microflow best practices, see [Microflow Naming Conventions](/refguide/naming-conventions/#microflow-naming-conventions), [Microflow General Best Practices](/refguide/general-best-practices/#microflow-dev-best-practices), and [Microflow Best Practices from the Community](/refguide/community-best-practices-for-app-performance/#microflow-community-best-practices).
+For the properties of the microflow itself, see [Microflow Properties](/refguide/microflow/). For microflow best practices, see the[Microflows](/refguide/naming-convention-best-practices/#microflow-naming-conventions/) section of *Naming Convention Best Practices*, [Microflow General Best Practices](/refguide/general-best-practices/#microflow-dev-best-practices), and [Microflow Best Practices from the Community](/refguide/community-best-practices-for-app-performance/#microflow-community-best-practices).
 
 For information on using microflows as data sources, see [Microflow Source](/refguide/microflow-source/).
 

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/extract-and-use-sub-microflows.md

@@ -45,7 +45,7 @@ To extract the validation steps into a sub-microflow, follow these steps:
 
 3. In the **Add microflow** dialog box, enter a name for the sub-microflow.
 
-    {{% alert color="info" %}}As a best practice, use a consistent naming scheme that clearly identifies the sub-microflow, for example, *SUB_{Microflow description}*. For more naming best practices, see [Microflow Naming Conventions](/refguide/naming-conventions/#microflow-naming-conventions).{{% /alert %}}
+    {{% alert color="info" %}}As a best practice, use a consistent naming scheme that clearly identifies the sub-microflow, for example, *SUB_{Microflow description}*. For more naming best practices, see the [Microflow](/refguide/naming-convention-best-practices/#microflow-naming-conventions/) section of *Naming Convention Best Practices*.{{% /alert %}}
 
 4. Click **OK**.
 5. Open the sub-microflow by right-clicking the sub-microflow call and selecting **Go to microflow**.

content/en/docs/refguide/modeling/best-practices/dev-best-practices/_index.md

@@ -15,7 +15,7 @@ aliases:
 
 Documents in this category help you adopt consistent naming and modeling conventions while developing your Mendix applications. Working within these practices improves your apps' maintainability and performance, and speeds up collaboration time among development groups.
 
-Even with the powerful navigation and search support in Mendix Studio Pro, adhering to naming and modeling conventions is a wise due to the following reasons:
+Even with the powerful navigation and search support in Mendix Studio Pro, adhering to naming and modeling conventions is wise due to the following reasons:
 
 * After finishing an application, it is usually handed over to different people for maintenance, so even years later, they will need to understand what you did and how to improve on it
 * Anybody should be able to quickly understand an existing app in terms of what is located where and how the different parts are related