From 684215670ff1ebb3e05df7b8c4c13912be80f621 Mon Sep 17 00:00:00 2001
From: clokep <clokep@users.noreply.github.com>
Date: Fri, 8 Sep 2023 13:48:35 +0000
Subject: deploy: 5c8870cb28cc98d0b7a310b5dd2fade7ff45743d

---
 develop/development/contributing_guide.html                | 2 +-
 develop/development/synapse_architecture/faster_joins.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

(limited to 'develop/development')

diff --git a/develop/development/contributing_guide.html b/develop/development/contributing_guide.html
index b328bba158..1bf8403da6 100644
--- a/develop/development/contributing_guide.html
+++ b/develop/development/contributing_guide.html
@@ -317,7 +317,7 @@ useful to reproduce this locally.</p>
 <h4 id="using-docker"><a class="header" href="#using-docker">Using Docker</a></h4>
 <p>The easiest way to do so is to run Postgres via a docker container. In one
 terminal:</p>
-<pre><code class="language-shell">docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgress -p 5432:5432 postgres:14
+<pre><code class="language-shell">docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgres -p 5432:5432 postgres:14
 </code></pre>
 <p>If you see an error like</p>
 <pre><code>docker: Error response from daemon: driver failed programming external connectivity on endpoint nice_ride (b57bbe2e251b70015518d00c9981e8cb8346b5c785250341a6c53e3c899875f1): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use.
diff --git a/develop/development/synapse_architecture/faster_joins.html b/develop/development/synapse_architecture/faster_joins.html
index d60c159d11..dcb761384f 100644
--- a/develop/development/synapse_architecture/faster_joins.html
+++ b/develop/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>
-- 
cgit 1.5.1