mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-26 21:14:09 +01:00
Fix typos.
Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
This commit is contained in:
parent
df20dae390
commit
1e888d6a3f
|
|
@ -1 +1 @@
|
|||
Disambiguate using property names with dots in them during push rule processiong, per [MSC3873](https://github.com/matrix-org/matrix-spec-proposals/pull/3873).
|
||||
Disambiguate using property names with dots in them during push rule processing, per [MSC3873](https://github.com/matrix-org/matrix-spec-proposals/pull/3873).
|
||||
|
|
|
|||
|
|
@ -945,7 +945,7 @@ uses the following rules:
|
|||
## Dot-separated property paths
|
||||
|
||||
It is useful to express the "path" to an event property by concatenating property
|
||||
names with dots, e.g. `content.body` would represent the a `body` property in the
|
||||
names with dots, e.g. `content.body` would represent a `body` property in the
|
||||
event's `content`.
|
||||
|
||||
To handle ambiguity when a property name contains a dot, any literal dot or
|
||||
|
|
@ -954,7 +954,7 @@ property `m.relates_to` in the `content` would be expressed as
|
|||
`content.m\.relates_to`.
|
||||
|
||||
It is recommended that implementations do not redundantly escape characters, as
|
||||
other escape sequences are reserve for future use.
|
||||
other escape sequences are reserved for future use.
|
||||
|
||||
## Security Threat Model
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue