diff --git a/jsonschema-core.md b/jsonschema-core.md
index cfc6338c..4060e243 100644
--- a/jsonschema-core.md
+++ b/jsonschema-core.md
@@ -2246,7 +2246,7 @@ determines the canonical nature of the resulting full IRI.[^18]
 and direct you to read the CREF located in {{#embedded}} for further comments.
 
 While the following IRIs do correctly indicate specific schemas, per the reasons
-outlined in {{embedded}}, they are to be avoided:
+outlined in {{embedded}}, they are to be avoided as they may not work in all implementations:
 
 Document location `/$defs/B`:
 - canonical (and base) `IRI: https://example.com/other.json`
diff --git a/jsonschema-validation.md b/jsonschema-validation.md
index 443e6880..7b1ed9ee 100644
--- a/jsonschema-validation.md
+++ b/jsonschema-validation.md
@@ -444,7 +444,7 @@ representation of an IP address as follows:
   [RFC3986](#rfc3986).
 - *iri:* A string instance is valid against this attribute if it is a valid IRI,
   according to [RFC3987](#rfc3987).
-- *IRI reference:* A string instance is valid against this attribute if it is a
+- *iri-reference:* A string instance is valid against this attribute if it is a
   valid IRI Reference (either an IRI or a relative-reference), according to
   [RFC3987](#rfc3987).
 - *uuid:* A string instance is valid against this attribute if it is a valid
@@ -948,7 +948,7 @@ schema form to the core spec
     - Restored "regex" format (removal was unintentional)
     - Added "date" and "time" formats, and reserved additional RFC 3339 format
       names
-    - I18N formats: "iri", "IRI reference", "idn-hostname", "idn-email"
+    - I18N formats: "iri", "iri-reference", "idn-hostname", "idn-email"
     - Clarify that "json-pointer" format means string encoding, not URI fragment
     - Fixed typo that inverted the meaning of `minimum` and `exclusiveMinimum`
     - Move format syntax references into Normative References