Bug 1493500 - Remove all trailing whitespaces from all files

10 files changed, 18 insertions, 18 deletions

diff --git a/docs/en/rst/administering/extensions.rst b/docs/en/rst/administering/extensions.rst
index 2c54b8463..62c7ec03d 100644
--- a/docs/en/rst/administering/extensions.rst
+++ b/docs/en/rst/administering/extensions.rst
@@ -14,5 +14,5 @@ last time you compiled the documentation):
 .. toctree::
    :maxdepth: 1
    :glob:
-   
+
    ../extensions/*/index-admin
diff --git a/docs/en/rst/administering/keywords.rst b/docs/en/rst/administering/keywords.rst
index 245bcbe4c..2582c29e4 100644
--- a/docs/en/rst/administering/keywords.rst
+++ b/docs/en/rst/administering/keywords.rst
@@ -7,7 +7,7 @@ The administrator can define keywords which can be used to tag and
 categorise bugs. For example, the keyword "regression" is commonly used.
 A company might have a policy stating all regressions
 must be fixed by the next release—this keyword can make tracking those
-bugs much easier. Keywords are global, rather than per product. 
+bugs much easier. Keywords are global, rather than per product.
 
 Keywords can be created, edited, or deleted by clicking the "Keywords"
 link in the admin page. There are two fields for each keyword—the keyword
diff --git a/docs/en/rst/api/core/v1/bug.rst b/docs/en/rst/api/core/v1/bug.rst
index 53f637a67..c6b7be084 100644
--- a/docs/en/rst/api/core/v1/bug.rst
+++ b/docs/en/rst/api/core/v1/bug.rst
@@ -479,9 +479,9 @@ limit             int       Limit the number of results returned. If the limit
                             set by the administrator, then the maximum limit will
                             be used instead. If you set the limit equal to zero,
                             then all matching results will be returned instead.
-longdescs.count   int       The number of comments a bug has. The bug's description 
+longdescs.count   int       The number of comments a bug has. The bug's description
                             is the first comment. For example, to find bugs which someone
-                            has commented on after they have been filed, search on 
+                            has commented on after they have been filed, search on
                             ``longdescs.count`` *greater than* 1.
 offset            int       Used in conjunction with the ``limit`` argument,
                             ``offset`` defines the starting position for the
@@ -1202,4 +1202,4 @@ attachment_id  int     The ID of the attachment that was changed.
                        This only appears if the change was to an attachment,
                        otherwise ``attachment_id`` will not be present in this
                        object.
-=============  ======  ==========================================================
\ No newline at end of file
+=============  ======  ==========================================================
diff --git a/docs/en/rst/api/core/v1/bugzilla.rst b/docs/en/rst/api/core/v1/bugzilla.rst
index e43472c30..220ee5fc5 100644
--- a/docs/en/rst/api/core/v1/bugzilla.rst
+++ b/docs/en/rst/api/core/v1/bugzilla.rst
@@ -312,7 +312,7 @@ Reports the status of the job queue.
 
    GET /rest/jobqueue_status
 
-This method requires an authenticated user. 
+This method requires an authenticated user.
 
 **Response**
 
@@ -328,4 +328,4 @@ name             type     description
 ===============  =======  ====================================================
 total            integer  The total number of jobs in the job queue.
 errors           integer  The number of errors produced by jobs in the queue.
-===============  =======  ====================================================
\ No newline at end of file
+===============  =======  ====================================================
diff --git a/docs/en/rst/integrating/extensions.rst b/docs/en/rst/integrating/extensions.rst
index 50f204746..e9ae48630 100644
--- a/docs/en/rst/integrating/extensions.rst
+++ b/docs/en/rst/integrating/extensions.rst
@@ -49,7 +49,7 @@ To add new fields to a bug, you need to do the following:
 
     my $field = new Bugzilla::Field({ name => $name });
     return if $field;
- 
+
     $field = Bugzilla::Field->create({
         name        => $name,
         description => $description,
@@ -67,12 +67,12 @@ To add new fields to a bug, you need to do the following:
 
   .. code-block:: perl
 
-    BEGIN { 
-       *Bugzilla::Bug::is_foopy = \&_bug_is_foopy; 
+    BEGIN {
+       *Bugzilla::Bug::is_foopy = \&_bug_is_foopy;
     }
- 
+
     ...
- 
+
     sub _bug_is_foopy {
         return $_[0]->{'is_foopy'};
     }
diff --git a/docs/en/rst/integrating/faq.rst b/docs/en/rst/integrating/faq.rst
index 19f8b59ff..f50453df5 100644
--- a/docs/en/rst/integrating/faq.rst
+++ b/docs/en/rst/integrating/faq.rst
@@ -18,10 +18,10 @@ How do I...
 ...use a word other than 'bug' to describe bugs?
   :ref:`Edit or override <templates>` the appropriate values in the template
   :file:`template/en/default/global/variables.none.tmpl`.
-  
+
 ...call the system something other than 'Bugzilla'?
   :ref:`Edit or override <templates>` the appropriate value in the template
   :file:`template/en/default/global/variables.none.tmpl`.
-  
+
 ...alter who can change what field when?
   See :ref:`who-can-change-what`.
diff --git a/docs/en/rst/integrating/languages.rst b/docs/en/rst/integrating/languages.rst
index 4d087a721..d76a82a82 100644
--- a/docs/en/rst/integrating/languages.rst
+++ b/docs/en/rst/integrating/languages.rst
@@ -3,7 +3,7 @@ Languages
 
 Bugzilla's templates can be localized, although it's a `big job
 <https://wiki.mozilla.org/Bugzilla:L10n:Guide>`_. If you have
-a localized set of templates for your version of Bugzilla, Bugzilla can 
+a localized set of templates for your version of Bugzilla, Bugzilla can
 support multiple languages at once. In that case, Bugzilla honours the user's
 ``Accept-Language`` HTTP header when deciding which language to serve. If
 multiple languages are installed, a menu will display in the header allowing
diff --git a/docs/en/rst/integrating/skins.rst b/docs/en/rst/integrating/skins.rst
index 2cd08b4c0..92bf60dfc 100644
--- a/docs/en/rst/integrating/skins.rst
+++ b/docs/en/rst/integrating/skins.rst
@@ -11,7 +11,7 @@ are a couple more which are part of
 `bugzilla.mozilla.org <http://git.mozilla.org/?p=webtools/bmo/bugzilla.git>`_.
 However, in each
 case you may need to check that the skin supports the version of Bugzilla
-you have. 
+you have.
 
 To create a new custom skin, make a directory that contains all the same CSS
 file names as :file:`skins/standard/`, and put your directory in
diff --git a/docs/en/rst/using/extensions.rst b/docs/en/rst/using/extensions.rst
index 752b50b9a..28bae5be5 100644
--- a/docs/en/rst/using/extensions.rst
+++ b/docs/en/rst/using/extensions.rst
@@ -14,5 +14,5 @@ last time you compiled the documentation):
 .. toctree::
    :maxdepth: 1
    :glob:
-   
+
    ../extensions/*/index-user
diff --git a/docs/en/rst/using/understanding.rst b/docs/en/rst/using/understanding.rst
index c52bd2167..958d4baae 100644
--- a/docs/en/rst/using/understanding.rst
+++ b/docs/en/rst/using/understanding.rst
@@ -26,7 +26,7 @@ installation of Bugzilla.
 
 *Product and Component*:
    Bugs are divided up by Product and Component, with a Product
-   having one or more Components in it. 
+   having one or more Components in it.
 
 *Version:*
    The "Version" field usually contains the numbers or names of released