From 1784886ea9871dfa9fff9e00aedf9cd66bed1e1e Mon Sep 17 00:00:00 2001 From: Daniel Perrett Date: Wed, 8 Jul 2015 11:43:37 +0100 Subject: [PATCH] Standardise use of hyphens with 'non' --- jsonschema-core.xml | 2 +- jsonschema-schema.xml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 1e8c50d7..02a631c5 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -522,7 +522,7 @@
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: diff --git a/jsonschema-schema.xml b/jsonschema-schema.xml index aebacfed..4674ac09 100644 --- a/jsonschema-schema.xml +++ b/jsonschema-schema.xml @@ -17,7 +17,7 @@ - JSON Schema: interactive and non interactive validation + JSON Schema: interactive and non-interactive validation
@@ -64,7 +64,7 @@ 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