Review docs under Nanoflows and other additions

Author: Yiyun333

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/error-handling-in-microflows.md

@@ -9,7 +9,7 @@ aliases:
 
 ## Introduction
 
-In a [microflow](/refguide/microflows/), microflow elements ([activities](/refguide/activities/), [decisions](/refguide/decisions/), or [loops](/refguide/loop/)) can sometimes fail and produce an error. If you do nothing, Mendix will report the error with a system error message and roll back all the changes. However, you can also change this behavior and handle errors yourself.
+In a [microflow](/refguide/microflows/), microflow elements ([activities](/refguide/activities/), [decisions](/refguide/decisions/), or [loops](/refguide/loop/)) can sometimes fail and produce an error. If you do nothing, Mendix reports the error with a system error message and roll back all the changes. However, you can also change this behavior and handle errors yourself.
 
 This document introduces different error handling options in microflows and explains how they work using simple examples. An example of how combined custom error handling works is also given in [An Example of Combined Error Handling](#example).
 

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

@@ -56,7 +56,7 @@ URLs are not supported for microflows that have non-persistable entities or list
 
 #### Name
 
-**Name** is the internal name of the microflow. When referring to the microflow in the app you will use this name. It must be unique within the module, but you can have two microflows with the same name in different modules. When referring to the microflow, you will normally prepend the name of the module to ensure uniqueness and allow you to use microflows in other modules.
+**Name** is the internal name of the microflow. You use this name to refer to the microflow in the app. It must be unique within the module, but you can have two microflows with the same name in different modules. When referring to the microflow, you normally prepend the name of the module to ensure uniqueness and allow you to use microflows in other modules.
 
 #### Export Level 
 

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

@@ -21,13 +21,13 @@ Nanoflow properties consist of the following sections:
 
 #### Return Type
 
-The return type defines what information the nanoflow returns. The caller of the nanoflow will get a result of this type. For possible return types, see [Data Types](/refguide/data-types/).
+The return type defines what information the nanoflow returns. The caller of the nanoflow gets a result of this type. For information on possible return types, see [Data Types](/refguide/data-types/).
 
 ### Common Section {#common}
 
 #### Name
 
-**Name** is the internal name of the nanoflow. When referring to the nanoflow in the app you will use this name. It must be unique within the module, but you can have two nanoflows with the same name in different modules. When referring to the nanoflow, you will normally prepend the name of the module to ensure uniqueness and allow you to use nanoflows in other modules.
+**Name** is the internal name of the nanoflow. You use this name to refer to the nanoflow in the app. It must be unique within the module, but you can have two nanoflows with the same name in different modules. When referring to the nanoflow, you normally prepend the name of the module to ensure uniqueness and allow you to use nanoflows in other modules.
 
 #### Documentation