From 41ccaac72fe697c6d05dc2d360c8c8f2c5585b71 Mon Sep 17 00:00:00 2001
From: Brad Bowman <github@bereft.net>
Date: Thu, 24 Nov 2016 15:49:07 +0100
Subject: [PATCH] A couple of typos

---
 jsonschema-core.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/jsonschema-core.xml b/jsonschema-core.xml
index b7140511..f387940c 100644
--- a/jsonschema-core.xml
+++ b/jsonschema-core.xml
@@ -134,7 +134,7 @@
                     In JSON Schema, the terms "JSON document", "JSON text", and "JSON value" are interchangeable because of the data model it defines.
                 </t>
                 <t>
-                    JSON Schema is only defined over JSON documents. However, any document or memory structure that can be parsed into or processed according to the JSON Schema data model can be interperted against a JSON Schema, including media types like <xref target="RFC7049">CBOR</xref>.
+                    JSON Schema is only defined over JSON documents. However, any document or memory structure that can be parsed into or processed according to the JSON Schema data model can be interpreted against a JSON Schema, including media types like <xref target="RFC7049">CBOR</xref>.
                 </t>
             </section>
 
@@ -155,7 +155,7 @@
                     </list>
                 </t>
                 <t>
-                    Whitespace and formatting conserns are thus outside the scope of JSON Schema.
+                    Whitespace and formatting concerns are thus outside the scope of JSON Schema.
                 </t>
                 <t>
                     Since an object cannot have two properties with the same key, behavior for a JSON document that tries to define two properties (the "member" production) with the same key (the "string" production) in a single object is undefined.