verified ux; tweaked wording

Author: gregsdennis

.jekyll-metadata

@@ -91,7 +91,7 @@ If the value is a JSON Path, the query is executed against the instance at the c
 > JSON Path returns a nodelist, which contains both values and their locations within the instance.  This operation discards the locations and retains only the values.
 {: .prompt-info }
 
-Otherwise, it must be resolved in accordance with the rules of `$ref` resolution for the relevant JSON Schema specification (e.g. [draft 2020-12, §8.2](https://json-schema.org/draft/2020-12/json-schema-core.html#name-base-uri-anchors-and-derefe)).  However, unlike `$ref` which requires that the indicated data must represent a valid schema object, `data` and `optionalData` references can identify any value which is valid for the associated keyword.
+Otherwise, it must be resolved in accordance with the rules of `$ref` resolution for the relevant JSON Schema specification (e.g. [draft 2020-12, §8.2](https://json-schema.org/draft/2020-12/json-schema-core#section-8.2)).  However, unlike `$ref` which requires that the indicated data must represent a valid schema object, `data` and `optionalData` references can identify any value which is valid for the associated keyword.
 
 For each successfully resolved reference, the full value at the specified location MUST be returned.
 
@@ -223,7 +223,7 @@ The schema below requires that `selection` be an ID from within the `options` ar
 }
 ```
 
-In this example, `$.options[*].id` returns an array of the available IDs which is then used in an `enum`.  Then, `selection` is validated to be one of those IDs.
+In this example, `$.options[*].id` evaluated against the instance returns an array of the available IDs which is used in `enum`.  Then, `selection` is validated to be one of those IDs.
 
 If `selection` is present in the array's ID values, then the validation passes.