mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-04-08 20:34:10 +02:00
Merge c12fbe4540 into f62aa09e60
This commit is contained in:
commit
b5d0eb51c6
|
|
@ -0,0 +1 @@
|
||||||
|
Fix typos, formatting, wording. Contributed by @HarHarLinks.
|
||||||
1
changelogs/internal/newsfragments/2318.clarification
Normal file
1
changelogs/internal/newsfragments/2318.clarification
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
Fix typos, formatting, wording. Contributed by @HarHarLinks.
|
||||||
|
|
@ -65,7 +65,7 @@ description = "Home of the Matrix specification for decentralised communication"
|
||||||
# Everything below this are Site Params
|
# Everything below this are Site Params
|
||||||
|
|
||||||
[params]
|
[params]
|
||||||
copyright = "The Matrix.org Foundation CIC"
|
copyright = "The Matrix.org Foundation C.I.C."
|
||||||
|
|
||||||
[params.version]
|
[params.version]
|
||||||
# must be one of "unstable", "current", "historical"
|
# must be one of "unstable", "current", "historical"
|
||||||
|
|
|
||||||
|
|
@ -3418,7 +3418,7 @@ This specification describes the following relationship types:
|
||||||
* [Event replacements](#event-replacements).
|
* [Event replacements](#event-replacements).
|
||||||
* [Event annotations](#event-annotations-and-reactions).
|
* [Event annotations](#event-annotations-and-reactions).
|
||||||
* [Threads](#threading).
|
* [Threads](#threading).
|
||||||
* [References](#reference-relations)
|
* [References](#reference-relations).
|
||||||
|
|
||||||
#### Aggregations of child events
|
#### Aggregations of child events
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -107,7 +107,7 @@ flag to `true`.
|
||||||
```
|
```
|
||||||
|
|
||||||
{{% boxes/note %}}
|
{{% boxes/note %}}
|
||||||
Clients which are acutely aware of threads (they do not render threads, but are otherwise
|
Clients which are aware of threads (they do not render threads, but are otherwise
|
||||||
aware of the feature existing in the spec) can treat rich replies to an event with a `rel_type`
|
aware of the feature existing in the spec) can treat rich replies to an event with a `rel_type`
|
||||||
of `m.thread` as a threaded reply, for conversation continuity on the threaded client's side.
|
of `m.thread` as a threaded reply, for conversation continuity on the threaded client's side.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -31,7 +31,7 @@ paths:
|
||||||
|
|
||||||
The body of the request should be the content object of the event; the
|
The body of the request should be the content object of the event; the
|
||||||
fields in this object will vary depending on the type of event. See
|
fields in this object will vary depending on the type of event. See
|
||||||
[Room Events](/client-server-api/#room-events) for the m. event specification.
|
[Room Events](/client-server-api/#room-events) for the `m.` event specification.
|
||||||
|
|
||||||
Homeservers MUST allow clients to send `m.room.redaction` events with this
|
Homeservers MUST allow clients to send `m.room.redaction` events with this
|
||||||
endpoint for all room versions. In rooms with a version older than 11 they
|
endpoint for all room versions. In rooms with a version older than 11 they
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,7 @@ properties:
|
||||||
type: object
|
type: object
|
||||||
type:
|
type:
|
||||||
description: The type of event. This SHOULD be namespaced similar to Java package
|
description: The type of event. This SHOULD be namespaced similar to Java package
|
||||||
naming conventions e.g. 'com.example.subdomain.event.type'
|
naming conventions e.g. `com.example.subdomain.event.type`
|
||||||
type: string
|
type: string
|
||||||
required:
|
required:
|
||||||
- type
|
- type
|
||||||
|
|
|
||||||
|
|
@ -49,7 +49,7 @@
|
||||||
</tr>
|
</tr>
|
||||||
{{ if $state_key }}
|
{{ if $state_key }}
|
||||||
<tr>
|
<tr>
|
||||||
<th>State key</th>
|
<th>State key:</th>
|
||||||
<td>{{ $state_key.description | markdownify }}</td>
|
<td>{{ $state_key.description | markdownify }}</td>
|
||||||
</tr>
|
</tr>
|
||||||
{{ end }}
|
{{ end }}
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue