[gimp-web/testing: 1/2] Fix for #131

[Pat David <patdavid src gnome org>]

commit 191843f5a7373454300df212b19e2d82f45a2fdf
Author: nmat <15926-nmat users noreply gitlab gnome org>
Date:   Sat May 18 09:27:55 2019 +0200

    Fix for #131
    
    * https://gitlab.gnome.org/Infrastructure/gimp-web/issues/131
    
    * Thanks for the findings @OddGrenadier

 .../tutorials/Automate_Editing_in_GIMP/index.md    | 37 +++++++++++-----------
 1 file changed, 18 insertions(+), 19 deletions(-)
---
diff --git a/content/tutorials/Automate_Editing_in_GIMP/index.md 
b/content/tutorials/Automate_Editing_in_GIMP/index.md
index 34335d2a..d19ee5d3 100644
--- a/content/tutorials/Automate_Editing_in_GIMP/index.md
+++ b/content/tutorials/Automate_Editing_in_GIMP/index.md
@@ -47,9 +47,9 @@ Suppose we wanted to set up the grid spacing so that it is centered on the image
 
 <figure>
 <img src="{filename}CommandsPythonConsole.jpg" alt="CommandsPythonConsole.jpg" />
-<figcaption> 
+<figcaption>
 Commands in the Python Console
-</figcaption> 
+</figcaption>
 </figure>
 
 If you watch the image as you enter the commands and have the Grid turned “ON” you will see the grid spacing 
on the active image change as we execute these commands.
@@ -76,9 +76,9 @@ Example "Exec" Loop:
 
 <figure>
 <img src="{filename}CommanderMacroSubMenu.jpg" alt="CommanderMacroSubMenu.jpg" />
-<figcaption> 
+<figcaption>
 Commander Macro Sub-Menu
-</figcaption> 
+</figcaption>
 </figure>
 
 ### Architecture
@@ -122,7 +122,7 @@ A final thing that we need to talk about that is not a 'category' of execution b
     def autoCommander(theImage, cmdListIndex):
         ...
         commanderName = cmdList[cmdListIndex]
-        ...     
+        ...
     #
     register (
         "autoCommander",         # Name registered in Procedure Browser
@@ -143,14 +143,14 @@ We now need to talk about the form and organization of the data that we intend t
 Python has several built in data structures such as dictionaries, lists to name a couple. A very powerful 
library structure that is well suited to our particular needs is a “tree”. A couple of the key features that 
make them well suited for our application are:
 
 1.  Trees have a natural 'hierarchical' feel to them, kind of like a directory structure or the 'folders' of 
an operating system. The levels of hierarchy can be thought of as ‘containing’ the contents in the lower 
level.
-2.  A branch can hold an indefinite number of elements, and those elements can be either a leaf with 
attributes or a sub-branch to another level. This lends a lot of flexibility with the way we structure of the 
data.
+2.  A branch can hold an indefinite number of elements, and those elements can be either a leaf with 
attributes or a sub-branch to another level. This lends a lot of flexibility with the way we structure the 
data.
 3.  The input / output format is XML, which is not only hierarchical, but it is text so it is human readable 
and portable to any platform (computer / OS).
 
 <figure>
 <img src="{filename}XmlHierarchyContainers.jpg" alt="XmlHierarchyContainers.jpg" />
-<figcaption> 
+<figcaption>
 XML Hierarchy - Containers
-</figcaption> 
+</figcaption>
 </figure>
 
 The examples use ElementTree to read and write the data between trees and XML. ElementTree is included with 
Python and described in the Python documentation, so we will not go into detail about the mechanics of tree 
structures here.
@@ -163,7 +163,7 @@ If you are using Windows the path would look something like:
 
     C:\Users\stephen\.gimp-2.8\myXml
 
-We will be dealing with a couple of types of pseudo code and xml files, and those will be keep in separate 
directories under myXml, but we will get to that in a bit.
+We will be dealing with a couple of types of pseudo code and xml files, and those will be kept in separate 
directories under myXml; however, we will get to that in a bit.
 
 ## Macro Implementation – Revisited
 
@@ -233,9 +233,9 @@ The Xml generator can be called from a GUI menu.
 
 <figure>
 <img src="{filename}PseudoCodeImported.jpg" alt="PseudoCodeImported.jpg" />
-<figcaption> 
+<figcaption>
 Xml files built
-</figcaption> 
+</figcaption>
 </figure>
 
 ### Displaying the Macro Names in a Menu
@@ -485,19 +485,19 @@ The following Appendices contain notes which are more specific to setting up the
 
 All of the example scripts begin with “auto”, e.g. autoAutoUpdate.py, autoBase.py, ... If you try them but 
then decide you don't like them they should be pretty easy to find and remove. The following example scripts 
should be loaded into your gimp/plug-ins directory. Something like /home/stephen/.gimp-2.8/plug-ins if your 
user name is stephen and you were using gimp 2.8\. Click on the filename to download.
 
-1.  [autoAutoUpdate.py](plug-ins/autoAutoUpdate.py)  
+1.  [autoAutoUpdate.py](plug-ins/autoAutoUpdate.py)
     Runs the auto update function on a directory of images.
-2.  [autoBase.py](plug-ins/autoBase.py)  
+2.  [autoBase.py](plug-ins/autoBase.py)
     Contains the classes that read and write the XML files that affect how the update works.
-3.  [autoCommander.py](plug-ins/autoCommander.py)  
+3.  [autoCommander.py](plug-ins/autoCommander.py)
     Runs the 'Commander' macros.
-4.  [autoJpegToXcf.py](plug-ins/autoJpegToXcf.py)  
+4.  [autoJpegToXcf.py](plug-ins/autoJpegToXcf.py)
     Imports the images into xcf format and assigns properties to image.
-5.  [autoRWparasites.py](plug-ins/autoRWparasites.py)  
+5.  [autoRWparasites.py](plug-ins/autoRWparasites.py)
     User Interface functions to read and write image parasites from the menu.
-6.  [autoWriteXml.py](plug-ins/autoWriteXml.py)  
+6.  [autoWriteXml.py](plug-ins/autoWriteXml.py)
     Reads \*.def files and generates XML for commander macros, workflows, and properties.
-7.  [autoXcfToJpg.py](plug-ins/autoXcfToJpg.py)  
+7.  [autoXcfToJpg.py](plug-ins/autoXcfToJpg.py)
     Exports the finished images back to jpeg format.
 
 ### Setting up the Example Pseudo Code
@@ -661,4 +661,3 @@ Image - Running your code in the Gimp Python Console
 </a>
 <br><span xmlns:dct="http://purl.org/dc/terms/";>GIMP Tutorial - Automate Editing</span> by <a 
rel="cc:attributionURL" xmlns:cc="http://creativecommons.org/ns#";>Stephen Kiel</a> is licensed under a <a 
href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US"; rel="license">Creative Commons 
Attribution-ShareAlike 3.0 Unported License</a>. The code sources in this tutorial are licensed by Stephen 
Kiel under the conditions of the <a href="https://www.gnu.org/copyleft/gpl.html";>GNU Public License GPL 
V3</a>.
 </small>
-