From 9dee6d9233355b9a8010807aebb09a2fc4537312 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 24 Aug 2022 17:21:12 -0600 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- content/client-server-api/modules/reference_relations.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/client-server-api/modules/reference_relations.md b/content/client-server-api/modules/reference_relations.md index 52018caa..c29f9a47 100644 --- a/content/client-server-api/modules/reference_relations.md +++ b/content/client-server-api/modules/reference_relations.md @@ -12,7 +12,7 @@ implied meaning behind the reference, and is usually context-dependent. Such an example is the [key verification framework](#key-verification-framework) which uses reference relations to associate distinct events with a specific verification attempt. -When bundled, a reference relations appear as an object with a `chunk` field to +The aggregation format of `m.reference` relations consists of a single `chunk` property to indicate all the events which `m.reference` the event (the parent). Currently, only a single `event_id` field is present on the events in the `chunk`. @@ -24,7 +24,7 @@ messages. An example `m.reference` would be: -```json5 +```json { "content": { "m.relates_to": { @@ -39,7 +39,7 @@ An example `m.reference` would be: The [bundle](#aggregations) under `m.relations` would appear similar to the following: -```json5 +```json { "m.reference": { "chunk": [