Fix a typo in the docs and fix the CI

Signed-off-by: ziad hany <ziadhany2016@gmail.com>

Author: ziadhany

docs/source/advisory-package-curation.rst

@@ -3,7 +3,7 @@
 Advisory Package Curation
 =========================
 
-Follow these steps to curate the packages associated with an advisory:
+Follow these steps to curate the package versions associated with vulnerability advisories:
 
 .. image:: images/advisory-package-curation.png
 
@@ -23,7 +23,7 @@ Follow these steps to curate the packages associated with an advisory:
 
       Click **Select value** multiple times to cycle through the available statuses (**AFFECTED**, **FIXED**, and **UNAFFECTED**).
 
-      Alternatively, if one of the suggested advisories is correct, click **Pick this** to automatically apply the recommended package version information.
+if one of the suggested advisories is correct, click **Pick this** to automatically apply the advisory package versions status.
 
    .. image:: images/package_pick_this.png
 

docs/source/advisory-severity-curation.rst

@@ -3,7 +3,7 @@
 Advisory Severity Curation
 ==========================
 
-Follow these steps to curate the severity for advisories:
+Follow these steps to curate the severity associated with vulnerability advisories:
 
 .. image:: images/advisory-severity-curation.png
 
@@ -21,4 +21,4 @@ Follow these steps to curate the severity for advisories:
 
 4. Once you have curated all advisories, click **Submit**
 
-   .. image:: images/severity_submit-button.png
+   .. image:: images/severity_submit.png

docs/source/advisory-todos.rst

@@ -22,7 +22,7 @@ Our advisory curation process supports enriching and validating the following vu
   - *(Not currently supported)* Advisories missing fixed package versions.
   - *(Not currently supported)* Advisories missing both affected and fixed package versions.
 
-* **Severity Curation**: Advisories with conflicting CVSS vectors (CVSSv3, CVSSv3.1, CVSSv4, ...) . See :ref:`advisory-severity-curation`.
+* **Severity Curation**: Advisories with conflicting CVSS vectors (CVSSv3, CVSSv3.1, CVSSv4) . See :ref:`advisory-severity-curation`.
 * **Weakness Curation**: Advisories with conflicting Common Weakness Enumeration (CWE) identifiers. See :ref:`advisory-weakness-curation`.
 * **Summary Curation**: *(Not currently supported).*
 
@@ -41,6 +41,6 @@ Accessing the Advisory To-Dos Queue
 
    .. image:: images/continue-button.png
 
-4. Search for advisories by **alias**, or filter the list by **Resolved** status or **issue type**.
+4. Search for advisories by **Alias**, or filter the list by **Resolved status** or **Issue type**.
 
    .. image:: images/advisory-to-do-dashbaord.png

docs/source/advisory-weakness-curation.rst

@@ -3,13 +3,13 @@
 Advisory Weakness Curation
 ===========================
 
-Follow these steps to curate the `Common Weakness Enumeration (CWE) <https://cwe.mitre.org/>`_ associated with an advisories:
+Follow these steps to curate the `Common Weakness Enumeration (CWE) <https://cwe.mitre.org/>`_ associated with vulnerability advisories:
 
 .. image:: images/advisory-weakness-curation.png
 
 1. Click the Alias you want to curate, for example, ``CVE-2022-24512``.
 
-2. Select the appropriate CWE status (APPLICABLE or NOT APPLICABLE) for the selected CWE ID.
+2. Select the appropriate CWE status (``APPLICABLE`` or ``NOT APPLICABLE``) for the selected CWE ID.
 
    .. image:: images/weakness_select_value.png
 

docs/source/images/pacakge_submit.png docs/source/images/package_submit.pngdocs/source/images/pacakge_submit.png renamed to docs/source/images/package_submit.png

@@ -59,7 +59,7 @@ vulnerabilities with comprehensive information from upstream and downstream publ
 sources including packages affected by a vulnerability advisories and packages that fix a
 vulnerability advisory.
 
-There is a `public vulnerableCode database <https://public.vulnerablecode.io/>`_
+There is a `Public VulnerableCode Database <https://public.vulnerablecode.io/>`_
 and the project also provides the tools to build your own instance of the database.
 
 Documentation overview
@@ -122,7 +122,7 @@ Consult the reference to understand VulnerableCode concepts.
 Advisory Curation
 ~~~~~~~~~~~~~~~~~
 
-Learn how to review and enrich vulnerability advisory data.
+Learn how to review and curate vulnerability advisories.
 
 - :ref:`advisory_todos`
 

…source/images/severity_submit-button.png docs/source/images/severity_submit.pngdocs/source/images/severity_submit-button.png renamed to docs/source/images/severity_submit.png docs/source/images/severity_submit-button.png renamed to docs/source/images/severity_submit.png

@@ -93,8 +93,8 @@ a CPE. This makes answers to questions such as "Is package *foo* vulnerable
 to vulnerability *bar*?" more accurate and easier to interpret.
 
 The primary access to VulnerableCode data is through a REST API, but there
-is also a Web UI for searching and browsing vulnerabilities by package
-or by vulnerability. For the initial releases both access modes are
+is also a Web UI for searching and browsing vulnerability advisories by package.
+For the initial releases both access modes are
 read-only, but our longer-term goal is to enable community curation of
 the data including addition of new packages and vulnerabilities, and
 reviewing and updating their relationships.