Fixed mistyping on main page
diff --git a/blog/2014/09/15/1_5_2-released.html b/blog/2014/09/15/1_5_2-released.html
index d07a009..f6c3118 100644
--- a/blog/2014/09/15/1_5_2-released.html
+++ b/blog/2014/09/15/1_5_2-released.html
@@ -72,8 +72,7 @@
 
 <p>Now, multiple adjacent single line comments or a single multiline comment exactly above a procedure is considired to be its user-defined description. This description is interpreted as raw HTML and used in autogenerated documentation. So, consider a procedure definition like this:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;// &lt;p&gt;Convenience method to set given &lt;b&gt;text&lt;/b&gt;
+<p><pre ><code class="language-ecl">&#x200b;// &lt;p&gt;Convenience method to set given &lt;b&gt;text&lt;/b&gt;
 // into a text field, located after a &lt;b&gt;label&lt;/b&gt;
 // in given &lt;b&gt;parent&lt;/b&gt;&lt;/p&gt;
 // &lt;p&gt;Example:&lt;/p&gt;
@@ -85,6 +84,7 @@
     $parent | get-editbox -after [get-label $label] | set-text $text
 }
 </code></pre>
+</p>
 
 <p>the resulting doc, which is displayed in documentation hover and completion proposals, would look like this:</p>
 
@@ -112,16 +112,17 @@
 <h4>delete-file command (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=442660">#442660</a>)</h4>
 
 <p>Now it is possible to remove files/folders from a file system:
-</p>
 <pre ><code class="language-ecl">&#x200b;format "%s/.my-app-tmp" [get-java-property "user.home"] | uri-to-file | delete-file
 </code></pre>
+</p>
 
 <h4>improved switch command (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=442016">#442016</a>)</h4>
 
 <p>Switch command accept an input value and a number of cases to compare value with:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;proc "get-os" {
+
+<p><pre ><code class="language-ecl">&#x200b;proc "get-os" {
     invoke-static -pluginId "org.eclipse.core.runtime"
                   -className "org.eclipse.core.runtime.Platform"
                   -methodName getOS
@@ -145,6 +146,7 @@
 &nbsp;
 print-os [get-os]
 </code></pre>
+</p>
 
 <p>Stay tuned!</p>
 
diff --git a/blog/2014/09/19/regression-testing.html b/blog/2014/09/19/regression-testing.html
index 9bd3d05..61fe931 100644
--- a/blog/2014/09/19/regression-testing.html
+++ b/blog/2014/09/19/regression-testing.html
@@ -173,7 +173,8 @@
 <p>You can replay this test case right from the editor. It will be executed successfully, however that's not what you really want &ndash; right now test case verifies wrong behavior, caused by a bug in an application. The test case should pass only after the bug will be fixed. Before describing a way to make this test case failing, let's quickly go through recorded script:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;with [get-view "Package Explorer" | get-tree] {
+
+<p><pre ><code class="language-ecl">&#x200b;with [get-view "Package Explorer" | get-tree] {
     select "project/folder1" "project/folder2"
     get-menu "Compare With/Each Other" | click
 }
@@ -186,6 +187,7 @@
 }
 get-editor "Compare ('project/folder1/file.txt' - 'project/folder2/file.txt')" | close 
 </code></pre>
+</p>
 
 <p>The scripting language (ECL) is inspired by TCL and Powershell &ndash; it consists of commands with arguments, connected by pipes and an output of the left command can be passed as an input to the right command. Square brackets (<code class="language-ecl">&#x200b;[]</code>) are used to pass an output of a command as an argument to another command. Curly brackets (<code class="language-ecl">&#x200b;{}</code>) are used to pass a script as an argument. It allows command to execute this script in some context.</p>
 
@@ -205,12 +207,13 @@
 <p>Next line, <code class="language-ecl">&#x200b;get-window Compare | get-label ...</code>, was recorded from an assertion mode. The general pattern here looks like this:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;get some UI object | get-property 'propertyName'
+
+<p><pre ><code class="language-ecl">&#x200b;get some UI object | get-property 'propertyName'
     | equals/&#x200b;not-equals 'expectedValue'
     | verify-true/&#x200b;verify-false
 </code></pre>
 
-<p><br/>
+<br/>
 In this particular case, we added an assertion for a property, which is used to control location, so in fact there is some repetition here, that does not affect anything, but we could just use <code class="language-ecl">&#x200b;get-window Compare | get-label &quot;There are...&quot;</code> as well &ndash; in case when there's no label with this text, the test would fail any way.</p>
 
 <p>Another important thing to notice about this script is that it does not contain any waiting logic &ndash; it waits for background operations automatically (calculation of comparison results in this case).</p>
@@ -219,9 +222,9 @@
 
 <p>Now let's make our test case to fail correctly. At first, we don't need a last line (<code class="language-ecl">&#x200b;get-editor ... | close</code>), because in case of correct behaviour, there should be no such editor. Instead we want to ensure that there is a window with correct label, so let's replace a last line of this script with this:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;get-window Compare | get-label "There are no differences between the selected inputs."
+<p><pre ><code class="language-ecl">&#x200b;get-window Compare | get-label "There are no differences between the selected inputs."
 </code></pre>
+</p>
 
 <p>Now, if you execute the resulting test case, it will fail as expected:</p>
 
@@ -269,8 +272,7 @@
 <p>As usual, create a test case, add launch and workbench contexts to it, and record test actions &ndash; open   <span class="uiElement">Launch configurations</span>
  dialog, select launch configuration and press required buttons. The resulting script will look like this:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;get-menu "Run/Run Configurations..." | click
+<p><pre ><code class="language-ecl">&#x200b;get-menu "Run/Run Configurations..." | click
 with [get-window "Run Configurations"] {
   get-tree | select "OSGi Framework/org.eclipse.ui osgi launch"
   get-button "Add Required Bundles" | click
@@ -278,6 +280,7 @@
   get-window Validation | get-button OK | click
 }
 </code></pre>
+</p>
 
 <p>We can replay it and obviously the test case will pass, as it does not contain any assertions yet.</p>
 
@@ -286,8 +289,10 @@
 <p>To assert that validation completed successfully, change the last line to this:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;get-window Validation | get-label "No problems were detected."
+
+<p><pre ><code class="language-ecl">&#x200b;get-window Validation | get-label "No problems were detected."
 </code></pre>
+</p>
 
 <p>Once a test case is replayed again, it correctly fails with a message <kbd>The Label "No problems were detected." could not be found</kbd>. To make sure that the test is correct, run the same test without any modifications on Kepler to see that it passes:</p>
 
@@ -327,7 +332,8 @@
 <p>The recorded script is below:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;get-menu "File/Import..." | click
+
+<p><pre ><code class="language-ecl">&#x200b;get-menu "File/Import..." | click
 with [get-window Import] {
     get-tree | select "General/Existing Projects into Workspace"
     get-button "Next &gt;" | click
@@ -340,26 +346,27 @@
 }
 get-window Import | get-tree | get-property itemCount | equals 0 | verify-true
 </code></pre>
+</p>
 
 <p><br/>
 You may notice that there's an interesting command recorded &#x2013; <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#set-dialog-result">set-dialog-result</a>. That's how RCPTT handles native dialogs: during recording, it remembers a value, selected by user in a native dialog, and stores it as a <code class="language-ecl">&#x200b;set-dialog-result</code> command. During test case execution RCPTT runtime automatically returns stored value to application code instead of opening a native dialog.</p>
 
 <p>However, in order to make a test case fully portable across machines and operating systes, we need to slightly modify this script in order to replace an absolute path with a value, relative to a home folder. This can be achieved by using two ECL commands &#x2013; <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#get-java-propery">get-java-propery</a> and <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#format">format</a>:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;set-dialog-result Folder [format "%s/projectsToImport" [get-java-property "user.home"]]
+<p><pre ><code class="language-ecl">&#x200b;set-dialog-result Folder [format "%s/projectsToImport" [get-java-property "user.home"]]
 </code></pre>
+</p>
 
 <h4>Asserting results</h4>
 
 <p>Next, we also need to modify the last part of a script, which asserts the results &#x2013; instead of asserting that there are no children, actually we want to assert the correct behavior, i.e. there is one child, <kbd>goodProject</kbd>. This can be done like this:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;with [get-window Import | get-tree] {
+<p><pre ><code class="language-ecl">&#x200b;with [get-window Import | get-tree] {
     select "goodProject.*"
     get-property itemCount | equals 1 | verify-true
 }
 </code></pre>
+</p>
 
 <p>Pay attention to this line &ndash; <code class="language-ecl">&#x200b;select &quot;goodProject.*&quot;</code>. Here we use a regular expression instead of full text of a tree item (full text also includes an absolute path on a file system). It is possible to use <code class="language-ecl">&#x200b;format</code> command again to construct a full text here, but in this case it is faster to simply strip an end text by <code class="language-ecl">.&#42;</code>.</p>
 
diff --git a/blog/2014/10/23/1_5_3-released.html b/blog/2014/10/23/1_5_3-released.html
index bfdc3f0..cb44d49 100644
--- a/blog/2014/10/23/1_5_3-released.html
+++ b/blog/2014/10/23/1_5_3-released.html
@@ -74,8 +74,7 @@
 
 <p>Then recorded script would look like this:</p>
 
-<p></p>
-<pre data-line="5"><code class="language-ecl">&#x200b;with [get-window Preferences] {
+<p><pre data-line="5"><code class="language-ecl">&#x200b;with [get-window Preferences] {
     with [get-window "Edit Proxy Entry"] {
         get-editbox -after [get-label "User:"] | set-text ooo
         get-editbox -after [get-label "Password:"] 
@@ -83,6 +82,7 @@
     }
 }
 </code></pre>
+</p>
 
 <p><br/></p>
 
diff --git a/blog/2014/11/11/rcptt-blog-launched.html b/blog/2014/11/11/rcptt-blog-launched.html
index 44c06f2..039d265 100644
--- a/blog/2014/11/11/rcptt-blog-launched.html
+++ b/blog/2014/11/11/rcptt-blog-launched.html
@@ -68,8 +68,7 @@
 
 <p>Oh, and by the way, if you haven't noticed yet, now we've got a nice syntax colorer for ECL snippets (thanks to an awesome <a href="http://prismjs.com">prism.js</a> library):</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;proc "find-tab-folder" [val activePage] {
+<p><pre ><code class="language-ecl">&#x200b;proc "find-tab-folder" [val activePage] {
   loop [val index [int 0]] {
     let [val folder [get-tab-folder -index $index]] {
       let [val folderActivePage [$folder | get-property activePage -raw]] {
@@ -85,6 +84,7 @@
 find-tab-folder "Task List" | get-object | save-screenshot "/tmp/tmp/tsk.png"
 //get-property activePage | equals "Package Explorer" | verify-true
 </code></pre>
+</p>
 
 <p>Things like rss/atom feeds and improved navigation are to be added in a nearest future.</p>
 
diff --git a/blog/2014/11/21/screenshots-with-rcptt.html b/blog/2014/11/21/screenshots-with-rcptt.html
index 7667cdb..87f98eb 100644
--- a/blog/2014/11/21/screenshots-with-rcptt.html
+++ b/blog/2014/11/21/screenshots-with-rcptt.html
@@ -231,6 +231,7 @@
   <li>Launch tests from attached project</li>
   <li>Go to your home folder and examine Documents/rcptt-screenshots folder
 </ul>    
+
         </div>
                     <p class="categories">
             Categories:
diff --git a/blog/2014/12/10/test-about-dialog.html b/blog/2014/12/10/test-about-dialog.html
index 0fbf247..b971124 100644
--- a/blog/2014/12/10/test-about-dialog.html
+++ b/blog/2014/12/10/test-about-dialog.html
@@ -183,6 +183,7 @@
 </code></pre>
 
 
+
         </div>
                     <p class="categories">
             Categories:
diff --git a/blog/atom.xml b/blog/atom.xml
index a31a779..78bf1be 100644
--- a/blog/atom.xml
+++ b/blog/atom.xml
@@ -3,7 +3,9 @@
     <title><![CDATA[RCP Testing Tool Blog]]></title>
     <link href="https://www.eclipse.org/rcptt/atom.xml" rel="self"/>
     <link href="https://www.eclipse.org/rcptt/"/>
-    <updated>2014-12-30T15:16:29+00:00</updated>
+    <updated>
+Warning: current() expects parameter 1 to be array, boolean given in phar://H:/rcptt/git/rcptt-site/sculpin.phar/vendor/twig/twig/lib/Twig/Extension/Core.php on line 721
+2015-02-09T12:14:54+00:00</updated>
     <id>https://www.eclipse.org/rcptt/blog</id>
             <author>
             <name><![CDATA[RCP Testing Tool Team]]></name>            <email><![CDATA[rcptt-dev@eclipse.org]]></email>        </author>
@@ -101,8 +103,7 @@
 
 <p>Oh, and by the way, if you haven't noticed yet, now we've got a nice syntax colorer for ECL snippets (thanks to an awesome <a href="http://prismjs.com">prism.js</a> library):</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;proc "find-tab-folder" [val activePage] {
+<p><pre ><code class="language-ecl">&#x200b;proc "find-tab-folder" [val activePage] {
   loop [val index [int 0]] {
     let [val folder [get-tab-folder -index $index]] {
       let [val folderActivePage [$folder | get-property activePage -raw]] {
@@ -118,6 +119,7 @@
 find-tab-folder "Task List" | get-object | save-screenshot "/tmp/tmp/tsk.png"
 //get-property activePage | equals "Package Explorer" | verify-true
 </code></pre>
+</p>
 
 <p>Things like rss/atom feeds and improved navigation are to be added in a nearest future.</p>
 
@@ -144,8 +146,7 @@
 
 <p>Then recorded script would look like this:</p>
 
-<p></p>
-<pre data-line="5"><code class="language-ecl">&#x200b;with [get-window Preferences] {
+<p><pre data-line="5"><code class="language-ecl">&#x200b;with [get-window Preferences] {
     with [get-window "Edit Proxy Entry"] {
         get-editbox -after [get-label "User:"] | set-text ooo
         get-editbox -after [get-label "Password:"] 
@@ -153,6 +154,7 @@
     }
 }
 </code></pre>
+</p>
 
 <p><br/></p>
 
@@ -228,8 +230,7 @@
 
 <p>Now, multiple adjacent single line comments or a single multiline comment exactly above a procedure is considired to be its user-defined description. This description is interpreted as raw HTML and used in autogenerated documentation. So, consider a procedure definition like this:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;// &lt;p&gt;Convenience method to set given &lt;b&gt;text&lt;/b&gt;
+<p><pre ><code class="language-ecl">&#x200b;// &lt;p&gt;Convenience method to set given &lt;b&gt;text&lt;/b&gt;
 // into a text field, located after a &lt;b&gt;label&lt;/b&gt;
 // in given &lt;b&gt;parent&lt;/b&gt;&lt;/p&gt;
 // &lt;p&gt;Example:&lt;/p&gt;
@@ -241,6 +242,7 @@
     $parent | get-editbox -after [get-label $label] | set-text $text
 }
 </code></pre>
+</p>
 
 <p>the resulting doc, which is displayed in documentation hover and completion proposals, would look like this:</p>
 
@@ -254,4 +256,4 @@
 	    
 	    ]]></content>
         </entry>
-    </feed>
\ No newline at end of file
+    </feed>
diff --git a/blog/categories/index.html b/blog/categories/index.html
index 9e9243a..25caae6 100644
--- a/blog/categories/index.html
+++ b/blog/categories/index.html
@@ -66,7 +66,8 @@
 <a href="https://www.eclipse.org/rcptt/blog/categories/ecl">ecl</a>
 <a href="https://www.eclipse.org/rcptt/blog/categories/news">news</a>
 <a href="https://www.eclipse.org/rcptt/blog/categories/tutorials">tutorials</a>
-</div>	      </div>
+</div>
+	      </div>
 
     </section>
     <script src="https://www.eclipse.org/rcptt/shared/js/main.js"></script>
diff --git a/blog/index.html b/blog/index.html
index f83cefb..2ad35a9 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -153,8 +153,7 @@
 
 <p>Oh, and by the way, if you haven't noticed yet, now we've got a nice syntax colorer for ECL snippets (thanks to an awesome <a href="http://prismjs.com">prism.js</a> library):</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;proc "find-tab-folder" [val activePage] {
+<p><pre ><code class="language-ecl">&#x200b;proc "find-tab-folder" [val activePage] {
   loop [val index [int 0]] {
     let [val folder [get-tab-folder -index $index]] {
       let [val folderActivePage [$folder | get-property activePage -raw]] {
@@ -170,6 +169,7 @@
 find-tab-folder "Task List" | get-object | save-screenshot "/tmp/tmp/tsk.png"
 //get-property activePage | equals "Package Explorer" | verify-true
 </code></pre>
+</p>
 
 <p>Things like rss/atom feeds and improved navigation are to be added in a nearest future.</p>
 
@@ -196,8 +196,7 @@
 
 <p>Then recorded script would look like this:</p>
 
-<p></p>
-<pre data-line="5"><code class="language-ecl">&#x200b;with [get-window Preferences] {
+<p><pre data-line="5"><code class="language-ecl">&#x200b;with [get-window Preferences] {
     with [get-window "Edit Proxy Entry"] {
         get-editbox -after [get-label "User:"] | set-text ooo
         get-editbox -after [get-label "Password:"] 
@@ -205,6 +204,7 @@
     }
 }
 </code></pre>
+</p>
 
 <p><br/></p>
 
diff --git a/blog/page/2/index.html b/blog/page/2/index.html
index 44bd1b0..79b8bf1 100644
--- a/blog/page/2/index.html
+++ b/blog/page/2/index.html
@@ -75,8 +75,7 @@
 
 <p>Now, multiple adjacent single line comments or a single multiline comment exactly above a procedure is considired to be its user-defined description. This description is interpreted as raw HTML and used in autogenerated documentation. So, consider a procedure definition like this:</p>
 
-<p></p>
-<pre ><code class="language-ecl">&#x200b;// &lt;p&gt;Convenience method to set given &lt;b&gt;text&lt;/b&gt;
+<p><pre ><code class="language-ecl">&#x200b;// &lt;p&gt;Convenience method to set given &lt;b&gt;text&lt;/b&gt;
 // into a text field, located after a &lt;b&gt;label&lt;/b&gt;
 // in given &lt;b&gt;parent&lt;/b&gt;&lt;/p&gt;
 // &lt;p&gt;Example:&lt;/p&gt;
@@ -88,6 +87,7 @@
     $parent | get-editbox -after [get-label $label] | set-text $text
 }
 </code></pre>
+</p>
 
 <p>the resulting doc, which is displayed in documentation hover and completion proposals, would look like this:</p>
 
diff --git a/blog/tags/index.html b/blog/tags/index.html
index 80ecdb9..03c65ff 100644
--- a/blog/tags/index.html
+++ b/blog/tags/index.html
@@ -62,7 +62,8 @@
 		<h2>Tags</h2>
 
 <div>
-</div>	      </div>
+</div>
+	      </div>
 
     </section>
     <script src="https://www.eclipse.org/rcptt/shared/js/main.js"></script>
diff --git a/documentation/faq/get-property-raw/index.html b/documentation/faq/get-property-raw/index.html
index ab4acd8..484fb39 100644
--- a/documentation/faq/get-property-raw/index.html
+++ b/documentation/faq/get-property-raw/index.html
@@ -97,8 +97,10 @@
 is executed, internally it does not return a property value, but instead it returns a special
  verification handle object. So a script like this:
 </p>
-<pre ><code class="language-ecl">&#x200b;get-editbox | get-property "text" | equals "foo" | verify-true
+
+<p><pre ><code class="language-ecl">&#x200b;get-editbox | get-property "text" | equals "foo" | verify-true
 </code></pre>
+</p>
 
 <p>Internally it is executed like this:</p>
 
@@ -116,23 +118,27 @@
 property values, for instance, use control enablement in if condition. <BR>Thus we added a <b>-raw</b> key to <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#get-property">get-property</a> command:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;// returns VerifyHandle, pretty useless without verify-true:
+
+<p><pre ><code class="language-ecl">&#x200b;// returns VerifyHandle, pretty useless without verify-true:
 get-editbox | get-property text
 // returns actual text value
 // can be stored in variable, passed to another command, etc 
 get-editbox | get-property text -raw 
 </code></pre>
+</p>
 
 <p>In order to be able to operate with raw values, we also added commands 
 like <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#eq">eq</a>, <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#gt">gt</a>, <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#lt">lt</a> and <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#assert-true">assert-true</a> as general-purpose ECL commands, without any RCPTT specifics. And since <code class="language-ecl">&#x200b;assert-true</code> does not have a 'context' of assertion, it just gets a single boolean value as an input, we added -message argument to it, so that users can specify an error message.
 Hence finally we came to a situation when the same assertion can be expressed in two different ways:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;// Old RCPTT style:
+
+<p><pre ><code class="language-ecl">&#x200b;// Old RCPTT style:
 get-property text | equals foo | verify-true
 //ECL style:
 get-property text -raw | eq foo | assert-true "Text is not 'foo'"
 </code></pre>
+</p>
 
 <p>Indeed, many users found this situation confusing and wondered whether they need to
  use <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#eq">eq</a> or <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#equals">equals</a>,  so finally we also made old RCPTT commands, like <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#equals">equals</a> and <a href="http://download.eclipse.org/rcptt/release/1.5.4/doc/ecl/index.html#verify-true">verify-true</a> more flexible,  so that they behave differently depending on kind of input: if they get a VerifyHandle as an input, they use old behavior, if they get an actual value, they behave as their general-purpose ECL counterparts.</p>
diff --git a/documentation/userguide/getstarted/index.html b/documentation/userguide/getstarted/index.html
index c111a04..effabd4 100644
--- a/documentation/userguide/getstarted/index.html
+++ b/documentation/userguide/getstarted/index.html
@@ -196,7 +196,8 @@
 <p>Before we go to <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/">Contexts</a>, let's take a look at recorded script:</p>
 
 <p></p>
-<pre ><code class="language-ecl">&#x200b;get-menu "File/New/Java Project" | click
+
+<p><pre ><code class="language-ecl">&#x200b;get-menu "File/New/Java Project" | click
 with [get-window "New Java Project"] {
     get-editbox -after [get-label "Project name:"] | set-text sample
     get-button Finish | click
@@ -204,6 +205,7 @@
 get-view "Package Explorer" | get-tree | get-item "sample/src"
     | get-property childCount | equals 0 | verify-true
 </code></pre>
+</p>
 
 <p>It's probably is understandable intuitively, but here's a brief description how does it work. A scripting language we use, <a href="https://www.eclipse.org/rcptt/documentation/userguide/ecl/">ECL</a> (which stands for Eclipse Command Language), is inspired by TCL and Powershell, and it consists of commands, connected by pipes.</p>
 
diff --git a/documentation/userguide/procedures/index.html b/documentation/userguide/procedures/index.html
index 8fae8b2..44ff42f 100644
--- a/documentation/userguide/procedures/index.html
+++ b/documentation/userguide/procedures/index.html
@@ -312,7 +312,8 @@
 $ cd q7.examples.procs<br>
 $ mvn clean package<br>
   </div>
-</div>  </div>
+</div>
+  </div>
 </div>
       </div>
 
diff --git a/main_page_content.html b/main_page_content.html
index e40f49d..d6e78e4 100644
--- a/main_page_content.html
+++ b/main_page_content.html
@@ -1,6 +1,6 @@
 <div id="midcolumn">
 <h1>RCP Testing Tool</h1>
-<p >RCP Testing Tool is a project for GUI testing automation of Eclispe-based applications. RCPTT is fully aware about Eclipse Platform's internals, hiding this complexity from end users and allowing QA engineers to create highly reliable UI tests at great pace.</p>
+<p >RCP Testing Tool is a project for GUI testing automation of Eclipse-based applications. RCPTT is fully aware about Eclipse Platform's internals, hiding this complexity from end users and allowing QA engineers to create highly reliable UI tests at great pace.</p>
 
 
 <section class="highlight key-features background-grey" style="margin:30px 0">