deploy: 88ba67eb91215a708f321e16559fe3c2c0d0a407

1 files changed, 1 insertions, 1 deletions

diff --git a/latest/development/synapse_architecture/faster_joins.html b/latest/development/synapse_architecture/faster_joins.html

index d60c159d11..dcb761384f 100644
--- a/latest/development/synapse_architecture/faster_joins.html
+++ b/latest/development/synapse_architecture/faster_joins.html
@@ -382,7 +382,7 @@ But don't want to send out sensitive data in other HS's events in this way.</p>
 <p>Suppose we discover after resync that we shouldn't have sent out one our events (not a prev_event) to a target HS. Not much we can do.
 What about if we didn't send them an event but shouldn't've?
 E.g. what if someone joined from a new HS shortly after you did? We wouldn't talk to them.
-Could imagine sending out the &quot;Missed&quot; events after the resync but... painful to work out what they shuld have seen if they joined/left.
+Could imagine sending out the &quot;Missed&quot; events after the resync but... painful to work out what they should have seen if they joined/left.
 Instead, just send them the latest event (if they're still in the room after resync) and let them backfill.(?)</p>
 <ul>
 <li>Don't do this currently.</li>