summary refs log tree commit diff
path: root/docs/log_contexts.md
diff options
context:
space:
mode:
authorreivilibre <38398653+reivilibre@users.noreply.github.com>2021-09-10 16:33:36 +0100
committerGitHub <noreply@github.com>2021-09-10 16:33:36 +0100
commitceab5a4bfa5a447b674a7e593217849770bfa7d5 (patch)
treee88620dfbd142d752892bec1622891a3b26d6621 /docs/log_contexts.md
parentHandle room upgrades for spaces (#10774) (diff)
downloadsynapse-ceab5a4bfa5a447b674a7e593217849770bfa7d5.tar.xz
Fix 2 typos in docs/log_contexts.md (#10795)
Diffstat (limited to '')
-rw-r--r--docs/log_contexts.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/log_contexts.md b/docs/log_contexts.md
index d49dce8830..cb15dbe158 100644
--- a/docs/log_contexts.md
+++ b/docs/log_contexts.md
@@ -10,7 +10,7 @@ Logcontexts are also used for CPU and database accounting, so that we
 can track which requests were responsible for high CPU use or database
 activity.
 
-The `synapse.logging.context` module provides a facilities for managing
+The `synapse.logging.context` module provides facilities for managing
 the current log context (as well as providing the `LoggingContextFilter`
 class).
 
@@ -351,7 +351,7 @@ and the awaitable chain is now orphaned, and will be garbage-collected at
 some point. Note that `await_something_interesting` is a coroutine, 
 which Python implements as a generator function.  When Python
 garbage-collects generator functions, it gives them a chance to 
-clean up by making the `async` (or `yield`) raise a `GeneratorExit`
+clean up by making the `await` (or `yield`) raise a `GeneratorExit`
 exception. In our case, that means that the `__exit__` handler of
 `PreserveLoggingContext` will carefully restore the request context, but
 there is now nothing waiting for its return, so the request context is