diff --git a/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.language.actions.xml b/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.language.actions.xml
index c3e03ab..8a787c2 100644
--- a/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.language.actions.xml
+++ b/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.language.actions.xml
@@ -291,7 +291,7 @@
     <para>
       The DYNAMICANCHORING action turns dynamic anchoring on or off
       (first parameter) and assigns the anchoring parameters penalty
-      (sceond parameter) and factor (third parameter).
+      (second parameter) and factor (third parameter).
     </para>
     <section>
       <title>
@@ -310,7 +310,7 @@
         <programlisting><![CDATA[Document{->DYNAMICANCHORING(true)};]]></programlisting>
       </para>
       <para>
-        The above example turns dynamic anchoring on.
+        The above example activates dynamic anchoring.
       </para>
     </section>
   </section>
@@ -383,11 +383,8 @@
     <para>
       This action filters the given types of annotations. They are now
       ignored by rules. For more informations on how rules work see
-      <xref linkend='ugr.tools.tm.language.inference' />
-      . Expressions are not yet supported. This action is complementary to
-      RETAINTYPE (see
-      <xref linkend='ugr.tools.tm.language.actions.retaintype' />
-      ).
+      <xref linkend='ugr.tools.tm.language.inference' />. Expressions are not yet supported. 
+      This action is related to RETAINTYPE (see <xref linkend='ugr.tools.tm.language.actions.retaintype' />).
     </para>
     <section>
       <title>
@@ -986,10 +983,8 @@
     <title>RETAINTYPE</title>
     <para>
       The RETAINTYPE action retains the given types. This means that they
-      are now not ignored by rules. This action is complementary to
-      FILTERTYPE (see
-      <xref linkend='ugr.tools.tm.language.actions.filtertype' />
-      ).
+      are now not ignored by rules. This action is related to
+      FILTERTYPE (see <xref linkend='ugr.tools.tm.language.actions.filtertype' />).
     </para>
     <section>
       <title>
@@ -1161,7 +1156,7 @@
       </para>
       <para>
         This rule removes all spaces in at the beginning and at the end of Keyword annotations and
-        thus changes the offsets of the matched annoations.
+        thus changes the offsets of the matched annotations.
       </para>
     </section>
   </section>
@@ -1172,7 +1167,7 @@
       The UNMARK action removes the annotation of the given type
       overlapping the matched annotation. There are two additional configurations: If additional
       indexes are given, then the span of the specified rule elements are applied, similar the the MARK action.
-      If instead a boolean is given as an additional argument, then all annoations of the given type are removed
+      If instead a boolean is given as an additional argument, then all annotations of the given type are removed
       that start at the macthed position.
     </para>
     <section>
diff --git a/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.overview.xml b/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.overview.xml
index 5c4080a..2d20d88 100644
--- a/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.overview.xml
+++ b/TextMarker/uima-docbook-textmarker/src/docbook/tools.textmarker.overview.xml
@@ -414,7 +414,7 @@
     </para>
 
     <para>
-      The rule element of the block definition can also refer to other annaotion types than <quote>Document</quote>. While the last example implemented something similar 
+      The rule element of the block definition can also refer to other annotation types than <quote>Document</quote>. While the last example implemented something similar 
       to an if-statement, the next example provides a show case for something similar to a for-each-statement.
     </para>
 
@@ -1019,7 +1019,7 @@
       <para>
         The Modifier Analysis Engine can be used to create an additional view <quote>modified</quote>, which contains all textual modifications and HTML highlightings that
         were specified by the executed rules. Therefore, this Analysis Engine can be applied, e.g., 
-        for anonymization where all annatotions of persons are replaced by the string <quote>Person</quote>. 
+        for anonymization where all annotations of persons are replaced by the string <quote>Person</quote>. 
         Furthermore, the content of the new view can optionally be stored in a new HTML file.
         A descriptor file for this Analysis Engine is located in the folder <quote>descriptor/utils</quote> of a TextMarker project.
       </para>