diff --git a/src/courses/delta/04.md b/src/courses/delta/04.md
index 00a67ad0f..f39a832b4 100644
--- a/src/courses/delta/04.md
+++ b/src/courses/delta/04.md
@@ -11,7 +11,7 @@ There are several situations that warrant the use of the delta process. These ar
 
 1. [Use Case 1](#411-use-case-1) - Check and update control IDs and metadata based on new guidance (run update controls)
 
-3. [Use Case 2](#415-use-case-4) - Generate stubs for new controls found in the XCCDF Benchmark file (run Delta without fuzzy matching)
+3. [Use Case 2](#415-use-case-2) - Generate stubs for new controls found in the XCCDF Benchmark file (run Delta without fuzzy matching)
 
 4. [Use Case 3](#414-use-case-3) - No mappings were found using update controls (run Delta with fuzzy matching)
 
@@ -25,7 +25,7 @@ Updated guidance sometimes modifies the control identification (ID) values of a
 
 [return to top](#41-use-cases-for-running-delta)
 
-### 4.1.4 Use Case 3
+### 4.1.4 Use Case 2
 
 New guidance often contains new controls that weren't previously defined. In this case, running the delta process generates the control stubs with all metadata, except for the describe block (code) content.
 
@@ -33,7 +33,7 @@ New guidance often contains new controls that weren't previously defined. In thi
 
 [return to top](#41-use-cases-for-running-delta)
 
-### 4.1.5 Use Case 4
+### 4.1.5 Use Case 3
 
 Running update controls may result in no controls being updated or no mappings being found from baseline X to baseline Y. This could be due to the baselines belonging to different platforms, or too many revisions were released between the two baselines, creating no way to map between them. In this case, use Delta with fuzzy matching.