MLAB-6146: checked and fixed grammar (#128)

* MLAB-6146: checked and fixed grammar

* MLAB-6146: fixes after review

Author: okonrad

mevislab.github.io/content/examples/basic_mechanisms/macro_modules_and_module_interaction/example2/index.md

@@ -10,7 +10,7 @@ This example shows how to create module interactions via Python scripting.
 ## Summary
 A new macro module `IsoCSOs` is created providing two viewers in its internal network, `View2D` and `SoExaminerViewer`. Both viewers are included in the panel of the module.
 
-To showcase how Python functions can be implemented in MeVisLab and called from within a module, additional buttons to browse directories, and create contours via the `CSOIsoGenerator` are added. Lastly, a field listener is implemented reacting to field changes by colorizing contours when the user hovers over them with the mouse. 
+To showcase how Python functions can be implemented in MeVisLab and called from within a module, additional buttons to browse directories and create contours via the `CSOIsoGenerator` are added. Lastly, a field listener is implemented reacting to field changes by colorizing contours when the user hovers over them with the mouse. 
 
 ![Screenshot](/examples/basic_mechanisms/macro_modules_and_module_interaction/example2/image2.png)
 

mevislab.github.io/content/examples/data_objects/surface_objects/example2/index.md

@@ -4,7 +4,7 @@ title: "Processing and modification of WEMs"
 category: "data_objects"
 ---
 
-# Surface Example 2: Processing and Modifying of WEMs
+# Surface Example 2: Processing and Modification of WEMs
 This example shows how to process and modify WEMs using the modules `WEMModify`, `WEMSmooth`, and `WEMSurfaceDistance`.
 ![Screenshot](/examples/data_objects/surface_objects/example2/DO7_03.png)
 

mevislab.github.io/content/introduction/introduction.md

@@ -192,7 +192,7 @@ An exemplary use case for a parameter connection is synchronization. Have a look
 The creation of macros is explained in more detail in [Tutorial Chapter I - Example 2.2](/tutorials/basicmechanisms/macromodules/globalmacromodules) 
 {{</alert>}}
 
-### Adding Modules to Your Workspace {#Searching_and_Adding_Modules}
+### Adding Modules to your Workspace {#Searching_and_Adding_Modules}
 
 There are several ways to add a module to your current network:
 -   via the menu bar entry {{< menuitem "Modules" >}}

mevislab.github.io/content/tutorials/basicmechanisms/coordinatesystems/coordinatesystems.md

@@ -42,7 +42,7 @@ The `ConstantImage` module generates an artificial image with a certain size, da
 
 ![ConstantImage Info](/images/tutorials/basicmechanics/ConstantImageInfo.png "ConstantImage Info")
 
-Placing an object into the Open Inventor scene of the `SoExaminerViewer`, in this case a `SoCube` with *width*, *height*, and *depth* of 10, places the object to the origin of the world coordinate system.
+Placing an object into the Open Inventor Scene of the `SoExaminerViewer`, in this case a `SoCube` with *width*, *height*, and *depth* of 10, places the object to the origin of the world coordinate system.
 
 ![SoCube in world coordinate system](/images/tutorials/basicmechanics/SoCubeWorldCoordinates.png "SoCube in world coordinate system")
 

mevislab.github.io/content/tutorials/basicmechanisms/coordinatesystems/coordinatesystems2.md

@@ -24,7 +24,7 @@ World coordinates also refer to the patient axes. They are:
 
 ![World Coordinates in Context of the Human Body](/images/tutorials/visualization/V2_00.png "World Coordinates in Context of the Human Body")
 
-The Digital Imaging and Communications in Medicine (DICOM) standard defines a data format that groups information into data sets. This way, the image data is always kept together with all meta information like patient ID, study time, series time, acquisition data, etc. The image slice is represented by another tag with pixel information.
+The DICOM (Digital Imaging and Communications in Medicine) standard defines a data format that groups information into data sets. This way, the image data is always kept together with all meta information like patient ID, study time, series time, acquisition data, etc. The image slice is represented by another tag with pixel information.
 
 DICOM tags have unique numbers, encoded as two 16-bit numbers, usually shown in hexadecimal notation as two four-digit numbers (xxxx,xxxx). These numbers are the data group number and the data element number.
 

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/guidesign.md

@@ -42,7 +42,7 @@ To add and edit a panel, open the context menu and select {{< menuitem "Related
 
 ### Module Interface
 By default, the *.script* file contains the {{< docuLinks "/Resources/Documentation/Publish/SDK/MDLReference/index.html#mdl_Interface" "interface" >}} of the module.
-In the interface section (everything inside the curled brackets behind the name *Interface*) you can define the module inputs, the module outputs, and also all module fields (or *Parameters*).
+In the interface section (everything insight the curled brackets behind the name *Interface*) you can define the module inputs, the module outputs, and also all module fields (or *Parameters*).
 
 [//]: <> (MVL-653)
 {{< highlight filename="Filter.script" >}}
@@ -288,7 +288,7 @@ Commands {
 {{</highlight>}}
 
 {{<alert class="info" caption="Infos">}}
-The section *Source* should already be available and generated automatically in the case you enable the Wizard to add a Python file to your module.
+The section *Source* should already be available and generated automatically in case you enable the Wizard to add a Python file to your module.
 {{</alert>}}
 
 [//]: <> (MVL-653)

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/helpfiles.md

@@ -69,7 +69,7 @@ Depending on the way the macro module was created, more or less features are aut
 {{</alert>}}
 
 ### Creation of an Example Network
-To add an example network to your module, you need to add a reference to the respective *.mlab* file to the module definition file (.def). Open the file *Filter.def*. You can find the line *exampleNetwork     = "$(LOCAL)/networks/FilterExample.mlab"*, which defines the reference to the *.mlab* file containing the example network. By default, the name of the example network is *ModulenameExample.mlab*. An *.mlab* file containing only the module *Filter* is created inside the folder *networks*.
+To add an example network to your module, you need to add a reference to the respective *.mlab* file to the module definition file (*.def*). Open the file *Filter.def*. You can find the line *exampleNetwork     = "$(LOCAL)/networks/FilterExample.mlab"*, which defines the reference to the *.mlab* file containing the example network. By default, the name of the example network is *ModulenameExample.mlab*. An *.mlab* file containing only the module *Filter* is created inside the folder *networks*.
 
 It is possible that the reference to the example network or the file *FilterExample.mlab* is missing. One reason could be that its creation was not selected when creating the macro module. In this case, add the reference and the file manually.
 
@@ -81,8 +81,8 @@ To create the example network, open the file *FilterExample.mlab* in MeVisLab an
 
 
 ## Summary
-* {{< docuLinks "/Resources/Documentation/Publish/SDK/MeVisLabManual/ch26.html" "MeVisLab MATE">}} is a built-in text editor that can be used to create module help files and module panels, or to create module interactions via Python scripting.
-* You can create help files via the module context menu using MeVisLab's MATE.
-* You can add an example network to your macro module via the *.def* file.
+* {{< docuLinks "/Resources/Documentation/Publish/SDK/MeVisLabManual/ch26.html" "MeVisLab MATE">}} is a built-in text editor which can be used to create module help files, module panels or to create module interactionss via Python scripting.
+* You can create help files via the module context menu using MeVisLab Mate.
+* You can add an example network to your macro module via the .def file.
 
 [//]: <> (MVL-653)

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/pythonscripting.md

@@ -83,10 +83,10 @@ The module `RunPythonScript` allows to execute Python scripts from within a MeVi
 
 #### Module Interactions via Python Scripting
 
-You can reference to a Python function inside a *.script* file of a macro module. With this, you can, for example, execute a Python function whenever you open a panel, or define the action that is executed when pressing a button or specify the command triggered by a [field listener](tutorials/basicmechanisms/macromodules/scriptingexample2). An example for module interactions via Python scripting is given in the same example.
+You can reference to a Python function inside a *.script* file of a macro module. With this, you can, for example, execute a Python function, whenever you open a panel, define the action that is executed when pressing a button or specify the command triggered by a [field listener](tutorials/basicmechanisms/macromodules/scriptingexample2). An example for module interactions via Python scripting is given in the same example.
 
 #### Python Scripting in Network Files (*.mlab*)
-If you do not want to create a macro module, you can also execute Python scripts in a network file (*.mlab*). Save your network using a defined name, for example, *mytest.mlab*. Then create a *.script* and a *.py* file in the same directory, using the same names (*mytest.script* and *mytest.py*).
+If you do not want to create a macro module, you can also execute Python scripts in a network file (*.mlab*). Save your network using a defined name, for example, *mytest.mlab*. Then, create a *.script* and a *.py* file in the same directory, using the same names (*mytest.script* and *mytest.py*).
 
 Open the *.script* file and add a *Commands* section defining the name of the Python file.
 

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/scriptingexample2.md

@@ -42,7 +42,7 @@ Now, create your macro module and reload MeVisLab. You can find your module via
 
 ![Enable Python scripting](/images/tutorials/basicmechanics/EnablePythonScripting.png "Enable Python scripting")
 
-To design a panel and create a user interface for the macro module, open the *.script* file. You can see that a *Commands* environment exist, which defines the Python file as source for all commands.
+To design a panel and create a user interface for the macro module, open the *.script* file. You can see that a *Commands* section exists, which defines the Python file as source for all commands.
 
 ![Open the script file](/images/tutorials/basicmechanics/OpenScriptFile.png "Open the script file")
 
@@ -139,7 +139,7 @@ Window {
 
 ![Add name field](/images/tutorials/basicmechanics/AddNameField.png "Add name field")
 
-### Add Buttons to Your Panel
+### Add Buttons to your Panel
 
 As a next step, we like to add a *Browse\...* button, like in the module
 `LocalImage`, and also a button to create the CSOs.
@@ -237,7 +237,7 @@ can do this in the following way:
 
     ![Scripting Assistant](/images/tutorials/basicmechanics/GUI_Exp_15.png "Scripting Assistant")
 
-2. Enable a functionality that allows us to notice the ID of the CSO we are currently hovering over with our mouse. For this, open the internal network of our macro module. We will use the module `SoView2DCSOExtensibleEditor`. Open its panel and select the tab *Advanced*. You can check a box to enable *Update CSO id under mouse*. If you now hover over a CSO, you can see its ID in the panel. We can save the internal network to save this functionality, but we can also solve our problem via scripting. The Scripting Assistant translated our action into code that we can use.
+2. Enable a functionality that allows us to notice the id of the CSO we are currently hovering over with our mouse. For this, open the internal network of our macro module. We will use the module `SoView2DCSOExtensibleEditor`. Open its panel and select the tab *Advanced*. You can check a box to enable *Update CSO id under mouse*. If you now hover over a CSO, you can see its ID in the panel. We can save the internal network to save this functionality, but we can also solve our problem via scripting. The Scripting Assistant translated our action into code that we can use.
 
     ![Enabling CSO id identification](/images/tutorials/basicmechanics/GUI_Exp_16.png "Enabling CSO id identification")
 

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/soviewportregion.md

@@ -29,7 +29,7 @@ Add an `ImageLoad` module to your workspace and select a 3D image like *./MeVisL
 
 ![Image Display Setup](/images/tutorials/basicmechanics/E6_1.png "Image Display Setup")
 
-Opening the three `View2D` module panels now shows the image data in three orthogonal views. The module `OrthoReformat3` transforms the input image (by rotating and/or flipping) into the three main views commonly used.
+Opening the three `View2D` module panels now shows the data in three orthogonal views. The module `OrthoReformat3` transforms the input image (by rotating and/or flipping) into the three main views commonly used.
 
 ![3 Views in 3 Viewers](/images/tutorials/basicmechanics/E6_2.png "3 Views in 3 Viewers")