Skip to content
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

Standardise use of hyphens with 'non' #3

Merged
merged 1 commit into from
Aug 5, 2015
Merged

Standardise use of hyphens with 'non' #3

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
2 changes: 1 addition & 1 deletion jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -522,7 +522,7 @@
<section title="Inline dereferencing and fragments">
<t>
When using inline dereferencing, a resolution scope may lead to a URI which
has a non empty fragment part which is not a JSON Pointer, as in this
has a non-empty fragment part which is not a JSON Pointer, as in this
example:
</t>

Expand Down
4 changes: 2 additions & 2 deletions jsonschema-schema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
<?rfc rfcedstyle="yes"?>
<rfc category="info" docName="draft-fge-json-schema-validation-01" ipr="trust200902">
<front>
<title abbrev="JSON Schema">JSON Schema: interactive and non interactive validation</title>
<title abbrev="JSON Schema">JSON Schema: interactive and non-interactive validation</title>

<author fullname="Geraint Luff" initials="G" surname="Luff" role="editor">
<address>
Expand Down Expand Up @@ -64,7 +64,7 @@
<abstract>
<t>
JSON Schema (application/schema+json) has several purposes, one of which is instance
validation. The validation process may be interactive or non interactive. For
validation. The validation process may be interactive or non-interactive. For
instance, applications may use JSON Schema to build a user interface enabling
interactive content generation in addition to user input checking, or validate data
retrieved from various sources. This specification describes schema keywords
Expand Down