diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 567d304e..c7085586 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -578,7 +578,7 @@ complex behavior. - The lexical scope of a keyword is deterimined by the nested JSON + The lexical scope of a keyword is determined by the nested JSON data structure of objects and arrays. The largest such scope is an entire schema document. The smallest scope is a single schema object with no subschemas. @@ -1008,7 +1008,7 @@
Several keywords can be used to reference a schema which is to be applied to the - current instance location. "$ref" and "$recursiveRef" are an applicator + current instance location. "$ref" and "$recursiveRef" are applicator keywords, applying the referenced schema to the instance. "$recursiveAnchor" is a helper keyword that controls how the referenced schema of "$recursiveRef" is determined. @@ -1242,7 +1242,7 @@
-
+
A schema MUST NOT be run into an infinite loop against an instance. For example, if two schemas "#alice" and "#bob" both have an "allOf" property @@ -1783,7 +1783,7 @@ If the object key is a property in the instance, the entire - instance must validate against the susbschema. Its use is + instance must validate against the subschema. Its use is dependent on the presence of the property. @@ -2440,7 +2440,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0 Emphasized annotations as a primary usage of JSON Schema Clarified $id by use cases Exhaustive schema identification examples - Replaced "external referencing" with how and when an implementation might know of a schema from another doucment + Replaced "external referencing" with how and when an implementation might know of a schema from another document Replaced "internal referencing" with how an implementation should recognized schema identifiers during parsing Dereferencing the former "internal" or "external" references is always the same process Minor formatting improvements