Correct typos and URLs for GSA#833 constraint re @Gabeblis feedback

Co-authored-by: Gabeblis <[email protected]>

src/validations/constraints/fedramp-external-constraints.xml

@@ -62,9 +62,8 @@
             </let>
             <let var="minor-version-valid" expression="$doc-oscal-version-parts[2] >= $required-doc-oscal-version-parts[2]"/>
             <let var="patch-version-valid" expression="$doc-oscal-version-parts[3] >= $required-doc-oscal-version-parts[3]"/>
-            <expect id="oscal-version-matches-fedramp-version" target="oscal-version" level="ERROR"
-                test="$major-version-valid and $minor-version-valid and $patch-version-valid">
-                <prop namespace="https://docs.oasis-open.org/sarif/sarif/v2.1.0" name="help-url" value="https://docs.oasis-open.org/sarif/sarif/v2.1.0"/>                
+            <expect id="oscal-version-matches-fedramp-version" target="oscal-version" test="$major-version-valid and $minor-version-valid and $patch-version-valid" level="ERROR">
+                <prop namespace="https://docs.oasis-open.org/sarif/sarif/v2.1.0" name="help-url" value="https://automate.fedramp.gov/documentation/general-concepts/oscal-file-concepts/#oscal-syntax-version"/>                
                 <message>A FedRAMP document SHOULD have an OSCAL version that matches the minimally required version for FedRAMP packages ({$fedramp-required-minimum-version} not {.}).</message>
             </expect>
         </constraints>

src/validations/constraints/unit-tests/oscal-version-matches-fedramp-version-FAIL.yaml

@@ -1,7 +1,7 @@
 test-case:
-  name: Positive Test for import-profile-has-available-document
+  name: Positive Test for oscal-version-matches-fedramp-version
   description: >-
-    This test case validates the behavior of constraint import-profile-has-available-document.
+    This test case validates the behavior of constraint oscal-version-matches-fedramp-version.
     Scenario 1 tests: an invalid match below the minimum required version threshold.
     Scenario 2 tests: an invalid match above the implied maximum required version threshold, a major version greater than required.
     Scenario 3 tests: an invalid match because the fedramp-version prop is missing, so a fallthrough default is required.