diff --git a/docs/howtoguides.rst b/docs/howtoguides.rst
index 33c4f890bd..23395d2904 100644
--- 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/docs/howtoguides/how_to_better_visualise_fixing_multiple_cves.rst b/docs/howtoguides/fix_how_to_better_visualise_fixing_multiple_cves.rst
similarity index 100%
rename from docs/howtoguides/how_to_better_visualise_fixing_multiple_cves.rst
rename to docs/howtoguides/fix_how_to_better_visualise_fixing_multiple_cves.rst
diff --git a/docs/howtoguides/how_to_know_if_system_affected_by_cve.rst b/docs/howtoguides/fix_how_to_know_if_system_affected_by_cve.rst
similarity index 100%
rename from docs/howtoguides/how_to_know_if_system_affected_by_cve.rst
rename to docs/howtoguides/fix_how_to_know_if_system_affected_by_cve.rst
diff --git a/docs/howtoguides/how_to_know_what_the_fix_command_would_change.rst b/docs/howtoguides/fix_how_to_know_what_the_fix_command_would_change.rst
similarity index 100%
rename from docs/howtoguides/how_to_know_what_the_fix_command_would_change.rst
rename to docs/howtoguides/fix_how_to_know_what_the_fix_command_would_change.rst
diff --git a/docs/howtoguides/how_to_not_fix_related_usns.rst b/docs/howtoguides/fix_how_to_not_fix_related_usns.rst
similarity index 100%
rename from docs/howtoguides/how_to_not_fix_related_usns.rst
rename to docs/howtoguides/fix_how_to_not_fix_related_usns.rst
diff --git a/docs/howtoguides/how_to_resolve_given_cve.rst b/docs/howtoguides/fix_how_to_resolve_given_cve.rst
similarity index 100%
rename from docs/howtoguides/how_to_resolve_given_cve.rst
rename to docs/howtoguides/fix_how_to_resolve_given_cve.rst
diff --git a/docs/howtoguides/fix_index.rst b/docs/howtoguides/fix_index.rst
new file mode 100644
index 0000000000..33c7d890ef
--- /dev/null
+++ 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>
\ No newline at end of file