docs: restructure of howto guides for pro fix related guides

canonical · Jun 10, 2024 · 049fbd0 · 049fbd0
1 parent cf6a7ee
commit 049fbd0
Show file tree

Hide file tree

Showing 7 changed files with 19 additions and 19 deletions.
diff --git a/docs/howtoguides.rst b/docs/howtoguides.rst
@@ -46,15 +46,6 @@ How to use ``pro`` commands
 
    Enable... <howtoguides/enable_index>
 
-``pro fix``
------------
-
-.. toctree::
-   :maxdepth: 1
-
-   How to know what the `fix` command would change? <howtoguides/how_to_know_what_the_fix_command_would_change>
-   Skip fixing related USNs <howtoguides/how_to_not_fix_related_usns>
-
 ``pro refresh``
 ---------------
 
@@ -79,6 +70,14 @@ How to use ``pro`` commands
 
    Check Ubuntu Pro Client version <howtoguides/check_pro_version>
 
+Fixing CVEs and USNs
+====================
+
+.. toctree::
+   :maxdepth: 2
+
+   Resolving CVEs and USNs... <howtoguides/fix_index>
+
 Corrupted lock files
 ====================
 
@@ -104,14 +103,4 @@ Ubuntu Pro Client for Clouds
    Create a customised Cloud Ubuntu Pro image <howtoguides/create_pro_golden_image>
    Cloud Ubuntu Pro images with FIPS updates <howtoguides/create_a_fips_updates_pro_cloud_image>
 
-Fixing CVEs and USNs
-====================
-
-.. toctree::
-   :maxdepth: 1
-
-   Is my system affected by this specific CVE? <howtoguides/how_to_know_if_system_affected_by_cve>
-   How do I resolve a single CVE or USN? <howtoguides/how_to_resolve_given_cve>
-   Better visualise results when fixing multiple CVEs <howtoguides/how_to_better_visualise_fixing_multiple_cves>
-
 
diff --git a/...better_visualise_fixing_multiple_cves.rst → ...better_visualise_fixing_multiple_cves.rst b/...better_visualise_fixing_multiple_cves.rst → ...better_visualise_fixing_multiple_cves.rst
diff --git a/...how_to_know_if_system_affected_by_cve.rst → ...how_to_know_if_system_affected_by_cve.rst b/...how_to_know_if_system_affected_by_cve.rst → ...how_to_know_if_system_affected_by_cve.rst
diff --git a/...now_what_the_fix_command_would_change.rst → ...now_what_the_fix_command_would_change.rst b/...now_what_the_fix_command_would_change.rst → ...now_what_the_fix_command_would_change.rst
diff --git a/...wtoguides/how_to_not_fix_related_usns.rst → ...uides/fix_how_to_not_fix_related_usns.rst b/...wtoguides/how_to_not_fix_related_usns.rst → ...uides/fix_how_to_not_fix_related_usns.rst
diff --git a/.../howtoguides/how_to_resolve_given_cve.rst → ...toguides/fix_how_to_resolve_given_cve.rst b/.../howtoguides/how_to_resolve_given_cve.rst → ...toguides/fix_how_to_resolve_given_cve.rst
diff --git a/docs/howtoguides/fix_index.rst b/docs/howtoguides/fix_index.rst
@@ -0,0 +1,11 @@
+Resolving CVEs and USNs...
+**************************
+
+.. toctree::
+   :maxdepth: 1
+
+   Is my system affected by this specific CVE? <fix_how_to_know_if_system_affected_by_cve>
+   How do I resolve a single CVE or USN? <fix_how_to_resolve_given_cve>
+   How to know what the `fix` command would change? <fix_how_to_know_what_the_fix_command_would_change>
+   Skip fixing related USNs <fix_how_to_not_fix_related_usns>
+   Better visualise results when fixing multiple CVEs <fix_how_to_better_visualise_fixing_multiple_cves>