Typos

content/client-server-api/modules/voip_events.md

@@ -73,7 +73,7 @@ up the call.
 #### ICE Candidate Batching
 Clients should aim to send a small number of candidate events, with guidelines:
  * ICE candidates which can be discovered immediately or almost immediately in the invite/answer
-   event itself (eg. host candidates). If server reflexive or relay candiates can be gathered in
+   event itself (eg. host candidates). If server reflexive or relay candidates can be gathered in
    a sufficiently short period of time, these should be sent here too. A delay of around 200ms is
    suggested as a starting point.
  * The client should then allow some time for further candidates to be gathered in order to batch them,

data/event-schemas/schema/m.call.hangup.yaml

@@ -11,7 +11,7 @@ description: |
       media had previously been received successfully, even if the ICE renegotiation itself failed.
    * `invite_timeout`: The other party did not answer in time.
    * `user_hangup`: Clients must now send this code when the user chooses to end the call, although
-     for backwards compatability with version 0, a clients should treat an absence of the `reason`
+     for backwards compatibility with version 0, a clients should treat an absence of the `reason`
      field as `user_hangup`.
    * `user_media_failed`: The client was unable to start capturing media in such a way that it is unable
      to continue the call.