fix up test with doc8_style

Signed-off-by: swastik <swastkk@gmail.com>

Author: swastkk

docs/source/archive/gsoc/reports/2024/scancode_toolkit_swastkk.rst

@@ -6,7 +6,8 @@ Compute summary for all detected packages.
 | **Organization:** `AboutCode <https://aboutcode.org>`_
 | **Project:** `Scancode Toolkit <https://github.com/aboutcode-org/scancode-toolkit>`_
 | **Mentee:** `Swastik Sharma (swastkk) <https://github.com/swastkk>`_
-| **Mentors:** `Philippe Ombredanne`_, `Ayan Sinha Mahapatra`_, `Avishrant Sharma`_, `Jonathan Yang`_, `Jay Kumar`_
+| **Mentors:** `Philippe Ombredanne`_, `Ayan Sinha Mahapatra`_, `Avishrant Sharma`_,
+                `Jonathan Yang`_, `Jay Kumar`_
 
 Overview
 --------
@@ -21,36 +22,32 @@ Implementation
 --------------
 
 - **Added a new command-line option called** ``--package-summary``:
-  
   - Provides a package-level summary within a single codebase.
   - Involves the ``license_clarity_score`` calculation.
-  - Populates package attributes like ``copyright``, ``holder``, 
+  - Populates package attributes like ``copyright``, ``holder``,
     ``other_license_expression``, ``notice_text``.
 
 - **The** ``--package-summary`` **option must be used with:**
-  
-  - ``--classify``: Helps ScanCode further classify scanned files/directories into 
+  - ``--classify``: Helps ScanCode further classify scanned files/directories into
     categories like ``legal``, ``readme``, ``top-level``, ``manifest``.
-  - ``--package`` or ``-p``: Detects various package manifests, lockfiles, and 
-    package-like data, assembles codebase-level packages and dependencies, and tags 
+  - ``--package`` or ``-p``: Detects various package manifests, lockfiles, and
+    package-like data, assembles codebase-level packages and dependencies, and tags
     files as part of the packages.
 
 - **Benefits of the change:**
-  
-  - Allows users to obtain a more refined summary for each individual package in 
+  - Allows users to obtain a more refined summary for each individual package in
     a codebase.
-  - Improves package assembly for various package ecosystems like npm, python-whl, 
-    rust, rubygems, etc. Since the package-level summary heavily depends on the package assembly,
-    there were several scenarios where key files for top-level packages were not properly tagged.
-    To address this, a method called ``get_top_level_resources`` was implemented. This method retrieves 
-    the resources for top-level packages, which helps in correctly tagging the key files.
+  - Improves package assembly for various package ecosystems like npm, python-whl,
+    rust, rubygems, etc. Since the package-level summary heavily depends on the
+    package assembly, there were several scenarios where key files for top-level
+    packages were not properly tagged. To address this, a method called
+    ``get_top_level_resources`` was implemented. This method retrieves the resources
+    for top-level packages, which helps in correctly tagging the key files.
 
 - **Testing:**
-  
   - All changes are tested through multiple full scan tests.
   - Validated both correct behavior and error handling.
 
-
 Linked Pull Requests
 --------------------
 
@@ -68,7 +65,7 @@ Linked Pull Requests
 Related Issues
 --------------
 
-.. list-table:: 
+.. list-table::
    :widths: 10 60 30
    :header-rows: 1
 
@@ -135,7 +132,8 @@ I would like to thank my mentors:
 - `Jonathan Yang`_
 
 Weekly Status calls were greatly helpful and those special 1:1 calls with
-`Ayan Sinha Mahapatra`_ and `Philippe Ombredanne`_ were so amazing. Thank you for your time and your patience!
+`Ayan Sinha Mahapatra`_ and `Philippe Ombredanne`_ were so amazing.
+Thank you for your time and your patience!
 
 
 .. _Philippe Ombredanne: https://github.com/pombredanne

docs/source/contributing.rst

@@ -2,13 +2,17 @@
 Contributing to AboutCode
 #########################
 
-We welcome you and your interest in contributing to open source software! AboutCode is always looking for enthusiatic contributors and we are happy to help with any questions or comments. Here a few resources to get started:
+We welcome you and your interest in contributing to open source software! AboutCode
+is always looking for enthusiatic contributors and we are happy to help with any questions
+or comments. Here a few resources to get started:
 
 1) Take a look through our public repos here: https://github.com/aboutcode-org/
     * Find one you are interested in and check out its open **Issues**
-2) If you have specific questions browse through our documentation here: https://aboutcode.readthedocs.io/en/latest/
+2) If you have specific questions browse through our documentation here:
+    https://aboutcode.readthedocs.io/en/latest/
     * Depending on the project, there may be a separate ReadTheDocs website
-    * Not finding what you were looking for or still have questions? Open an issue on the relevant repository or ask directly via Gitter or Slack
+    * Not finding what you were looking for or still have questions?
+    Open an issue on the relevant repository or ask directly via Gitter or Slack
 
 You can always interact with the AboutCode community on Gitter_ and Slack_.