summary refs log tree commit diff
path: root/docs/log_contexts.md
diff options
context:
space:
mode:
authorPatrick Cloke <clokep@users.noreply.github.com>2023-09-08 09:47:36 -0400
committerGitHub <noreply@github.com>2023-09-08 09:47:36 -0400
commit5c8870cb28cc98d0b7a310b5dd2fade7ff45743d (patch)
treef8a8392b2f04e764daa3a7170078496087e4e147 /docs/log_contexts.md
parentFix bug with new task scheduler using lots of CPU. (#16278) (diff)
downloadsynapse-5c8870cb28cc98d0b7a310b5dd2fade7ff45743d.tar.xz
Fix-up incorrect spellings in docs. (#16282)
Diffstat (limited to 'docs/log_contexts.md')
-rw-r--r--docs/log_contexts.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/log_contexts.md b/docs/log_contexts.md

index cb15dbe158..9d087d11ef 100644 --- a/docs/log_contexts.md +++ b/docs/log_contexts.md
@@ -86,7 +86,7 @@ So we have stopped processing the request (and will probably go on to start processing the next), without clearing the logcontext. To circumvent this problem, synapse code assumes that, wherever you have -an awaitable, you will want to `await` it. To that end, whereever +an awaitable, you will want to `await` it. To that end, wherever functions return awaitables, we adopt the following conventions: **Rules for functions returning awaitables:**