@@ -306,7 +306,7 @@ independent of the parent schema. A schema that contains one or more embedded
306
306
schemas is called a "Compound Schema Document". This draft introduces guidance
307
307
on how bundlers should embedded schemas to create Compound Schema Documents.
308
308
309
- If you reference an external schema, that schema can declare it's own ` $schema `
309
+ If you reference an external schema, that schema can declare its own ` $schema `
310
310
and that may be different than the ` $schema ` of the referencing schema.
311
311
Implementations need to be prepared to switch processing modes or throw an
312
312
error if they don't support the ` $schema ` of the referenced schema. Embedded
@@ -417,7 +417,7 @@ embedded schemas using `$defs`. Here's what the bundled schema would look like.
417
417
}
418
418
}
419
419
},
420
- "$id" : " https://example.com/schema/common" : {
420
+ "https://example.com/schema/common" : {
421
421
"$schema" : " https://json-schema.org/draft/2019-09" ,
422
422
"$id" : " https://example.com/schema/common" ,
423
423
@@ -462,7 +462,7 @@ unknown keyword is the keyword's value.
462
462
463
463
## Vocabulary Changes
464
464
The ` unevaluatedProperties ` and ` unevaluatedItems ` keywords have been moved from
465
- the applicator vocabulary to their own vocabulary designated which is required
465
+ the applicator vocabulary to their own designated vocabulary which is required
466
466
in the default meta-schema. In Draft 2019-09, these keywords were expected to
467
467
throw an error if not implemented. This was a special-case behavior of the
468
468
applicator vocabulary. Moving the "unevaluated" keywords into their own
0 commit comments