Skip to content

improve some wording in draft 2020-xx rc0 #1038

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 28, 2020
Merged

improve some wording in draft 2020-xx rc0 #1038

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@
where an instance may be outside any of the six JSON data types.
</t>
<t>
In this case, annotations still apply; but validation keywords will not be useful,
In this case, annotations still apply; but most validation keywords will not be useful,
as they will always pass or always fail.
</t>
<t>
Expand Down Expand Up @@ -345,7 +345,7 @@
of their subschemas.
</t>
<t>
Keywords within the same schema object are referred to as adjacent keywords.
Keywords which are properties within the same schema object are referred to as adjacent keywords.
</t>
<t>
Extension keywords, meaning those defined outside of this document
Expand All @@ -364,7 +364,7 @@
<section title="Boolean JSON Schemas">
<t>
The boolean schema values "true" and "false" are trivial schemas that
always produce themselves as assertions results, regardless of the
always produce themselves as assertion results, regardless of the
instance value. They never produce annotation results.
</t>
<t>
Expand Down Expand Up @@ -547,7 +547,7 @@
dialect described in <xref target="ecma262">ECMA-262, section 21.2.1</xref>.
</t>
<t>
Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide
Regular expressions SHOULD be built with the "u" flag (or equivalent) to provide
Unicode support, or processed in such a way which provides Unicode as defined
by ECMA-262.
</t>
Expand Down
2 changes: 1 addition & 1 deletion schema.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
"https://json-schema.org/draft/2019-09/vocab/unevaluated": true,
"https://json-schema.org/draft/2019-09/vocab/validation": true,
"https://json-schema.org/draft/2019-09/vocab/meta-data": true,
"https://json-schema.org/draft/2019-09/meta/format-annotation": true,
"https://json-schema.org/draft/2019-09/vocab/format-annotation": true,
"https://json-schema.org/draft/2019-09/vocab/content": true
},
"$dynamicAnchor": "meta",
Expand Down