|
287 | 287 | where an instance may be outside any of the six JSON data types. |
288 | 288 | </t> |
289 | 289 | <t> |
290 | | - In this case, annotations still apply; but validation keywords will not be useful, |
| 290 | + In this case, annotations still apply; but most validation keywords will not be useful, |
291 | 291 | as they will always pass or always fail. |
292 | 292 | </t> |
293 | 293 | <t> |
|
345 | 345 | of their subschemas. |
346 | 346 | </t> |
347 | 347 | <t> |
348 | | - Keywords within the same schema object are referred to as adjacent keywords. |
| 348 | + Keywords which are properties within the same schema object are referred to as adjacent keywords. |
349 | 349 | </t> |
350 | 350 | <t> |
351 | 351 | Extension keywords, meaning those defined outside of this document |
|
364 | 364 | <section title="Boolean JSON Schemas"> |
365 | 365 | <t> |
366 | 366 | The boolean schema values "true" and "false" are trivial schemas that |
367 | | - always produce themselves as assertions results, regardless of the |
| 367 | + always produce themselves as assertion results, regardless of the |
368 | 368 | instance value. They never produce annotation results. |
369 | 369 | </t> |
370 | 370 | <t> |
|
547 | 547 | dialect described in <xref target="ecma262">ECMA-262, section 21.2.1</xref>. |
548 | 548 | </t> |
549 | 549 | <t> |
550 | | - Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide |
| 550 | + Regular expressions SHOULD be built with the "u" flag (or equivalent) to provide |
551 | 551 | Unicode support, or processed in such a way which provides Unicode as defined |
552 | 552 | by ECMA-262. |
553 | 553 | </t> |
|
0 commit comments