Remove mention of where the code is

Author: erikjohnston

docs/log_contexts.md

@@ -573,12 +573,11 @@ the tokio runtime, the current logcontext must be captured and carried along, so
 that log records emitted while the future is polled (including any `log::`
 records from dependencies, and any Python invoked back from Rust) are attributed
 correctly. Don't use a bare `tokio::spawn`. Instead use
-`LogContextHandle::capture(py)` plus `LogContextHandle::scope` (in
-`rust/src/logging/context.rs`), which capture the caller's logcontext from the
-Python side and record it on the spawned task; this is what `create_deferred`
-does. `current_context()` returns the task's captured context first, so
-`LoggingContextFilter` — and therefore `pyo3-log` — sees the right context on
-worker threads without any per-log-record work.
+`LogContextHandle::capture(py)` plus `LogContextHandle::scope`, which capture
+the caller's logcontext from the Python side and record it on the spawned task;
+this is what `create_deferred` does. `current_context()` returns the task's
+captured context first, so `LoggingContextFilter` — and therefore `pyo3-log` —
+sees the right context on worker threads without any per-log-record work.
 
 ## Debugging logcontext issues
 

synapse/logging/context.py

@@ -170,9 +170,9 @@ def __bool__(self) -> Literal[False]:
 def current_context() -> LoggingContextOrSentinel:
     """Get the current logging context.
 
-    The storage lives in the Rust extension (see `rust/src/logging/context.rs`),
-    which represents "no context" as `None`. This wrapper maps that to
-    `SENTINEL_CONTEXT`, so callers never see `None`.
+    The storage lives in the Rust extension, which represents "no context" as
+    `None`. This wrapper maps that to `SENTINEL_CONTEXT`, so callers never see
+    `None`.
     """
     context = _rust_current_context()
     return SENTINEL_CONTEXT if context is None else context

tests/synapse_rust/test_logcontext.py

@@ -13,7 +13,7 @@
 """Tests for logcontext attribution across the Python/Rust boundary.
 
 The current logcontext is stored on the Rust side
-(`synapse.synapse_rust.logcontext` / `rust/src/logging/context.rs`), visible
+(`synapse.synapse_rust.logcontext`), visible
 from both Python (reactor/threadpool threads) and Rust (tokio tasks). These
 tests exercise the two guarantees that gives us:
 

tests/util/test_logcontext.py

@@ -732,9 +732,9 @@ class LogContextErrorMessageTestCase(unittest.TestCase):
     """Tests asserting the exact messages passed to `logcontext_error`, and
     the conditions that trigger each one.
 
-    The implementation lives in Rust (`rust/src/logging/context.rs`). Downstream
-    log scraping depends on the wording and argument order of these messages, so
-    accidental changes must fail a test.
+    The implementation lives in Rust. Downstream log scraping depends on the
+    wording and argument order of these messages, so accidental changes must
+    fail a test.
     """
 
     def setUp(self) -> None: