Numerous spelling fixes

Author: handrews

jsonschema-hyperschema.xml

@@ -146,7 +146,7 @@
                 A user agent need not construct a link unless a client application requests
                 that link.  JSON Hyper-Schema can also be used on the server side to generate
                 other link serializations or representation formats at runtime, or pre-emptively
-                follow links to faciliate server push usage.
+                follow links to facilitate server push usage.
             </t>
 
             <section title="Terminology">
@@ -267,8 +267,8 @@
                 which is also used to illustrate points in the
                 <xref target="implementation">"Implementation Requirements"</xref>, and to
                 show the output generated by <xref target="examples">examples</xref>.
-                It is RECOMMENDED that implementations be capable of producting output
-                in this format to faciliated testing.  The URI of the JSON Schema
+                It is RECOMMENDED that implementations be capable of producing output
+                in this format to facilitated testing.  The URI of the JSON Schema
                 describing the recommended output format is
                 <eref target="http://json-schema.org/draft-7-wip/hyper-schema-output#">
                 http://json-schema.org/draft-7-wip/hyper-schema-output#</eref>
@@ -372,7 +372,7 @@
                     Implementations MUST be able to construct the link context's URI, and
                     (if necessary for full identification), a JSON Pointer in string representation
                     form as per <xref target="RFC6901">RFC 6901, section 5</xref> in place of
-                    a URI fragment.  The process for construcing a URI based on a URI template
+                    a URI fragment.  The process for constructing a URI based on a URI template
                     is given in the <xref target="uriTemplating">URI Templating</xref> section.
                 </t>
                 <section title="anchor" anchor="anchor">
@@ -501,7 +501,7 @@
                     making use of instance data.  Additionally, with
                     <xref target="hrefSchema">"hrefSchema"</xref>, this template can identify
                     a set of possible target resources to use based on client input.
-                    The full process of resolvling the URI template, with or without client
+                    The full process of resolving the URI template, with or without client
                     input, is covered in the <xref target="uriTemplating">URI Templating</xref>
                     section.
                 </t>
@@ -521,7 +521,7 @@
 
             <section title="Adjusting URI Template resolution">
                 <t>
-                    The keywords in this section are used when resolving all URI Tempaltes
+                    The keywords in this section are used when resolving all URI Templates
                     involved in hyper-schema: "base", "anchor", and "href".  See the
                     <xref target="uriTemplating">URI Templating</xref> section for the complete
                     template resolution algorithm.
@@ -530,7 +530,7 @@
                     Note that when resolving a "base" template, the attachment point from
                     which resolution begins is the attachment point of the "href" or "anchor"
                     keyword being resolved which requires "base" templates to be resolved,
-                    not the attachment point of the "base" kewyord itself.
+                    not the attachment point of the "base" keyword itself.
                 </t>
                 <section title="templatePointers" anchor="templatePointers">
                     <t>
@@ -927,7 +927,7 @@
                 </t>
                 <t>
                     And implementation MUST support looking up links by either their
-                    attachement pointer or context pointer, either by performing the look-up
+                    attachment pointer or context pointer, either by performing the look-up
                     or by providing the set of all links with both pointers determined
                     so that user agents can implement the look-up themselves.
                 </t>
@@ -1083,7 +1083,7 @@ for varname in T:
                     </t>
                     <figure>
                         <preamble>
-                            "InputForm" represents whatevers sort of input mechanism is appropriate.
+                            "InputForm" represents whatever sort of input mechanism is appropriate.
                             This may be a literal web form, or may be a more programmatic construct
                             such as a callback function accepting specific fields and data types,
                             with the given initial values, if any.
@@ -1209,11 +1209,11 @@ for varname in templateData:
                     The requirements around discovering links based on their context, or
                     using the context of links to identify collections, present unique
                     challenges when used with streaming parsers.  It is not possible to
-                    authoritatively fulfill these requirments without processing the entire
+                    authoritatively fulfill these requirements without processing the entire
                     schema and instance documents.
                 </t>
                 <t>
-                    Such implementations MAY chooose to return non-authoritative answers
+                    Such implementations MAY choose to return non-authoritative answers
                     based on data processed to date.  When offering this approach,
                     implementations MUST be clear on the nature of the response, and MUST
                     offer an option to block and wait until all data is processed and
@@ -1356,8 +1356,8 @@ for varname in templateData:
             </t>
             <t>
                 This appendix provides guidance on how to define links for use with each
-                common HTTP method, and how collection resources impose additional constarints
-                on the use of HTTP POST.  Additionaly, guidance is provided on hinting at
+                common HTTP method, and how collection resources impose additional constraints
+                on the use of HTTP POST.  Additionally, guidance is provided on hinting at
                 HTTP response header values and describing possible HTTP request headers
                 that are relevant to the given resource.
             </t>