Fix rendering of m.receipt event in Client-Server API (#1637)

... and other improvements

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

data/api/application-service/definitions/protocol.yaml

@@ -41,7 +41,6 @@ properties:
     type: string
     example: "mxc://example.org/aBcDeFgH"
   field_types:
-    title: Field Types
     description: |-
       The type definitions for the fields defined in the `user_fields` and
       `location_fields`. Each entry in those arrays MUST have an entry here. The

data/api/client-server/cross_signing.yaml

@@ -150,7 +150,6 @@ paths:
       description: |-
         Publishes cross-signing signatures for the user.
 
-        The request body is a map from user ID to key ID to signed JSON object.
         The signed JSON object must match the key previously uploaded or
         retrieved for the given key ID, with the exception of the `signatures`
         property, which contains the new signature(s) to add.
@@ -162,7 +161,8 @@ paths:
           application/json:
             schema:
               type: object
-              title: Signatures
+              description: |-
+                A map of user ID to a map of key ID to signed JSON object.
               additionalProperties:
                 type: object
                 additionalProperties: