fixed typos

Author: EduardKrieger

documentation/Functions.md

@@ -352,20 +352,20 @@ If the tutorial should be tested on the console environment, you have to specify
 ### displayContent <a name="displayContent"></a>
 #### parameter
 1. The title of the step. 
-2. An array of json objects with files, content, or images to be rendered within the katacoda step. The use for this function is to display an image and some descriptive text. No Katacoda Syntax is allowed in the files or the content!
+2. An array of json objects with files, content, or images to be rendered within the Katacoda step. The use for this function is to display an image and some descriptive text. No Katacoda syntax is allowed in the files or the content!
 3. (Optional) Path to the current directory where the user is located (relative to the workspace directory). Only needed if the directory is changed within this step.
 #### example 
 display("Step title", [{ "file": "files/description.asciidoc" }, { "content": "This is just plain content." }, { "image": "files/image.png" }])
 
 #### Details
 Available attributes in the json objects:
 
-1. file: Path to a file whose content is to be displayed in the katacoda step (e.g. .asciidoc or .txt file). The file should be following the formating of asciidoc files. 
-2. content: Plain text to be displayed in the katacoda step. This Text should be following the formating of asciidoc files.
-3. image: Path to an image to be displayed in the katacoda step.
+1. file: Path to a file whose content is to be displayed in the Katacoda step (e.g. .asciidoc or .txt file). The file should be following the formating of asciidoc files. 
+2. content: Plain text to be displayed in the Katacoda step. This Text should be following the formating of asciidoc files.
+3. image: Path to an image to be displayed in the Katacoda step.
 
 #### Formatting rules for content and .asciidoc or .txt files.
-* You can add headers to structure your text. The generated headers are shown in the examples below. The headers should fit into the overall structure of the generated wiki so level 1 header arent allowed, but the other header can be used at your judgement.
+* You can add headers to structure your text. The generated headers are shown in the examples below. The headers should fit into the overall structure of the generated wiki so level 1 header are not allowed, but the other header can be used at your judgement.
 * A list always needs an empty newline between the last row and the list.
 * Use asciidoc style of links
 

engine/wikiRunner.ts

@@ -8,11 +8,13 @@ import * as ejs from "ejs";
 export abstract class WikiRunner extends Runner {
 
     public outputPathTutorial: string;
+    public commandCntMap = new Map();
+
+    protected readonly INSTALLED_TOOLS: string = "installedTools";
     protected fileTypeMap = new Map([ [".java", "java"],[".ts", "typescript"],
     [".js", "javascript"], [".html", "html"],
     [".scss", "css"], [".asciidoc", "asciidoc"], ]);
-    protected readonly INSTALLED_TOOLS: string = "installedTools";
-    public CommandCntMap = new Map();
+    
 
 
     init(playbook: Playbook): void {
@@ -21,7 +23,7 @@ export abstract class WikiRunner extends Runner {
         this.setVariable(this.WORKSPACE_DIRECTORY, path.join(this.getWorkingDirectory()));
         this.setVariable(this.INSTALLED_TOOLS, "");
         for(let i = 0; i< playbook.steps.length; i++){
-            this.CommandCntMap.set(i, playbook.steps[i].lines.length-1);
+            this.commandCntMap.set(i, playbook.steps[i].lines.length-1);
         }
     }
 
@@ -49,7 +51,7 @@ export abstract class WikiRunner extends Runner {
     }
 
     protected checkForTextAfter(runCommand: RunCommand): string{
-        return this.CommandCntMap.get(runCommand.stepIndex) == runCommand.lineIndex 
+        return this.commandCntMap.get(runCommand.stepIndex) == runCommand.lineIndex 
             ? runCommand.textAfter
             : undefined;
     }

runners/wikiConsole/templates/adaptTemplates.asciidoc

@@ -1,7 +1,7 @@
 <%if(title){%>== <%- title; %>
 <%if(text){%><%- text; %><%}%><%}else{%>
 
-=== Generate CobiGen Templates 
+=== Generate CobiGen templates 
 <%if(text){%><%- text; %><%}%>
 
 How to use CobiGen, to generate templates for the following code generation.
@@ -12,7 +12,7 @@ More information about CobiGen on https://devonfw.com/website/pages/docs/master-
 
 * An installed devonfw distribution is needed. To execute the CobiGen CLI, you have to install the devonfw IDE first. Follow the https://devonfw.com/website/pages/docs/devonfw-ide-introduction.asciidoc.html[devonfw IDE] documentation to install the same.
 
-==== Generate CobiGen Templates with CobiGen CLI
+==== Generate CobiGen templates with CobiGen CLI
 
 First open a command prompt in your current workspace. You should be inside your devonfw directory, if not change your directory to *<%= devonPath;%>*.
 Run the CobiGen command  `devon cobigen adapt-templates`

runners/wikiConsole/templates/addSetupScript.asciidoc

@@ -1,7 +1,7 @@
 <%if(title){%>== <%- title; %>
 <%if(text){%><%- text; %><%}%><%}else{%>
 
-=== Run a Setupscript
+=== Run a setup script
 <%if(text){%><%- text; %><%}%><%}%>
 
 Run a Script to setup the enviroment for the Tutorial.  
@@ -33,7 +33,7 @@ The editor opens a new editor window for an untitled file where you can insert t
 Save the file by selecting *Save* or *Save as* in the file context menu or by using the keyboard shortcut ctrl+s.
 A file explorer window opens where you should set the filename to *<%= scriptNameLinux; %>* and save it to your current directory. 
 
-==== Run the Setupscript
+==== Run the setup script
 
 .Operating system
 . Windows + 

runners/wikiConsole/templates/createFolder.asciidoc

@@ -1,10 +1,10 @@
 <%if(title){%>== <%- title; %>
 <%if(text){%><%- text; %><%}%><%}else{%>
 
-=== Create Folder
+=== Create folder
 <%if(text){%><%- text; %><%}%><%}%>
 
-==== Creating a new Folder
+==== Creating a new folder
 
 A folder can be created either from within an IDE like VSCode or Eclipse by simply right clicking in the file explorer and creating a new folder. Another approach is to use the Terminal. 
 

runners/wikiEclipse/templates/adaptTemplates.asciidoc

@@ -1,7 +1,7 @@
 <%if(title){%>== <%- title; %>
 <%if(text){%><%- text; %><%}%><%}else{%>
 
-=== Generate new Templates for CobiGen 
+=== Generate new templates for CobiGen 
 
 <%if(text){%><%- text; %><%}%>
 
@@ -11,7 +11,7 @@ More information about CobiGen on https://devonfw.com/website/pages/docs/master-
 ==== Prerequisites
 An installed devonfw distribution is needed. To execute CobiGen in Eclipse IDE, you have to install the devonfw IDE with the Eclipse IDE first. Follow the https://devonfw.com/website/pages/docs/devonfw-ide-introduction.asciidoc.html[devonfw-ide] documentation to install the same.
 
-==== Generate CobiGen Templates with Eclipse IDE
+==== Generate CobiGen templates with Eclipse IDE
 
 First, open Eclipse IDE, and if your file explorer is empty load any file, create a file, or project into Eclipse.
 Right-click any file in the file explorer to open a dropdown menu where you can select CobiGen and an additional menu opens. Select *Adapt Templates...* and CobiGen starts generating a new template folder. CobiGen gives you a warning that existing templates will be overridden in your current workspace, you can confirm to continue. If the folder is already existing CobiGen will inform you, that for updating your templates you have to use the *Update Templates...* functionality else CobiGen will create a folder and download the latest template to use it. You can confirm the messages with *OK* or *Update* and the CobiGen templates folder is imported successfully.