Check Sphinx syntax and formatting and correct as needed

Signed-off-by: John M. Horan <[email protected]>

Author: johnmhoran

docs/source/importers_link.rst

@@ -3,4 +3,4 @@
 Importers
 =========
 
-.. include:: ../../SOURCES.rst
+.. include:: ../../SOURCES.rst

docs/source/reference_importer_overview.rst

@@ -3,8 +3,8 @@
 Importer Overview
 ==================
 
-Importers are responsible for scraping vulnerability data such as vulnerabilities and their fixes and
-for storing the scraped information in a structured fashion. The structured data created by the
+Importers are responsible for scraping vulnerability data such as vulnerabilities and their fixes
+and for storing the scraped information in a structured fashion. The structured data created by the
 importer then provides input to an improver (see :ref:`improver-overview`), which is responsible
 for creating a relational model for vulnerabilities, affected packages and fixed packages.
 

docs/source/tutorial_add_new_importer.rst

@@ -90,8 +90,8 @@ implementing the unimplemented methods.
 Specify the Importer License
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Importers scrape data off the internet.  In order to make sure the data is useable, a license must be
-provided.
+Importers scrape data off the internet.  In order to make sure the data is useable, a license
+must be provided.
 Populate the ``spdx_license_expression`` with the appropriate value.
 The SPDX license identifiers can be found at https://spdx.org/licenses/.
 
@@ -102,10 +102,10 @@ The SPDX license identifiers can be found at https://spdx.org/licenses/.
 Implement the ``advisory_data`` Method
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The ``advisory_data`` method scrapes the advisories from the data source this importer is targeted
-at.
-It is required to return an *Iterable of AdvisoryData objects*, and thus it is a good idea to yield from
-this method after creating each AdvisoryData object.
+The ``advisory_data`` method scrapes the advisories from the data source this importer is
+targeted at.
+It is required to return an *Iterable of AdvisoryData objects*, and thus it is a good idea to yield
+from this method after creating each AdvisoryData object.
 
 At this point, an example importer will look like this:
 

docs/source/tutorial_add_new_improver.rst

@@ -68,10 +68,9 @@ Writing an improver
 Locate the Source File
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
-If the improver will be working on data imported by a specific importer, it  will be located in the same
-file at :file:`vulnerabilites/importers/{importer-name.py}`.
-Otherwise, if it is a generic improver, create a new file
-:file:`vulnerabilites/improvers/{improver-name.py}`.
+If the improver will be working on data imported by a specific importer, it  will be located in
+the same file at :file:`vulnerabilites/importers/{importer-name.py}`.  Otherwise, if it is a
+generic improver, create a new file :file:`vulnerabilites/improvers/{improver-name.py}`.
 
 Explore Package Managers (Optional)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -107,10 +106,10 @@ the ``Advisory`` QuerySet returned by the ``interesting_advisories`` property.
 It is expected to return an iterable of ``Inference`` objects for the given ``AdvisoryData``. To
 avoid storing a lot of Inferences in memory, it is preferable to yield from this method.
 
-A very simple Improver that processes all Advisories to create the minimal relationships that can be
-obtained by existing data can be found at :file:`vulnerabilites/improvers/default.py`, which is an
-example of a generic improver.  For a more sophisticated and targeted example, you can look at an already
-implemented improver (e.g., :file:`vulnerabilites/importers/nginx.py`).
+A very simple Improver that processes all Advisories to create the minimal relationships that can
+be obtained by existing data can be found at :file:`vulnerabilites/improvers/default.py`, which is
+an example of a generic improver.  For a more sophisticated and targeted example, you can look
+at an already implemented improver (e.g., :file:`vulnerabilites/importers/nginx.py`).
 
 Improvers are not limited to improving discrete versions and may also improve ``aliases``.
 One such example, improving the importer written in the :ref:`importer tutorial