Another attempt at describing what a dynamic anchor is

Author: jdesrosiers

specs/jsonschema-core.md

@@ -966,13 +966,15 @@ just a fragment identifier not an IRI reference. To reference the "foo"
 `$anchor` from the same schema resource, you would use the fragment-only IRI
 `#foo`. See below for full examples.
 
-`$dynamicAnchor` defines a different kind of identifier that only has meaning
-when used as a value for `$dynamicRef`. It's not a fragment identifier that can
-be used in an IRI. `$dynamicRef` uses a syntax similar to a fragment-only IRI,
-but the semantics are different. Unlike fragments in IRIs, the fragment in
-`$dynamicRef` identifiers identifies the primary resource (the schema resource)
-in addition to the secondary resource (the subschema within that schema
-resource). See {{dynamic-ref}} for details.
+`$dynamicAnchor` defines a different kind of fragment identifier that only has
+meaning when used with `$dynamicRef`. It's not a normal fragment identifier and
+therefore can't be used anywhere other than `$dynamicRef`. Normal [fragment
+identifiers](https://www.rfc-editor.org/rfc/rfc3986#section-3.5) identify the
+secondary resource (the subschema) while the rest of the IRI identifies the
+primary resource (the schema resource). The fragment identifiers defined by
+`$dynamicAnchor` are not normal fragment identifies because they identify both
+the primary resource and the secondary resource. See {{dynamic-ref}} for
+details.
 
 If present, the value of these keywords MUST be a string and MUST conform to the
 plain name fragment identifier syntax defined in {{fragments}}.