Merge pull request #271 from handrews/hyper-typos

Fix typos in hyper-schema spec.

Author: awwright

jsonschema-hyperschema.xml

@@ -739,7 +739,7 @@ GET /foo/
                         </figure>
                     </t>
                     <t>
-                        A third party might then write provide the following Link Description Object at another location:
+                        A third party might then provide the following Link Description Object at another location:
                         <figure>
                             <artwork>
 <![CDATA[{
@@ -855,7 +855,7 @@ GET /foo/
                         This property specifies that the client can construct a templated query or non-idempotent request to a resource.
                     </t>
                     <t>
-                        If "method" is "get", the link identifies how a user can compute the URI of an arbitrary resource. For example, how compute a link to a page of search results relating to the instance, for a user-selected query term. Despite being named after GET, there is no constraint on the method or protocol used to interact with the remote resource.
+                        If "method" is "get", the link identifies how a user can compute the URI of an arbitrary resource. For example, how to compute a link to a page of search results relating to the instance, for a user-selected query term. Despite being named after GET, there is no constraint on the method or protocol used to interact with the remote resource.
                     </t>
                     <t>
                         If "method" is "post", the link specifies how a user can construct a document to submit to the link target for evaluation.
@@ -867,7 +867,7 @@ GET /foo/
 
                 <section title="encType">
                     <t>
-                        If present, this property indicates the media type format the client should use to encode a query parameter or send to the server. posting to the collection of instances at the target resource.
+                        If present, this property indicates the media type format the client should use to encode a query parameter or send to the server.
                         If the method is "get", this will indicate how to encode the query-string that is appended to the "href" link target.
                         If the method is "post", this indicates which media type to send to the server and how to encode it.
 
@@ -911,7 +911,7 @@ GET /foo/
                     </t>
 
                     <t>
-                        Note that this does not provide data for any URI templates.  That is handed by <xref target="hrefSchema">"hrefSchema"</xref>.  If the method is "get" and the resolved URI Template has a query string, the query string produced by input validated against "schema" replaces the existing query string.
+                        Note that this does not define the structure for URI template variables.  That is handed by <xref target="hrefSchema">"hrefSchema"</xref>.  If the method is "get" and the resolved URI Template has a query string, the query string produced by input validated against "schema" replaces the existing query string.
                     </t>
 
                     <t>