Skip to content

Commit a4c474e

Browse files
Fix casing typo
Co-authored-by: witchent <[email protected]>
1 parent 3367f56 commit a4c474e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

proposals/2716-batch-send-historical-messages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -524,7 +524,7 @@ presentation of room versions in clients, and it would require support for
524524
retrospectively specifying the `predecessor` of the current room when you
525525
retrospectively import history. Currently `predecessor` is in the immutable
526526
`m.room.create` event of a room, so cannot be changed retrospectively - and
527-
doing so in a safe and race-free manner sounds Hard. A big problem with this
527+
doing so in a safe and race-free manner sounds hard. A big problem with this
528528
approach is if you just want to inject a few old lost messages - eg if you're
529529
importing a mail or newsgroup archive and you stumble across a lost mbox with a
530530
few msgs in retrospect, you wouldn't want or be able to splice a whole new room

0 commit comments

Comments
 (0)