Fix trailing whitespaces and trailing newlines

7 files changed, 13 insertions, 14 deletions

diff --git a/doc/backlinks.rst b/doc/backlinks.rst
index 34323e8f7..375386cd6 100644
--- a/doc/backlinks.rst
+++ b/doc/backlinks.rst
@@ -12,4 +12,3 @@ Python code:
 * SaltStack (https://github.com/saltstack)
 * CodeFactor (https://github.com/codefactor-io)
 * many more...
-
diff --git a/doc/how_tos/transform_plugins.rst b/doc/how_tos/transform_plugins.rst
index d3919fd20..de51ef229 100644
--- a/doc/how_tos/transform_plugins.rst
+++ b/doc/how_tos/transform_plugins.rst
@@ -101,7 +101,7 @@ Lets run Pylint with this plugin and see:
   amitdev$
 
 All the false positives associated with ``WarningMessage`` are now gone. This is just
-an example, any code transformation can be done by plugins. 
+an example, any code transformation can be done by plugins.
 
 See `astroid/brain`_ for real life examples of transform plugins.
 
diff --git a/doc/tutorial.rst b/doc/tutorial.rst
index 02e7444bb..8cb27bab6 100644
--- a/doc/tutorial.rst
+++ b/doc/tutorial.rst
@@ -18,7 +18,7 @@ in open source.  Whatever the motivation, your good intentions may not have the
 desired outcome if people find your code hard to use or understand.  The Python
 community has formalized some recommended programming styles to help everyone
 write code in a common, agreed-upon style that makes the most sense for shared
-code.  This style is captured in `PEP 8`_, the "Style Guide for Python Code".  
+code.  This style is captured in `PEP 8`_, the "Style Guide for Python Code".
 Pylint can be a quick and easy way of
 seeing if your code has captured the essence of `PEP 8`_ and is therefore
 ``friendly`` to other potential users.
diff --git a/doc/user_guide/index.rst b/doc/user_guide/index.rst
index 80fe2767e..e25db0f99 100644
--- a/doc/user_guide/index.rst
+++ b/doc/user_guide/index.rst
@@ -11,4 +11,4 @@ User Guide
    output
    message-control
    options
-   ide-integration
\ No newline at end of file
+   ide-integration
diff --git a/doc/whatsnew/1.6.rst b/doc/whatsnew/1.6.rst
index fe599165f..f58a24d80 100644
--- a/doc/whatsnew/1.6.rst
+++ b/doc/whatsnew/1.6.rst
@@ -25,7 +25,7 @@ New checkers
 
       for key in dictionary.keys():
           ...
-      
+
       # Can be refactored to:
       for key in dictionary:
           ...
@@ -80,7 +80,7 @@ New features
 
 
 * We added a new option, ``redefining-builtins-modules``, which is used for
-  defining the modules which can redefine builtins. 
+  defining the modules which can redefine builtins.
   *pylint* will emit an error when a builtin is redefined, such as defining
   a variable called ``next``. But in some cases, the builtins can be
   redefined in the case they are imported from other places, different
@@ -102,7 +102,7 @@ Bug fixes
 * Fixed a bug where the top name of a qualified import was detected as an unused variable.
 
 * We don't warn about ``invalid-sequence-index`` if the indexed object has unknown
-  base classes, that Pylint cannot deduce.  
+  base classes, that Pylint cannot deduce.
 
 
 
diff --git a/doc/whatsnew/1.8.rst b/doc/whatsnew/1.8.rst
index 884d16404..7e84a8846 100644
--- a/doc/whatsnew/1.8.rst
+++ b/doc/whatsnew/1.8.rst
@@ -52,7 +52,7 @@ New checkers
 
      # Case1: a=0, b=2, args=(4,5)
      foo(0,2,4,5) # 0 2 (4,5) ==> Observed values are same as expected values
-     
+
      # Case2: a=0, b=<default_value>, args=(4,5)
      foo(0,4,5) # 0 4 (5,) ==> args list got modified as well as the observed value of b
 
@@ -253,7 +253,7 @@ New checkers
         elif arg < 20:
             return
 
-  According to PEP8_, if any return statement returns an expression, 
+  According to PEP8_, if any return statement returns an expression,
   any return statements where no value is returned should explicitly state this as return None,
   and an explicit return statement should be present at the end of the function (if reachable).
   Thus, the previous function should be written:
@@ -340,7 +340,7 @@ Other Changes
 
 * ``missing-param-doc`` and ``missing-type-doc`` are no longer emitted when
   ``Args`` and ``Keyword Args`` are mixed in Google docstring.
-    
+
 * Fix of false positive ``useless-super-delegation`` message when
   parameters default values are different from those used in the base class.
 
@@ -360,9 +360,9 @@ Other Changes
 
 * Fix the ignored ``pylint disable=fixme`` directives for comments following
   the last statement in a file.
-   
+
 * Fix ``line-too-long`` message deactivated by wrong disable directive.
-  The directive ``disable=fixme`` doesn't deactivate anymore the emission 
+  The directive ``disable=fixme`` doesn't deactivate anymore the emission
   of ``line-too-long`` message for long commented lines.
 
 * If the rcfile specified on the command line doesn't exist, then an
@@ -371,4 +371,4 @@ Other Changes
 * Fix the wrong scope of ``disable=`` directive after a commented line.
   For example when a ``disable=line-too-long`` directive is at the end of a
   long commented line, it no longer disables the emission of ``line-too-long``
-  message for lines that follow. 
+  message for lines that follow.
diff --git a/doc/whatsnew/2.4.rst b/doc/whatsnew/2.4.rst
index 0dc289785..961a0b2d0 100644
--- a/doc/whatsnew/2.4.rst
+++ b/doc/whatsnew/2.4.rst
@@ -130,7 +130,7 @@ New checkers
 Other Changes
 =============
 
-* Don't emit ``protected-access`` when a single underscore prefixed attribute is used 
+* Don't emit ``protected-access`` when a single underscore prefixed attribute is used
   inside a special method
 
   Close #1802