Attempt to make things clearer

api/client-server/administrative_contact.yaml

@@ -126,8 +126,8 @@ paths:
         Proxies the identity server API ``validate/email/requestToken``, but
         first checks that the given email address is not already associated
         with an account on this Home Server. This API should be used to request
-        validation tokens when adding an email address to an account. This API
+        validation tokens when adding an email address to an account. This API's
-        behaves identically to `/register/email/requestToken`
+        parameters and response is identical to that of `/register/email/requestToken`.
       responses:
         200:
           description: An email was sent to the given address

api/client-server/registration.yaml

@@ -250,11 +250,12 @@ paths:
         first checks that the given email address is associated with an account
         on this Home Server. This API should be used to request
         validation tokens when authenticating for the
-        `account/password` endpoint. This API behaves identically to
+        `account/password` endpoint. This API's parameters and response are
-        `/register/email/requestToken` except that `M_THREEPID_NOT_FOUND` may be
+        identical to that of `/register/email/requestToken` except that
-        returned if no account matching the given email address could be found.
+        `M_THREEPID_NOT_FOUND` may be returned if no account matching the
-        The server may instead send an email to the given address prompting
+        given email address could be found. The server may instead send an
-        the user to create an account. `M_THREEPID_IN_USE` may not be returned.
+        email to the given address prompting the user to create an account.
+        `M_THREEPID_IN_USE` may not be returned.
       responses:
         200:
           description: An email was sent to the given address