Fixed "Trailing whitespace" and "Line too long" warning by doc8

Author: chinyeungli

docs/source/aboutcode-toolkit/reference.rst

@@ -87,7 +87,7 @@ Options
 
         Users can use the following in the template to get the vartext:
         {{ variables['title'] }}
-        {{ variables['header'] }} 
+        {{ variables['header'] }}
 
     --verbose
 
@@ -98,9 +98,12 @@ Options
 The following data are passed to jinja2 and, therefore, can be used for a custom template:
  * about object: the about objects
  * common_licenses: a common license keys list in licenses.py
- * license_key_and_context: a dictionary list with license_key as a key and license text as the value
- * license_file_name_and_key: a dictionary list with license file name as a key and license key as the value
- * license_key_to_license_name: a dictionary list with license key as a key and license file name as the value
+ * license_key_and_context: a dictionary list with license_key as a key
+   and license text as the value
+ * license_file_name_and_key: a dictionary list with license file name as
+   a key and license key as the value
+ * license_key_to_license_name: a dictionary list with license key as a key
+   and license file name as the value
 
 
 check
@@ -261,7 +264,7 @@ Options
     The above command will only inventory the ABOUT files which have the "license_expression: gpl-2.0"
 
     -f, --format [json|csv]
- 
+
         Set OUTPUT file format.  [default: csv]
 
     $ about inventory -f json LOCATION OUTPUT
@@ -299,7 +302,7 @@ The multiple licenses support format for ABOUT files are by "grouping" with the
             file: mit.LICENSE
 
 
-Multiple license_file support 
+Multiple license_file support
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 To support multiple license file for a license, the correct format is to separate by comma
 
@@ -348,7 +351,8 @@ transform
 
 Purpose
 ^^^^^^^
-Transform the CSV file at LOCATION by applying renamings, filters and checks and write a new CSV to OUTPUT.
+Transform the CSV file at LOCATION by applying renamings, filters and checks
+and write a new CSV to OUTPUT.
 
 Options
 ^^^^^^^
@@ -365,7 +369,7 @@ Options
 
         Show configuration file format help and exit.
         This option will print out examples of the the YAML configuration file.
-        
+
         Keys configuration are: `field_renamings`, `required_fields` and `field_filters`
 
     $ about transform --help-format

docs/source/aboutcode-toolkit/specification.rst

@@ -106,8 +106,8 @@ A field name can contain only these US-ASCII characters:
 - Field names are not case sensitive. For example, "HOMEPAGE_URL" and "HomePage_url"
   represent the same field name.
 
-- A field name must start at the beginning of a new line. No spaces is allowed in the 
-  field name. It can be followed by one or more spaces that must be ignored. 
+- A field name must start at the beginning of a new line. No spaces is allowed in the
+  field name. It can be followed by one or more spaces that must be ignored.
   These spaces are commonly used to improve the readability of an ABOUT file.
 
 
@@ -158,7 +158,7 @@ name syntax or invalid content. Tools should report additional validation error
 details. The validation process should check that each field name is
 syntactically correct and that fields contain correct values according to its
 concise, common sense definition in this specification. For certain fields,
-additional and specific validations are relevant such as URL validation, 
+additional and specific validations are relevant such as URL validation,
 path resolution and verification, and so forth. Tools should
 report a warning for present fields that do not have any value.
 
@@ -230,7 +230,7 @@ Referencing the file or directory documented by an ABOUT file
 
 An ABOUT file documents one file or directory. The mandatory "about_resource"
 field reference the documented file or directory. The value of the
-"about_resource" field is the name or path of the referenced file or directory. 
+"about_resource" field is the name or path of the referenced file or directory.
 
 A tool processing an ABOUT file must report an error if this field is missing.
 
@@ -404,15 +404,15 @@ These fields support checksums (such as SHA1 and MD5)commonly provided with
 downloaded archives to verify their integrity. A tool can optionally use these
 to verify the integrity of a file documented by an ABOUT file.
 
-- checksum_md5: MD5 for the file documented by this ABOUT file in the 
+- checksum_md5: MD5 for the file documented by this ABOUT file in the
   "about_resource" field.
 
 - checksum_sha1: SHA1 for the file documented by this ABOUT file in the
   "about_resource" field.
 
 - checksum_sha256: SHA256 for the file documented by this ABOUT file in the
   "about_resource" field.
-  
+
 Some examples::
 
       checksum_md5: f30b9c173b1f19cf42ffa44f78e4b96c