more fixes + image link fix

src/courses/delta/02.md

@@ -23,8 +23,6 @@ For more information on this command, refer to the documentation for [`inspec_pr
 This command is similar to the Chef InSpec [Initialize a new profile](../beginner/03.md#creating-the-profile), but it uses the XCCDF content to configure (generate) the profile controls metadata and [supporting structure](../beginner/02.md#the-structure-of-an-inspec-profile).
 :::
 
-The [Delta CLI Tools section](./03.md#31-cli-tools) covers specific requirements for both the `delta` and `update_controls4delta` commands.
-
 ## 2.2 Glossary of Terms
 
 For definitions of terms used within the Delta Process, refer to [Terms & Definitions](../profile-dev-test/27.md#terms--definitions).

src/courses/delta/03.md

@@ -80,8 +80,4 @@ saf generate delta --help
 For more information on these commands, refer to the following documentation:
 
 - [update_controls4delta](https://saf-cli.mitre.org/#delta-supporting-options)
-- [saf generate delta](https://saf-cli.mitre.org/#delta)
-
-::: warning Delta Process Limitations
-The Delta process has been tested using DISA XCCDF STIG Benchmark Guidances only.
-:::
+- [saf generate delta](https://saf-cli.mitre.org/#delta)

src/courses/delta/04.md

@@ -68,7 +68,7 @@ This include the profile summary JSON file generated used `cinc-auditor json red
 Running the update controls command on this profile can give us information on what needs to be updated:
 `saf generate update_controls4delta -X rhel_8_xccdf.xml -J profile.json -c ./redhat-enterprise-linux-8-stig-baseline/controls`
 
-![update_controls4delta output](../../assets/img/Delta_Class/use_case_2_2.png)
+![update_controls4delta output](../../assets/img/Delta_Class/use_case_2-2.png)
 
 From this we can gather:
 1. No existing controls needed to be renamed in the new STIG guidance (366 controls with correct identification, 0 processed files).