Add "Scan Package" pipeline in the documentation along some cleanups

Signed-off-by: Thomas Druez <[email protected]>

Author: tdruez

docs/run-docker.rst

@@ -27,8 +27,8 @@ create an environment file, and build the Docker image::
     docker-compose build
 
 .. note::
-    The image will need to be re-build when the ScanCode.io app source code if
-    modified or updated.
+    The image will need to be re-build when the ScanCode.io source code is modified or
+    updated.
 
 Run the Image
 -------------

docs/scanpipe-output.rst

@@ -1,7 +1,7 @@
 .. _scanpipe_output:
 
-Output
-======
+Output Files
+============
 
 Whether you use the command line or the web application to run your
 scans, the generated results are available for review or export in

docs/scanpipe-pipelines.rst

@@ -27,3 +27,8 @@ Scan Codebase
 -------------
 .. autoclass:: scanpipe.pipelines.scan_codebase.ScanCodebase()
     :members:
+
+Scan Package
+------------
+.. autoclass:: scanpipe.pipelines.scan_package.ScanPackage()
+    :members:

docs/tutorial-1.rst

@@ -1,7 +1,7 @@
 .. _tutorial_1:
 
-Docker Image Analysis (command line)
-====================================
+Analyze Docker Image (command line)
+===================================
 
 In this tutorial, you will learn by example how to use ScanCode.io to analyze
 a test Docker image by following the given steps and, along the way,

docs/tutorial-2.rst

@@ -1,7 +1,8 @@
 .. _tutorial_2:
 
-Scan Codebase (command line)
-============================
+Analyze Codebase (command line)
+===============================
+
 The focus of this tutorial is to guide you through scanning a codebase package
 using ScanCode.io.