From c70067dd1e7eb26c5f1e17ccab5f3a7fbc786ae0 Mon Sep 17 00:00:00 2001 From: Daniel Wagner-Hall Date: Mon, 19 Oct 2015 10:44:26 +0100 Subject: [PATCH] Simplify language --- specification/modules/third_party_invites.rst | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/specification/modules/third_party_invites.rst b/specification/modules/third_party_invites.rst index ebca59cf..85538c31 100644 --- a/specification/modules/third_party_invites.rst +++ b/specification/modules/third_party_invites.rst @@ -36,8 +36,8 @@ A client asks a server to invite a user by their third party identifier. Server behaviour ---------------- -All homeservers MUST verify the signature in the ``signed`` property of the -``third_party_invite`` property in the ``content`` the event. +All homeservers MUST verify the signature in the event's +``content.third_party_invite.signed`` object. If a client of the current homeserver is joining by an ``m.room.third_party_invite``, that homesever MUST validate that the public @@ -94,9 +94,8 @@ For example: When the third party user validates their identity, they are told about the invite, and ask their homeserver, H3, to join the room. - H3 validates that signature in the ``signed`` property of the - ``third_party_invite`` property of the ``content`` property of the event, - and may check ``key_validity_url``. + H3 validates the signature in the event's + ``content.third_party_invite.signed`` object. H3 then asks H1 to join it to the room. H1 *must* validate the ``signed`` property *and* check ``key_validity_url``.