diff options
author | Patrick Cloke <clokep@users.noreply.github.com> | 2023-09-08 09:47:36 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-09-08 09:47:36 -0400 |
commit | 5c8870cb28cc98d0b7a310b5dd2fade7ff45743d (patch) | |
tree | f8a8392b2f04e764daa3a7170078496087e4e147 /docs/development | |
parent | Fix bug with new task scheduler using lots of CPU. (#16278) (diff) | |
download | synapse-5c8870cb28cc98d0b7a310b5dd2fade7ff45743d.tar.xz |
Fix-up incorrect spellings in docs. (#16282)
Diffstat (limited to 'docs/development')
-rw-r--r-- | docs/development/contributing_guide.md | 2 | ||||
-rw-r--r-- | docs/development/synapse_architecture/faster_joins.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/development/contributing_guide.md b/docs/development/contributing_guide.md index 698687b91f..4ae2fcfee3 100644 --- a/docs/development/contributing_guide.md +++ b/docs/development/contributing_guide.md @@ -266,7 +266,7 @@ The easiest way to do so is to run Postgres via a docker container. In one terminal: ```shell -docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgress -p 5432:5432 postgres:14 +docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgres -p 5432:5432 postgres:14 ``` If you see an error like diff --git a/docs/development/synapse_architecture/faster_joins.md b/docs/development/synapse_architecture/faster_joins.md index 1e6d585b00..2256c30239 100644 --- a/docs/development/synapse_architecture/faster_joins.md +++ b/docs/development/synapse_architecture/faster_joins.md @@ -264,7 +264,7 @@ But don't want to send out sensitive data in other HS's events in this way. 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 "Missed" events after the resync but... painful to work out what they shuld have seen if they joined/left. +Could imagine sending out the "Missed" 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.(?) - Don't do this currently. - If anyone who has received our messages sends a message to a HS we missed, they can backfill our messages |