Fix typos in two explainer files (#203)

Author: juanferrub

README.md

@@ -321,7 +321,7 @@ By default, WebMCP is enabled in top-level `Window`s and its same-origin iframes
   <iframe src="https://chat-bot-provider.example/" allow="tools"></iframe>
   ```
 
-Calls to `document.modelContext.registerTool()` will return a promise rejected with `NotAllowedError` DOMException when the permission is disabled, whether by the `allow` attribute or the `Permissions-Policy: tools=()` header. Handling of declarative tool registration errors, including when the permisssion is disabled is TBD; see [Issue #182](https://github.com/webmachinelearning/webmcp/issues/182).
+Calls to `document.modelContext.registerTool()` will return a promise rejected with `NotAllowedError` DOMException when the permission is disabled, whether by the `allow` attribute or the `Permissions-Policy: tools=()` header. Handling of declarative tool registration errors, including when the permission is disabled is TBD; see [Issue #182](https://github.com/webmachinelearning/webmcp/issues/182).
 
 #### Cross-origin iframe exposure: `exposedTo`
 

declarative-api-explainer.md

@@ -109,7 +109,7 @@ TODO: The exact algorithms reducing a form, its form-associated elements, and *t
 like [`step`](https://html.spec.whatwg.org/C#the-step-attribute) and
 [`min`](https://html.spec.whatwg.org/C#attr-input-min) is TBD. We need to concretely specify how
 various form-associated elements like `<input>` and `<select>` reduce to a JSON Schema that includes
-`anyOf`, `oneOf`, and `maximum`/`mininum` declarations.
+`anyOf`, `oneOf`, and `maximum`/`minimum` declarations.
 
 Chromium is implementing a loose version of this and will conduct testing/trials to see if what
 we've come up with should be supported by the community as a general approach.