Fix docs typo and CI docs validation error

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

Author: ziadhany

docs/source/advisory-package-curation.rst

@@ -3,7 +3,8 @@
 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
 
@@ -21,16 +22,19 @@ Follow these steps to curate the packages associated with an advisory:
 
    .. note::
 
-      Click **Select value** multiple times to cycle through the available statuses (**AFFECTED**, **FIXED**, and **UNAFFECTED**).
+      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 statuses.
 
    .. image:: images/package_pick_this.png
 
-3. Click **Next item**. If the button is available, repeat steps 2–3 for each remaining package.
+3. Click **Next item**. If the button is available, repeat steps 2–3 for each
+remaining package.
 
    .. image:: images/package_next_item.png
 
 4. After reviewing all packages, click **Submit** to save and complete the package curation.
 
-   .. image:: images/package_submit.png
+   .. image:: images/package_submit.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

@@ -4,34 +4,50 @@ Advisory Todos
 ==============
 
 Overview
-----------
-The Advisory To-Dos queue contains security advisories that require manual review to improve the quality and
-accuracy of vulnerablecode data
+--------
+
+The Advisory To-Dos queue contains security advisories that require
+manual review to improve the quality and accuracy of VulnerableCode
+data.
 
 Supported Advisory Curation Types
-------------------------------------
+---------------------------------
 
-Our advisory curation process supports enriching and validating the following vulnerability advisory metadata, depending on the information available from trusted sources:
+Our advisory curation process supports enriching and validating the
+following vulnerability advisory metadata, depending on the information
+available from trusted sources:
 
 * **Package Curation**: See :ref:`advisory-package-curation`.
 
   - Advisories with conflicting **fixed** package versions.
   - Advisories with conflicting **affected** package versions.
-  - Advisories with conflicting **affected** and **fixed** package versions.
-  - *(Not currently supported)* Advisories missing affected package versions.
-  - *(Not currently supported)* Advisories missing fixed package versions.
-  - *(Not currently supported)* Advisories missing both affected and fixed package versions.
+  - Advisories with conflicting **affected** and **fixed** package
+    versions.
+  - *(Not currently supported)* Advisories missing affected package
+    versions.
+  - *(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, and CVSSv4). See
+  :ref:`advisory-severity-curation`.
+
+* **Weakness Curation**: Advisories with conflicting Common Weakness
+  Enumeration (CWE) identifiers. See
+  :ref:`advisory-weakness-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).*
 
-Each curation guide provides detailed instructions for reviewing advisories in the corresponding curation queue.
+Each curation guide provides detailed instructions for reviewing
+advisories in the corresponding curation queue.
 
 Accessing the Advisory To-Dos Queue
 -----------------------------------
 
-1. Go to https://public.vulnerablecode.io/.
+1. Go to `public.vulnerablecode.io
+   <https://public.vulnerablecode.io/>`_.
 
 2. Click **Advisory To-Dos**.
 
@@ -41,6 +57,7 @@ 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
 
@@ -19,4 +19,4 @@ Follow these steps to curate the `Common Weakness Enumeration (CWE) <https://cwe
 
 3. Click **Submit**.
 
-   .. image:: images/weakness_submit.png
+   .. image:: images/weakness_submit.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.