summary refs log tree commit diff
path: root/docs
diff options
context:
space:
mode:
authorRichard van der Hoff <github@rvanderhoff.org.uk>2017-03-18 22:47:37 +0000
committerGitHub <noreply@github.com>2017-03-18 22:47:37 +0000
commitd78d08981a6b4f5fe2e2395050e411d0ceedfbb0 (patch)
tree0d1e47cf24be7b52703f1690f238fac1e63139ac /docs
parentLogcontext docs (diff)
downloadsynapse-d78d08981a6b4f5fe2e2395050e411d0ceedfbb0.tar.xz
log_contexts.rst: fix typos
Diffstat (limited to '')
-rw-r--r--docs/log_contexts.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/log_contexts.rst b/docs/log_contexts.rst
index a5f59745e6..ffe438c614 100644
--- a/docs/log_contexts.rst
+++ b/docs/log_contexts.rst
@@ -331,7 +331,7 @@ gathered:
             result = yield defer.gatherResults([d1, d2])
 
 In this case particularly, though, option two, of using
-``logcontext.preserve.fn`` almost certainly makes more sense, so that
+``logcontext.preserve_fn`` almost certainly makes more sense, so that
 ``operation1`` and ``operation2`` are both logged against the original
 logcontext. This looks like:
 
@@ -355,7 +355,7 @@ follow for any more exotic flows. It's hard not to wonder if we could have done
 something else.
 
 We're not going to rewrite Synapse now, so the following is entirely of
-acadamic interest, but I'd like to record some thoughts on an alternative
+academic interest, but I'd like to record some thoughts on an alternative
 approach.
 
 I briefly prototyped some code following an alternative set of rules. I think