Merge pull request #470 from dlax/hyperschema-minor-edits

A couple of edits/fixes in hyperschema spec

Author: handrews

jsonschema-hyperschema.xml

@@ -1289,7 +1289,7 @@ for varname in templateData:
             </t>
             <t>
                 This section provides guidance on how to use each common HTTP method with a link,
-                and how colletion resources impose additional constraints on HTTP POST.
+                and how collection resources impose additional constraints on 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>
@@ -1635,7 +1635,7 @@ Link: <https://schema.example.com/entry> rel=describedBy
                     input, as well as using them alongside of resolving the URI Template with
                     input.  Unlike HTML forms, which require either constructing a URI or
                     sending a payload, but do not allow not both at once, JSON Hyper-Schema can
-                    describe both sorts of input to for the same operation on the same link.
+                    describe both sorts of input for the same operation on the same link.
                 </t>
                 <t>
                     The "submissionSchema" and "submissionMediaType" fields are for
@@ -1650,7 +1650,7 @@ Link: <https://schema.example.com/entry> rel=describedBy
                     a message for sending.  Since there is no concept of a retrievable,
                     replaceable, or deletable target resource, "targetSchema" and
                     "targetMediaType" are not used.  Non-representation payloads are
-                    described by "submissionSchema" and "submission MediaType".
+                    described by "submissionSchema" and "submissionMediaType".
                 </t>
                 <t>
                     Therefore, we use "submissionMediaType" to indicate a multipart/alternative