Remove trailing spaces

This patch removes trailing spaces from source files.

3 files changed, 11 insertions, 11 deletions

diff --git a/doc/admin/fan/dmtf.rst b/doc/admin/fan/dmtf.rst
index cb8234d..9f0f5ae 100644
--- a/doc/admin/fan/dmtf.rst
+++ b/doc/admin/fan/dmtf.rst
@@ -136,7 +136,7 @@ It inherts many methods that are not supported because underlying library does
 not offer such functionality. Controlling of fans is very hardware dependent.
 Different drivers may provide different ways and possibilities to manage
 connected fans.
-    
+
 ..
     ***************************************************************************
 
diff --git a/doc/admin/software/configuration.rst b/doc/admin/software/configuration.rst
index 028f399..bd94aec 100644
--- a/doc/admin/software/configuration.rst
+++ b/doc/admin/software/configuration.rst
@@ -3,7 +3,7 @@ Configuration
 There are various options affecting behaviour of *OpenLMI Software* provider.
 All of them can be fine-tuned using two configuration files. The main one is
 located at: ::
-    
+
     /etc/openlmi/software/software.conf
 
 The other one is a global configuration file for all providers in *OpenLMI*
@@ -78,7 +78,7 @@ Options related to the use of *YUM* API and its configuration.
 
     ``[Yum] Level`` : defaults to ``ERROR``
         Can be set to one of the following:
-        
+
             * ``CRITICAL``
             * ``ERROR``
             * ``WARNING``
@@ -135,7 +135,7 @@ logging configuration needs to be configured extra.
         This is an absolute or relative path to a file, where the logging
         will be done. Without this option set, logging of ``YumWorker`` is
         disabled (assuming the ``[YumWorkerLog] FileConfig`` option is also
-        unset). 
+        unset).
 
     ``[YumWorkerLog] Level`` : defaults to ``DEBUG``
         This has generally the same meaning as ``Level`` in previous section
diff --git a/doc/admin/software/introduction.rst b/doc/admin/software/introduction.rst
index 21cead0..4e70b29 100644
--- a/doc/admin/software/introduction.rst
+++ b/doc/admin/software/introduction.rst
@@ -77,7 +77,7 @@ Mapping of objects to *CIM* classes
 
 Repository : :ref:`LMI_SoftwareIdentityResource<LMI-SoftwareIdentityResource>`
     Is represented by ``LMI_SoftwareIdentityResource``. What distinguishes
-    particular repository from others on the same system is a 
+    particular repository from others on the same system is a
     :ref:`LMI_SoftwareIdentityResource.Name<LMI-SoftwareIdentityResource-Name>`
     key property. It's the name of repository written in square brackets in
     repository config. Not the configuration file name, not the ``name``
@@ -98,7 +98,7 @@ Installed file : :ref:`LMI_SoftwareIdentityFileCheck<LMI-SoftwareIdentityFileChe
     Is represented by ``LMI_SoftwareIdentityFileCheck``. Represents a
     verification check of particular file installed by *RPM* package. It contains
     attributes being checked, like:
-    
+
         * ``User ID``, ``Group ID``
         * ``Checksum``
         * ``Link Target``
@@ -107,15 +107,15 @@ Installed file : :ref:`LMI_SoftwareIdentityFileCheck<LMI-SoftwareIdentityFileChe
     Each is present twice. One property represents the current value of
     installed file and the other the value stored in *RPM* package, that the
     file should have. The later properties have ``Original`` suffix. So for
-    example: 
-        
+    example:
+
         * :ref:`UserID<LMI-SoftwareIdentityFileCheck-UserID>` vs
-          :ref:`UserIDOriginal<LMI-SoftwareIdentityFileCheck-UserIDOriginal>` 
+          :ref:`UserIDOriginal<LMI-SoftwareIdentityFileCheck-UserIDOriginal>`
         * :ref:`FileChecksum<LMI-SoftwareIdentityFileCheck-FileChecksum>` vs
-          :ref:`FileChecksumOriginal<LMI-SoftwareIdentityFileCheck-FileChecksumOriginal>` 
+          :ref:`FileChecksumOriginal<LMI-SoftwareIdentityFileCheck-FileChecksumOriginal>`
 
     Mentioned attributes are compared when the package verification is done.
-    Single file can also be easily checked. Either by running 
+    Single file can also be easily checked. Either by running
     :ref:`LMI_SoftwareIdentityFileCheck.Invoke()<LMI-SoftwareIdentityFileCheck-Invoke>`
     method on particular object path or by testing the
     :ref:`FailedFlags<LMI-SoftwareIdentityFileCheck-FailedFlags>` property for