diff --git a/src/testinputs/com/puppycrawl/tools/checkstyle/filters/InputSuppressWarningsFilter.java b/src/testinputs/com/puppycrawl/tools/checkstyle/filters/InputSuppressWarningsFilter.java
index 5341f584a..a1e907459 100644
--- a/src/testinputs/com/puppycrawl/tools/checkstyle/filters/InputSuppressWarningsFilter.java
+++ b/src/testinputs/com/puppycrawl/tools/checkstyle/filters/InputSuppressWarningsFilter.java
@@ -6,7 +6,7 @@ package com.puppycrawl.tools.checkstyle.filters;
 
 /**
  * Test input for using comments to suppress errors.
- * 
+ *
  * @author Trevor Robinson
  **/
 @SuppressWarnings("foo") // coverage: no following AST
diff --git a/src/xdocs/config.xml b/src/xdocs/config.xml
index 6e4d0a703..aff5a512a 100755
--- a/src/xdocs/config.xml
+++ b/src/xdocs/config.xml
@@ -1096,23 +1096,27 @@
 
       <subsection name="SuppressWarningsFilter">
         <h4>SuppressWarningsFilter</h4>
-        <p>Filter <code>SuppressWarningsFilter</code> uses annotations to suppress audit events</p>
+        <p>
+          Filter <code>SuppressWarningsFilter</code> uses annotations to
+          suppress audit events.
+        </p>
 
         <p>
           Rationale: Same as for
           <code>SuppressionCommentFilter</code>. In the contrary to it
-          here we do not used comments but the builtin syntax of
-          <code>@SuppressWarnings</code>. This can be perceived as more
-          elegant solution than using comments. Also this maybe
-          supported but various IDE.
+          here, comments are not used comments but the builtin syntax of
+          <code>@SuppressWarnings</code>. This can be perceived as a
+          more elegant solution than using comments. Also this approach
+          maybe supported by various IDE.
         </p>
         <p>
-          Usage: This filter only works in conjunction withe a
-          <code>SuppressWarningsHolder</code> since that check find the
-          annotations in all *.java files and make them available for
-          the filter. Because of that a configuration that includes this
-          filter must also include <code>SuppressWarningsHolder</code>
-          as a child module of the <code>TreeWalker</code>.
+          Usage: This filter only works in conjunction with a
+          <code>SuppressWarningsHolder</code>, since that check finds
+          the annotations in the Java files and makes them available for
+          the filter. Because of that, a configuration that includes
+          this filter must also include
+          <code>SuppressWarningsHolder</code> as a child module of the
+          <code>TreeWalker</code>.
         </p>
 
         <h5>SuppressWarningsFilter Properties</h5>
diff --git a/src/xdocs/config_annotation.xml b/src/xdocs/config_annotation.xml
index 0bfd5ffb8..ab2c81a2e 100644
--- a/src/xdocs/config_annotation.xml
+++ b/src/xdocs/config_annotation.xml
@@ -341,17 +341,15 @@
     <section name="SuppressWarningsHolder">
       <subsection name="Description">
         <p>
-          Maintains a set of check suppressions from SuppressWarnings
-          annotations. It allows to prevent Stylecheck from reporting
-          errors from parts of code that were annotated with
-          <code>SuppressWarnings</code> and using name of the check to
-          be excluded. You can also define aliases for check names that
-          need to be suppressed.
+          Maintains a set of check suppressions from
+          <code>@SuppressWarnings</code> annotations. It allows to
+          prevent Checkstyle from reporting errors from parts of code
+          that were annotated with <code>@SuppressWarnings</code> and
+          using name of the check to be excluded. You can also define
+          aliases for check names that need to be suppressed.
          </p>
       </subsection>
 
-
-
       <subsection name="Properties">
         <table>
           <tr>