Fixes Spelling Errors

This commits fixes some spelling mistakes and Adds guide to use GNU Aspell to do the same.

Signed-off-by: Ayan Sinha Mahapatra <ayansmahapatra@gmail.com>

Author: AyanSinhaMahapatra

docs/source/scancode-toolkit/cli-reference/index.rst

@@ -1,4 +1,4 @@
-**Command Line Interface Referance**
+**Command Line Interface Reference**
 ====================================
 
 .. toctree::
@@ -10,7 +10,7 @@
    simple-examples
 
 ..
-   [ToAdd]
+   [To-Add]
    core-options
    output-format
    output-filters-and-control

docs/source/scancode-toolkit/contribute/contrib_dev.rst

@@ -27,7 +27,7 @@ either using a checkout or a download, without needing a compiler and toolchain
 The corresponding source code for the pre-built binaries are store in a separate repository at
 https://github.com/nexB/scancode-thirdparty-src.
 
-We store bundled thirdparty components and libraries in the ``thirdparty`` directory. Python
+We store bundled third-party components and libraries in the ``thirdparty`` directory. Python
 libraries are stored as wheels, eventually pre-built if the corresponding wheel is not available
 in the Pypi repository. Some of these components may be advanced builds with bug fixes or advanced
 patches.

docs/source/scancode-toolkit/contribute/contrib_doc.rst

@@ -1,7 +1,7 @@
 Contributing to the Documentation
 =================================
 
-Continious Integration
+Continuous Integration
 ----------------------
 
 The documentations are checked on every new commit through Travis-CI, so that common errors are
@@ -60,13 +60,13 @@ What is checked:
     - lines should not be longer than 100 characters - D001
 
         - RST exception: line with no whitespace except in the beginning
-        - RST exception: lines with http or https urls
+        - RST exception: lines with http or https URLs
         - RST exception: literal blocks
         - RST exception: rst target directives
 
     - no trailing whitespace - D002
     - no tabulation for indentation - D003
-    - no carriage returns (use unix newlines) - D004
+    - no carriage returns (use UNIX newlines) - D004
     - no newline at end of file - D005
 
 Extra Style Checks
@@ -87,7 +87,7 @@ Extra Style Checks
 
     -, for subsections
 
-    ^, for subsubsections
+    ^, for sub-subsections
 
     ", for paragraphs
 
@@ -128,6 +128,15 @@ Extra Style Checks
 
 5. Using ``:ref:`` only when necessary
 
-    Use ``:ref:`` to create internal links only when needed, i.e. it is referanced somewhere.
-    Do not create referances for all the sections and then only referance some of them, because
-    this created unnecessary referances. This also generates ERROR in ``restructuredtext-lint``.
+    Use ``:ref:`` to create internal links only when needed, i.e. it is referenced somewhere.
+    Do not create references for all the sections and then only reference some of them, because
+    this created unnecessary references. This also generates ERROR in ``restructuredtext-lint``.
+
+6. Spelling
+
+    You should check for spelling errors before you push changes. `Aspell <http://aspell.net/>`_
+    is a GNU project Command Line tool you can use for this purpose. Download and install Aspell,
+    then execute ``aspell check <file-name>`` for all the files changed. Be careful about not
+    changing commands or other stuff as Aspell gives prompts for a lot of them. Also delete the
+    temporary ``.bak`` files generated. Refer the `manual <http://aspell.net/man-html/>`_ for more
+    information on how to use.

docs/source/scancode-toolkit/contribute/cut_new_release.rst

@@ -28,7 +28,7 @@ How to cut a new release:
 - upload the release archives created in the ``dist/`` directory to the GitHub release page.
 
 - save the release as a draft. Use the previous release notes to create notes in the same style.
-  Ensure that the link to thirdparty source code is present.
+  Ensure that the link to third-party source code is present.
 
 - test the downloads.
 

docs/source/scancode-toolkit/contribute/roadmap.rst

@@ -48,7 +48,7 @@ Copyrights
 - |white_check_mark| speed up copyright detection
 - |white_check_mark| improved detected lines range
 - |white_check_mark| streamline grammar of copyright parser
-- |white_check_mark| normalize holders and authors for summarization
+- |white_check_mark| normalize holders and authors for summarizing
 - |white_check_mark| normalize and streamline results data format
 
 Core features
@@ -121,7 +121,7 @@ Other work in progress
 ----------------------
 
 - ScanCode server: Spawned as its own project: https://github.com/nexB/scancode-server. Will
-  include Integration / webhooks for Github, Bitbucket.
+  include Integration / webhooks for GitHub, Bitbucket.
 - VulnerableCode: NVD and CVE lookups: Spawned as its own project: https://github.com/nexB/vulnerablecode
 - ScanCode Workbench: desktop app for scan review: Spawned as its own project:
   https://github.com/nexB/scancode-workbench
@@ -158,8 +158,8 @@ Core scans
 - |white_check_mark| file information (size, type, etc.)
 - |white_check_mark| URLs, emails, authors
 
-Ouputs and UI
-^^^^^^^^^^^^^
+Outputs and UI
+^^^^^^^^^^^^^^
 - |white_check_mark| JSON compact and pretty
 - |white_check_mark| plain HTML tables, also usable in a spreadsheet
 - |white_check_mark| fancy HTML 'app' with a file tree navigation, and scan results filtering,

docs/source/scancode-toolkit/explanations/index.rst

@@ -7,7 +7,7 @@
    overview
 
 ..
-   [ToAdd]
+   [To-Add]
    file_collect_classify
    extract
    rules_engine

docs/source/scancode-toolkit/index.rst

@@ -1,4 +1,4 @@
-**Scancode-Toolkit Documentation**
+**ScanCode-Toolkit Documentation**
 ==================================
 
 .. toctree::

docs/source/scancode-toolkit/misc/support.rst

@@ -1,6 +1,6 @@
 Support
 =======
 
-Post questions and bugs as Github tickets at: https://github.com/nexB/scancode-toolkit/issues
+Post questions and bugs as GitHub tickets at: https://github.com/nexB/scancode-toolkit/issues
 
 Ask question on StackOverflow using the [scancode] tag.