|
578 | 578 | complex behavior. |
579 | 579 | </t> |
580 | 580 | <t> |
581 | | - The lexical scope of a keyword is deterimined by the nested JSON |
| 581 | + The lexical scope of a keyword is determined by the nested JSON |
582 | 582 | data structure of objects and arrays. The largest such scope |
583 | 583 | is an entire schema document. The smallest scope is a single |
584 | 584 | schema object with no subschemas. |
|
1008 | 1008 | <section title="Schema References"> |
1009 | 1009 | <t> |
1010 | 1010 | Several keywords can be used to reference a schema which is to be applied to the |
1011 | | - current instance location. "$ref" and "$recursiveRef" are an applicator |
| 1011 | + current instance location. "$ref" and "$recursiveRef" are applicator |
1012 | 1012 | keywords, applying the referenced schema to the instance. "$recursiveAnchor" |
1013 | 1013 | is a helper keyword that controls how the referenced schema of "$recursiveRef" |
1014 | 1014 | is determined. |
|
1242 | 1242 | </section> |
1243 | 1243 | </section> |
1244 | 1244 |
|
1245 | | - <section title="Guarding Against Inifinite Recursion"> |
| 1245 | + <section title="Guarding Against Infinite Recursion"> |
1246 | 1246 | <t> |
1247 | 1247 | A schema MUST NOT be run into an infinite loop against an instance. For |
1248 | 1248 | example, if two schemas "#alice" and "#bob" both have an "allOf" property |
|
1783 | 1783 | </t> |
1784 | 1784 | <t> |
1785 | 1785 | If the object key is a property in the instance, the entire |
1786 | | - instance must validate against the susbschema. Its use is |
| 1786 | + instance must validate against the subschema. Its use is |
1787 | 1787 | dependent on the presence of the property. |
1788 | 1788 | </t> |
1789 | 1789 | <t> |
@@ -2440,7 +2440,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0 |
2440 | 2440 | <t>Emphasized annotations as a primary usage of JSON Schema</t> |
2441 | 2441 | <t>Clarified $id by use cases</t> |
2442 | 2442 | <t>Exhaustive schema identification examples</t> |
2443 | | - <t>Replaced "external referencing" with how and when an implementation might know of a schema from another doucment</t> |
| 2443 | + <t>Replaced "external referencing" with how and when an implementation might know of a schema from another document</t> |
2444 | 2444 | <t>Replaced "internal referencing" with how an implementation should recognized schema identifiers during parsing</t> |
2445 | 2445 | <t>Dereferencing the former "internal" or "external" references is always the same process</t> |
2446 | 2446 | <t>Minor formatting improvements</t> |
|
0 commit comments