From ec7e795112ddc5a4d6fb498be996784e9c0ee8b4 Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Thu, 26 Sep 2019 17:20:40 +0100 Subject: [PATCH] reflow --- proposals/2290-separate-threepid-bind-hs.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/proposals/2290-separate-threepid-bind-hs.md b/proposals/2290-separate-threepid-bind-hs.md index 95f810e9..aa71fb35 100644 --- a/proposals/2290-separate-threepid-bind-hs.md +++ b/proposals/2290-separate-threepid-bind-hs.md @@ -70,7 +70,8 @@ homeserver. An example of binding a threepid to an identity server with this new endpoint is as follows: -First the client must request the threepid be validated by its chosen identity server. +First the client must request the threepid be validated by its chosen +identity server. ``` POST https://identity.server/_matrix/identity/v2/validate/email/requestToken @@ -89,7 +90,8 @@ ID, the given client_secret, and a randomly-generated token. Once an email has been sent, the user clicks the link in the email, which notifies the identity server that the email has been verified. -Next, the client completes the bind by calling the new endpoint on the homeserver: +Next, the client completes the bind by calling the new endpoint on the +homeserver: ``` POST https://home.server/_matrix/client/r0/account/3pid/bind