diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md
index 1c310e78..51251b0d 100644
--- a/content/client-server-api/modules/end_to_end_encryption.md
+++ b/content/client-server-api/modules/end_to_end_encryption.md
@@ -434,7 +434,7 @@ shared by the other messages of that session.
 
 In general, verification operates as follows:
 
-- Alice requests a key verification with Bob by sending an key verification
+- Alice requests a key verification with Bob by sending a key verification
   request event.  If the verification is being requested in a room, this will
   be an event with type `m.room.message` and `msgtype`
   `m.key.verification.request`; if the verification is being requested using
diff --git a/data/event-schemas/schema/m.room.message$m.key.verification.request.yaml b/data/event-schemas/schema/m.room.message$m.key.verification.request.yaml
index 4eb4483a..c0a0764c 100644
--- a/data/event-schemas/schema/m.room.message$m.key.verification.request.yaml
+++ b/data/event-schemas/schema/m.room.message$m.key.verification.request.yaml
@@ -11,7 +11,7 @@ properties:
       body:
         type: string
         description: |-
-          a fallback message to alert users that their client does not support
+          A fallback message to alert users that their client does not support
           the key verification framework, and that they should use a different method
           to verify keys.  For example, "Alice is requesting to verify keys with you.
           However, your client does not support this method, so you will need to use
@@ -58,6 +58,7 @@ properties:
       - from_device
       - methods
       - msgtype
+      - to
     type: object
   type:
     enum: