Skip to content

Commit 8280b86

Browse files
Grammar fixes
Co-Authored-By: Andrew Morgan <[email protected]>
1 parent d48fea8 commit 8280b86

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

proposals/2162-signaling-errors-at-bridges.md

+5-4
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ There are some common reasons why an error occurred. These are encoded in the
5151
totally legitimate to “handle” an event by doing nothing and not throwing this
5252
error. It is at the discretion of the bridge author to find a good balance
5353
between informing the user and preventing unnecessary spam. Throwing this
54-
error only for some subtypes of an event if fine.
54+
error only for some subtypes of an event is fine.
5555

5656
* `m.bridge_unavailable` The homeserver couldn't reach the bridge.
5757

@@ -130,7 +130,7 @@ error(s) having a sender of the same bridge as the revocation event are
130130
considered revoked. Clients can show a revoke error e.g. as “Delivered to
131131
Discord at 14:52.” besides the original event.
132132

133-
On an unsuccessful retry the bridge may edit the errors content to reflect the
133+
On an unsuccessful retry the bridge may edit the error's content to reflect the
134134
new state, e.g. because the type of error changed or to communicate the new
135135
time.
136136

@@ -163,14 +163,15 @@ Example of the new retry events:
163163
Overview of the relations between the different event types:
164164

165165
```
166+
m.references
166167
________________ _____________________
167168
| | | |
168169
| Original Event |-+-| Bridge Error |
169170
|________________| | |_____________________|
170171
| _____________________
171172
| | |
172173
+-| Retry Request |
173-
m.references | |_____________________|
174+
| |_____________________|
174175
| _____________________
175176
| | |
176177
+-| Bridge Error Revoke |
@@ -187,7 +188,7 @@ otherwise.
187188
In the case the bridge is down or otherwise disconnected from the homeserver, it
188189
naturally has no way to inform its users about the unavailability. In this case
189190
the homeserver can stand in as an agent for the bridge and answer requests in
190-
its responsibility.
191+
its absence.
191192

192193
For this to happen, the homeserver will send out a bridge error event in the
193194
moment a transaction delivery to the bridge failed. The clients at this point

0 commit comments

Comments
 (0)