wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

revert example which was corect first time; fix rst

Browse source
This commit is contained in:
Matthew Hodgson 2018-09-01 02:44:53 +01:00
parent 2c0b45fd14
commit db302b66ca
2 changed files with 9 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

3
api/server-server/definitions/event-schemas/m.direct_to_device.yaml
View file

@ -51,8 +51,7 @@ allOf:
The contents of the messages to be sent. These are arranged in 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. 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. The device ID may also be *, meaning all known devices for the user.
example: |- example: {
{
"alice@example.org": { "alice@example.org": {
"IWHQUZUIAH": { "IWHQUZUIAH": {
"algorithm": "m.megolm.v1.aes-sha2", "algorithm": "m.megolm.v1.aes-sha2",

2
specification/server_server_api.rst
View file

@ -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. EDU. There are no PDUs or Federation Queries involved.
Each send-to-device message should be sent to the destination server using 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}} {{definition_ss_event_schemas_m_direct_to_device}}