Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Commit ceab5a4

Browse files
authored
Fix 2 typos in docs/log_contexts.md (#10795)
1 parent 63f28e4 commit ceab5a4

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

changelog.d/10795.doc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Correct 2 typographical errors in the *Log Contexts* documentation.

docs/log_contexts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Logcontexts are also used for CPU and database accounting, so that we
1010
can track which requests were responsible for high CPU use or database
1111
activity.
1212

13-
The `synapse.logging.context` module provides a facilities for managing
13+
The `synapse.logging.context` module provides facilities for managing
1414
the current log context (as well as providing the `LoggingContextFilter`
1515
class).
1616

@@ -351,7 +351,7 @@ and the awaitable chain is now orphaned, and will be garbage-collected at
351351
some point. Note that `await_something_interesting` is a coroutine,
352352
which Python implements as a generator function. When Python
353353
garbage-collects generator functions, it gives them a chance to
354-
clean up by making the `async` (or `yield`) raise a `GeneratorExit`
354+
clean up by making the `await` (or `yield`) raise a `GeneratorExit`
355355
exception. In our case, that means that the `__exit__` handler of
356356
`PreserveLoggingContext` will carefully restore the request context, but
357357
there is now nothing waiting for its return, so the request context is

0 commit comments

Comments
 (0)