|
585 | 585 | complex behavior. |
586 | 586 | </t> |
587 | 587 | <t> |
588 | | - The lexical scope of a keyword is deterimined by the nested JSON |
| 588 | + The lexical scope of a keyword is determined by the nested JSON |
589 | 589 | data structure of objects and arrays. The largest such scope |
590 | 590 | is an entire schema document. The smallest scope is a single |
591 | 591 | schema object with no subschemas. |
|
1280 | 1280 | <section title="Schema References"> |
1281 | 1281 | <t> |
1282 | 1282 | Several keywords can be used to reference a schema which is to be applied to the |
1283 | | - current instance location. "$ref" and "$recursiveRef" are an applicator |
| 1283 | + current instance location. "$ref" and "$recursiveRef" are applicator |
1284 | 1284 | keywords, applying the referenced schema to the instance. "$recursiveAnchor" |
1285 | 1285 | is a helper keyword that controls how the referenced schema of "$recursiveRef" |
1286 | 1286 | is determined. |
|
1514 | 1514 | </section> |
1515 | 1515 | </section> |
1516 | 1516 |
|
1517 | | - <section title="Guarding Against Inifinite Recursion"> |
| 1517 | + <section title="Guarding Against Infinite Recursion"> |
1518 | 1518 | <t> |
1519 | 1519 | A schema MUST NOT be run into an infinite loop against an instance. For |
1520 | 1520 | example, if two schemas "#alice" and "#bob" both have an "allOf" property |
|
2067 | 2067 | </t> |
2068 | 2068 | <t> |
2069 | 2069 | If the object key is a property in the instance, the entire |
2070 | | - instance must validate against the susbschema. Its use is |
| 2070 | + instance must validate against the subschema. Its use is |
2071 | 2071 | dependent on the presence of the property. |
2072 | 2072 | </t> |
2073 | 2073 | <t> |
@@ -2746,7 +2746,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0 |
2746 | 2746 | <t>Emphasized annotations as a primary usage of JSON Schema</t> |
2747 | 2747 | <t>Clarified $id by use cases</t> |
2748 | 2748 | <t>Exhaustive schema identification examples</t> |
2749 | | - <t>Replaced "external referencing" with how and when an implementation might know of a schema from another doucment</t> |
| 2749 | + <t>Replaced "external referencing" with how and when an implementation might know of a schema from another document</t> |
2750 | 2750 | <t>Replaced "internal referencing" with how an implementation should recognized schema identifiers during parsing</t> |
2751 | 2751 | <t>Dereferencing the former "internal" or "external" references is always the same process</t> |
2752 | 2752 | <t>Minor formatting improvements</t> |
|
0 commit comments