revert example which was corect first time; fix rst

api/server-server/definitions/event-schemas/m.direct_to_device.yaml

@@ -51,17 +51,16 @@ allOf:
               The contents of the messages to be sent.  These are arranged in
               a map of user IDs to a map of device IDs to message bodies.
               The device ID may also be *, meaning all known devices for the user.
-            example: |-
-              {
-                "alice@example.org": {
-                  "IWHQUZUIAH": {
-                    "algorithm": "m.megolm.v1.aes-sha2",
-                    "room_id": "!Cuyf34gef24t:localhost",
-                    "session_id": "X3lUlvLELLYxeTx4yOVu6UDpasGEVO0Jbu+QFnm0cKQ",
-                    "session_key": "AgAAAADxKHa9uFxcXzwYoNueL5Xqi69IkD4sni8LlfJL7qNBEY..."
-                  }
+            example: {
+              "alice@example.org": {
+                "IWHQUZUIAH": {
+                  "algorithm": "m.megolm.v1.aes-sha2",
+                  "room_id": "!Cuyf34gef24t:localhost",
+                  "session_id": "X3lUlvLELLYxeTx4yOVu6UDpasGEVO0Jbu+QFnm0cKQ",
+                  "session_key": "AgAAAADxKHa9uFxcXzwYoNueL5Xqi69IkD4sni8LlfJL7qNBEY..."
                 }
               }
+            }
         required:
           - sender
           - type

specification/server_server_api.rst

@@ -1018,7 +1018,7 @@ The server API for send-to-device messaging is based on the following
 EDU. There are no PDUs or Federation Queries involved.
 
 Each send-to-device message should be sent to the destination server using
-the following EDU::
+the following EDU:
 
 {{definition_ss_event_schemas_m_direct_to_device}}