additional review comments resolved

Author: sahehb

mevislab.github.io/content/tutorials/image_processing/cpp_1.md

@@ -22,7 +22,7 @@ Make sure to have [cmake](https://cmake.org/download) installed. This example ha
 In this example, we develop our own C++ ML module, which adds a constant value to each voxel of the given input image.
 
 ## Steps to Do
-### Create a new ML Module
+### Create a New ML Module
 Before creating the module, make sure to have your own user package available. See [Package creation](tutorials/basicmechanisms/macromodules/package/) for details about Packages.
 
 Use the *Project Wizard* via the menu entry {{< menuitem "File" "Run Project Wizard ..." >}} to create a new ML module. Select *ML Module* and click *Run Wizard*.
@@ -60,7 +60,7 @@ The Project Wizard creates a *CMakeLists.txt* file that describes the typical pr
 
 Just make sure that the MLAB_ROOT environment variable is set on your system and points to the packages directory of your MeVisLab installation, because this is used to resolve the reference to the 'MeVisLab' project.
 
-Open a commandline and change to your current module directory (the directory containing your *CMakeLists.txt* file). Enter **cmake . -G "Visual Studio 17"**. After execution, a lot of files are generated by CMake. 
+Open a command line and change to your current module directory (the directory containing your *CMakeLists.txt* file). Enter **cmake . -G "Visual Studio 17"**. After execution, a lot of files are generated by CMake. 
 
 For further documentation about our use of CMake, see: [CMake for MeVisLab - Documentation](https://mevislabdownloads.mevis.de/docs/current/MeVisLab/Resources/Documentation/Publish/SDK/CMakeManual/#mainBook).
 
@@ -124,7 +124,7 @@ Next, we are going to finally change the voxel values of the image. Open the fil
 ```
 {{</highlight>}}
 
-Then, change the inner line of the loop, so that the constant value is added to the value of the input voxel:
+Then, change the inner line of the loop so that the constant value is added to the value of the input voxel:
 
 {{< highlight filename="mlSimpleAddOutputImageHandler.cpp" >}}
 ```c++
@@ -141,9 +141,9 @@ Compile the project in the development environment. Make sure to select a *Relea
 ### Use Your Module in MeVisLab
 Your compiled **.dll* is available in your project directory under *Sources/lib*. In order to use it in MeVisLab, it needs to be copied to the *lib* folder of your user package.
 
-You can either do this manually or via PostBuild step.
+This only works in a post-build step.
 
-In the case MeVisLab was running during development, restart MeVisLab and use your new module.
+If the environment variable *MLAB_AUTOMATIC_POSTBUILD_COPY* is set, the newly compiled DLLs and .lib files are copied to the correct location when MeVisLab restarts. Otherwise, they must be copied manually.
 
 For testing purposes, you can use a `LocalImage` module and two `View2D` modules. Connect the `SimpleAdd` module to the second `View2D` and change the <field>Constant Value</field> field.
 

mevislab.github.io/content/tutorials/image_processing/cpp_development.md

@@ -18,7 +18,7 @@ menu:
 The development of your own C++ modules can be done by ML modules and by Open Inventor modules.
 
 {{<alert class="info" caption="Important Information">}}
-Make sure to use a compiler that is compatible to your currently installed MeVisLab version.
+Make sure to use a compiler that is compatible with your currently installed MeVisLab version.
 {{</alert>}}
 
 ### ML Modules on the C++ Level
@@ -27,9 +27,9 @@ Make sure to use a compiler that is compatible to your currently installed MeVis
 * Inputs and outputs for abstract data structures are connectors to pointers of objects derived from class Base and are called Base objects.
 
 ### Open Inventor Modules on the C++ Level
-* Most Open Inventor modules are objects derived from class SoNode defined in the Open Inventor library.
-* Open Inventor inputs and outputs are connectors to objects derived from class SoNode defined in the Open Inventor library. Many Open Inventor modules will return themselves as outputs (“self”). On inputs, they may have connectors to child Open Inventor modules.
-* Some Open Inventor modules are objects derived from class SoEngine. They are used for calculations and return their output not via output connectors but via fields.
+* Most Open Inventor modules are objects derived from class SoNode, defined in the Open Inventor library.
+* Open Inventor inputs and outputs are connectors to objects derived from class SoNode, defined in the Open Inventor library. Many Open Inventor modules will return themselves as outputs (“self”). On inputs, they may have connectors to child Open Inventor modules.
+* Some Open Inventor modules are objects derived from class SoEngine. They are used for calculations and return their output not via output connectors but via parameter fields.
 * Open Inventor modules may also have input and output connectors to Base objects and Image objects.
 * All standard Open Inventor nodes defined in the Open Inventor library are available in MeVisLab as Open Inventor modules.