From 1e888d6a3ff81b0d29e266c75aa5de8eef406c11 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Tue, 14 Mar 2023 12:36:48 -0400 Subject: [PATCH] Fix typos. Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- changelogs/client_server/newsfragments/1464.clarification | 2 +- content/appendices.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/changelogs/client_server/newsfragments/1464.clarification b/changelogs/client_server/newsfragments/1464.clarification index 940fec84..a9a6865b 100644 --- a/changelogs/client_server/newsfragments/1464.clarification +++ b/changelogs/client_server/newsfragments/1464.clarification @@ -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). diff --git a/content/appendices.md b/content/appendices.md index 366d1796..4d04d35f 100644 --- a/content/appendices.md +++ b/content/appendices.md @@ -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