update use case 1, begin use case 2

src/courses/delta/04.md

@@ -19,9 +19,9 @@ There are several situations that warrant the use of the delta process. These ar
 
 ### 4.1.1 Use Case 1
 
-Updated guidance sometimes modifies the control identification (ID) values of a given control. To make these modifications from baseline X to baseline Y, use the update controls process with the provided XCCDF guidance. The process checks if the new guidance changes the control numbers and updates them if necessary.
+Updated guidances sometimes modifies the control identification (ID) values of a given control. To make these modifications from baseline X to baseline Y, use the update controls process with the provided XCCDF STIG guidance file. The process checks if the new guidance changes the control numbers and updates the internal metadata if necessary.
 
-Suppose we want to update our [Windows Server 2019 inspec profile repository](https://github.com/mitre/microsoft-windows-server-2019-stig-baseline/t) to the latest version. We would take the following steps:
+Suppose we want to update our [Windows Server 2019 inspec profile repository](https://github.com/mitre/microsoft-windows-server-2019-stig-baseline/) from [version 1 release 3](https://github.com/mitre/microsoft-windows-server-2019-stig-baseline/releases/tag/1.3.0) to version 3 release 2.
 
 #### Step 1: Collect necessary files:
 1. Download or clone the Windows Server 2019 profile repository to your system.
@@ -44,6 +44,12 @@ The output should look like this:
 
 ![Update Controls Output](../../assets/img/Delta_Class/use_case_1-3.png)
 
+From these results we can gather that:
+1. 31 controls were skipped, because they are not present in the STIG guidance. This indicates that these controls were deleted in the recent revision.
+2. 272 controls have had their control IDs updated. Any metadata changes have also been made to the controls as well.
+3. 0 controls were found to have the correct identification. This indicated that the STIG guidance renamed all mapped controls.
+4. 1 new control was found in the STIG guidance. It is important to note that `update_controls4delta` does not generate this control for you.
+
 **Process:** Run `update_controls4delta`
 
 [return to top](#41-use-cases-for-running-delta)
@@ -52,6 +58,16 @@ The output should look like this:
 
 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.
 
+Suppose we want to update our [RedHat Enterprise Linux 8 STIG Baseline](https://github.com/mitre/redhat-enterprise-linux-8-stig-baseline) from [Version 1 Release 14](https://github.com/mitre/redhat-enterprise-linux-8-stig-baseline) to version 2 release 1.
+
+#### Step 1: Collect necessary files
+![File directory containing an inspec profile, and XCCDF XML file, and a profile summary JSON](../../assets/img/Delta_Class/use_case_2_1.png)
+
+#### **OPTIONAL**: Run update_controls4delta
+If we were to run the update controls method on this profile, we would observe the following output:
+
+#### Step 2: Run Delta
+
 **Process:** Run `delta`
 
 [return to top](#41-use-cases-for-running-delta)