Fix failing test with scripts

Signed-off-by: swastik <[email protected]>

Author: swastkk

docs/source/archive/gsoc-toc.rst

@@ -15,7 +15,6 @@ GSoC 2024
    :maxdepth: 2
 
    gsoc/reports/2024/scancode_toolkit_swastkk
-   
 
 GSoC 2022
 ---------

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

@@ -11,7 +11,7 @@ Compute summary for all detected packages.
 Overview
 --------
 
-Previously, we computed the summary at the codebase level, which included elements like the 
+Previously, we computed the summary at the codebase level, which included elements like the
 `license_clarity_score`, `declared_holder`, `other_license_expressions`, and more.
 This project aims to improve scanning accuracy by computing summaries and license clarity scores for
 each package and its files, rather than for the entire scan. This involves enhancing package models
@@ -22,16 +22,18 @@ Implementation
 
 All the work I did is contained in `this single PR <https://github.com/aboutcode-org/scancode-toolkit/pull/3792>`_.
 I added a new command-line option called ``--package-summary`` that users can employ to obtain
-a package-level summary within a single codebase. The package level summary involves the 
+a package-level summary within a single codebase. The package level summary involves the
 ``license_clarity_score`` calculation and population of package attributes like ``copyright``,
-``holder``, ``other_license_expression``, ``notice_text``. This option must be called with ``--classify``
-option that helps ScanCode further classify scanned files/directories, to determine whether
-they fall in these categories `legal`, `readme`, `top-level`, `manifest` & ``--package`` or ``-p`` option
-detects various package manifests, lockfiles and package-like data and then assembles codebase level packages
-and dependencies from these package data detected at files. Also tags files if they are part of the packages.
+``holder``, ``other_license_expression``, ``notice_text``. This option must be called
+with ``--classify`` option that helps ScanCode further classify scanned files/directories,
+to determine whether they fall in these categories `legal`, `readme`, `top-level`, `manifest`
+& ``--package`` or ``-p`` option detects various package manifests, lockfiles and
+package-like data and then assembles codebase level packages and dependencies from
+these package data detected at files. Also tags files if they are part of the packages.
 
-This change allows users to get the more refined summary for each individual package that is present in a codebase.
-Also this feature improves the package assembly for various package ecosystems like npm, python-whl, rust, rubygems etc.
+This change allows users to get the more refined summary for each individual package
+that is present in a codebase. Also this feature improves the package assembly for
+various package ecosystems like npm, python-whl, rust, rubygems etc.
 
 
 Finally, all these changes are tested through multiple unit tests validating both correct
@@ -63,5 +65,5 @@ I would like to thank my mentors
 - `@35C4n0r <https://github.com/35C4n0r>`_
 - `@jono-yang <https://github.com/JonoYang>`_
 
-Weekly calls were greatly helpful and those special 1:1 call with `@AyanSinhaMahapatra` and `@pombredanne` 
-were so amazing. Thank you for your time and your patience!
+Weekly calls were greatly helpful and those special 1:1 call with
+`@AyanSinhaMahapatra` and `@pombredanne` were so amazing. Thank you for your time and your patience!