additional review comments corrected

Author: Heckmann

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

@@ -65,7 +65,7 @@ Interface {
 {{</highlight>}}
 
 ##### Module Inputs and Outputs
-To create an input/output, you need to define a *Field* in the respective input/output section. Each input/output gets a name (here <field>input0</field>/<field>output0</field>) that you can use to reference this field. The module input maps to an input of the internal network. You need to define this mapping. In this case, the input of the macro module `Filter` maps to the input of the module `Convolution` of the internal network (<field>internalName</field> = <field>Convolution.input0</field>). Similarly, you need to define which output of the internal network maps to the output of the macro module `Filter`. In this example, the output of the internal module `Arithmethic2` maps to the output of our macro module `Filter` (<field>internalName</field> = <field>Arithmetic2.output0</field>).
+To create an input/output, you need to define a *Field* in the respective input/output section. Each input/output gets a name (here <field>input0</field>/<field>output0</field>) that you can use to reference this field. The module input maps to an input of the internal network. You need to define this mapping. In this case, the input of the macro module `Filter` maps to the input of the module `Convolution` of the internal network (<inlineCode>internalName = Convolution.input0</inlineCode>). Similarly, you need to define which output of the internal network maps to the output of the macro module `Filter`. In this example, the output of the internal module `Arithmethic2` maps to the output of our macro module `Filter` (<inlineCode>internalName = Arithmetic2.output0</inlineCode>).
 
 Creating an input/output causes:
 1. Input/output connectors are added to the module.
@@ -76,7 +76,7 @@ Creating an input/output causes:
 ![Internal Network of your macro module](images/tutorials/basicmechanics/BM_23.png "Internal Network of your macro module")
 
 ##### Module Fields
-In the *Parameters* section, you can define *fields* of your macro module. These fields may map to existing fields of the internal network (<field>internalName</field> = ...), but they do not need to and can also be completely new. You can reference these fields when creating a panel, to allow interactions with these fields. All fields appear in the *Automatic Panel*.
+In the *Parameters* section, you can define *fields* of your macro module. These fields may map to existing fields of the internal network (<attribute>internalName</attribute> = ...), but they do not need to and can also be completely new. You can reference these fields when creating a panel, to allow interactions with these fields. All fields appear in the *Automatic Panel*.
 
 ### Module Panel Layout
 To create your own user interface, we need to create a {{< docuLinks "/Resources/Documentation/Publish/SDK/MDLReference/index.html#mdl_Window" "Window" >}}. A window is one of the layout elements that exist in MDL. These layout elements are called {{< docuLinks "/Resources/Documentation/Publish/SDK/MDLReference/index.html#Controls" "controls" >}}. The curled brackets define the window section, in which you can define properties of the window and insert further controls like a {{< docuLinks "/Resources/Documentation/Publish/SDK/MDLReference/index.html#mdl_Box" "Box" >}}.
@@ -186,13 +186,13 @@ You can add the module `GUIExample` to your workspace and play around with is.
 {{</alert>}}
 
 #### Access to Existing Fields of the Internal Network
-To interact with fields of the internal network in your user interface, we need to access these fields. To access the field of the internal module `Convolution`, which defines the <field>Kernel</field>, we need to use the internal network name. To find the internal field name, open the internal network of the macro module `Filter` (click on the module using the middle mouse button {{< mousebutton "middle" >}}).
+To interact with fields of the internal network in your user interface, we need to access these fields. To access the field of the internal module `Convolution`, which defines the *Kernel*, we need to use the internal network name. To find the internal field name, open the internal network of the macro module `Filter` (click on the module using the middle mouse button {{< mousebutton "middle" >}}).
 
-Then, open the panel of the module `Convolution` and right-click {{< mousebutton "right" >}} the field title <field>Use</field> of the box *Predefined Kernel* and select <field>Copy Name</field>. You now copied the internal network name of the field to your clipboard. The name is made up of *ModuleName.FieldName*, in this case <field>Convolution.predefKernel</field>.
+Then, open the panel of the module `Convolution` and right-click {{< mousebutton "right" >}} the field title *Use* of the box *Predefined Kernel* and select *Copy Name*. You now copied the internal network name of the field to your clipboard. The name is made up of *ModuleName.FieldName*, in this case <field>Convolution.predefKernel</field>.
 
 ![Convolution Module](images/tutorials/basicmechanics/Convolution.png "Convolution Module")
 
-In the panel of the module `Convolution`, you can change this variable <field>Kernel</field> via a drop-down menu. In MDL, a drop-down menu is called a {{< docuLinks "/Resources/Documentation/Publish/SDK/MDLReference/index.html#mdl_ComboBox" "ComboBox" >}}. We can take over the field <field>predefKernel</field>, its drop-down menu and all its properties by creating a new field in our panel and reference to the internal field <field>Convolution.predefKernel</field>, which already exist in the internal network.
+In the panel of the module `Convolution`, you can change this variable *Kernel* via a drop-down menu. In MDL, a drop-down menu is called a {{< docuLinks "/Resources/Documentation/Publish/SDK/MDLReference/index.html#mdl_ComboBox" "ComboBox" >}}. We can take over the field <field>predefKernel</field>, its drop-down menu and all its properties by creating a new field in our panel and reference to the internal field <field>Convolution.predefKernel</field>, which already exist in the internal network.
 
 Changes of the properties of this field can be done in the curled brackets using tags (here, we changed the title).
 

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

@@ -129,13 +129,13 @@ Window {
                 Viewer View2D.self {
                     type    = SoRenderArea
                     pw      = 400 ph = 400
-                    expandX = yes
-                    expandY = yes
+                    expandX = Yes
+                    expandY = Yes
                 }
                 Viewer View3D.self {
                     pw      = 400 ph = 400
-                    expandX = yes
-                    expandY = yes
+                    expandX = Yes
+                    expandY = Yes
                 }
             }
         }

mevislab.github.io/content/tutorials/dataobjects/surfaces/surfaceexample5.md

@@ -58,7 +58,7 @@ To translate the LUT values from the PVLs into color, open the panel of `SoLUTEd
 
 Our goal is to colorize faces of the *Octasphere* in red if they are close to or even intersect the cubic WEM. And we like to colorize faces of the *Octasphere* in green if these faces are far away from the cubic WEM.
 
-Open the tab *Editor* of the panel of `SoLUTEditor`. This tab allows to interactively select a color for each PVL value. Select the color point on the left side. Its <field>Position</field> value is supposed to be *0*, so we like to set the *Color* to *red* in order to color-code small distances between the WEMs in red. In addition to that, increase the <field>Opacity</field> of this color point. Next, select the right color point. Its <field>Position</field> is supposed to be *3* and thus equals the value of the field <field>New Range Max</field>. As these color points colorize large distances between WEMs, set the Color to *green*. You can add new color points by clicking on the colorized bar in the panel. Select, for example, the Color *yellow* for a color point in the middle. Select and shift the color points to get the desired visualization.
+Open the tab *Editor* of the panel of `SoLUTEditor`. This tab allows to interactively select a color for each PVL value. Select the color point on the left side. Its <field>Position</field> value is supposed to be *0*, so we like to set the <field>Color</field> to *red* in order to color-code small distances between the WEMs in red. In addition to that, increase the <field>Opacity</field> of this color point. Next, select the right color point. Its <field>Position</field> is supposed to be *3* and thus equals the value of the field <field>New Range Max</field>. As these color points colorize large distances between WEMs, set the Color to *green*. You can add new color points by clicking on the colorized bar in the panel. Select, for example, the Color *yellow* for a color point in the middle. Select and shift the color points to get the desired visualization.
 
 ![Changing the LUT](images/tutorials/dataobjects/surfaces/DO12_09.png "Changing the LUT")
 

mevislab.github.io/content/tutorials/summary/summary3.md

@@ -87,7 +87,7 @@ The *Source Box* shall provide the possibility to select a file for loading into
 
 Add a field to the *Parameters* section of your *.script* file. Name the field <field>openFile</field> and set <attribute>type</attribute> to *String* and <attribute>internalName</attribute> to <field>LocalImage.name</field>.
 
-Then, add another field to your *Box* for the *Source* and use the field name from *Parameters* section, in this case <field>openFile</field>. Set <attribute>browseButton</attribute> = *Yes* and <attribute>browseMode</attribute> = *open* and save your script.
+Then, add another field to your *Box* for the *Source* and use the field name from *Parameters* section, in this case <field>openFile</field>. Set <attribute>browseButton</attribute> to *Yes* and <attribute>browseMode</attribute> to *open* and save your script.
 
 {{< highlight filename="<MACRO_NAME>.script" >}}
 ```Stan

mevislab.github.io/content/tutorials/testing/testingexample1.md

@@ -94,7 +94,7 @@ The *OpenFiles* function first defines the `DicomImport` field <field>inputMode<
 When calling the function *TEST_DicomImport*, an expected value of 1.0 is defined. Then, the DICOM files are opened.
 
 {{<alert class="check" caption="Check">}}
-Call *Base.ignoreWarningAndError(MLAB.processEvents)* instead of *MLAB.processEvents()* if you receive error messages regarding invalid DICOM tags.
+Call <inlineCode>Base.ignoreWarningAndError(MLAB.processEvents)</inlineCode> instead of <inlineCode>MLAB.processEvents()</inlineCode> if you receive error messages regarding invalid DICOM tags.
 {{</alert>}}
 
 When <field>ready</field> is true, the test touches the <field>selectNextItem</field> trigger, so that the first images of the patient are selected and shown. The source directory will be written on the console as an additional log message for informative purposes.