edits suggested by @handrews

Author: gregsdennis

jsonschema-core.xml

@@ -2756,11 +2756,11 @@
                     Implementations MAY elect to provide additional information.
                 </t>
 
-                <section title="Subschema Relative Location">
+                <section title="Evaluation path">
                     <t>
-                        The relative location of the validating subschema that follows the path
-                        traversed through the schema. The value MUST be expressed as a JSON
-                        Pointer, and it MUST include any by-reference applicators such as
+                        The location of the schema resource that produced the output unit, represented
+                        by the path traversed during evaluation. The value MUST be expressed as a
+                        JSON Pointer, and it MUST include any by-reference applicators such as
                         "$ref" or "$dynamicRef".
                         <cref>
                             The schema may not actually have a value at the location indicated
@@ -2784,12 +2784,13 @@
                     </t>
                 </section>
 
-                <section title="Subschema Absolute Location">
+                <section title="Subschema Location">
                     <t>
-                        The absolute, dereferenced location of the validating subschema.  The value MUST
-                        be expressed as a full IRI using the canonical IRI of the relevant
-                        schema object, and it MUST NOT include by-reference applicators
-                        such as "$ref" or "$dynamicRef" as path components.
+                        The absolute, dereferenced location of the schema resource that produced
+                        the output unit.  The value MUST be expressed using the canonical IRI of the
+                        relevant schema resource plus a JSON Pointer fragment that indicates the contained
+                        subschema that produced the output.  It MUST NOT include by-reference applicators
+                        such as "$ref" or "$dynamicRef".
                         <cref>
                             Note that "absolute" here is in the sense of "absolute filesystem path"
                             (meaning the complete location) rather than the "absolute-IRI"
@@ -2857,11 +2858,12 @@ https://example.com/schemas/common#/$defs/count/minimum
 
                 <section title="Nested Results">
                     <t>
-                        Nested results are generated from applicator keywords: keywords with
-                        subschemas or collections of subschemas as values.  Keywords which
-                        have arrays of subschemas (e.g. "anyOf") will generally generate an output
-                        unit for each subschema.  In order to accommodate potentially multiple
-                        results, the value of this property MUST be an array of output units.
+                        Nested results are generated from keywords which create a new dynamic
+                        scope by applying a subschema to the instance or a child of the instance.
+                        Keywords which have multiple subschemas (e.g. "anyOf") will generally
+                        generate an output unit for each subschema.  In order to accommodate
+                        potentially multiple results, the value of this property MUST be an
+                        array of output units, even if only a single output unit is produced.
                     </t>
                     <t>
                         For "basic", this property will appear only at the root output unit