Update from review comments

Author: knolleary

docs/developing-flows/documenting-flows.md

@@ -75,7 +75,7 @@ This is where adding port labels can help document the intended logic.
 
 For example, the Switch node provides default labels for its outputs that are shown when the mouse hovers over them. They can help quickly identify the purpose of each branch in the flow.
 
-Whilst the default labels may be sufficient in the context of the flow itself, it is also possible to custom labels to provide more detailed information.
+Whilst the default labels may be sufficient in the context of the flow itself, it is also possible to customise labels to provide more detailed information.
 
 <div style="width: 600px" class="figure">
   <img src="images/placeholder.png" alt="Link nodes">

docs/developing-flows/flow-structure.md

@@ -104,9 +104,9 @@ Node-RED provides the Catch and Status nodes as ways of building flows that can
 
 As there is no direct visual association between a Catch node and the nodes it targets, you should consider how to position them in order to keep the flows readable.
 
-Placing them close to the parts of the flow they correspond to can help, but you should take care not cause your flows to be come overcrowded.
+Placing them close to the parts of the flow they correspond to can help, but you should take care not cause your flows to become overcrowded.
 
-Although approach is to group all of the error handling flows below the main flow - making the 'good' path clearly distinct from the error paths.
+Another approach is to group all of the error handling flows below the main flow - making the 'good' path clearly distinct from the error paths.
 
 Giving your Catch nodes a clear name is also very important to help easily identify the scenarios they are intended to handle.