summary refs log tree commit diff
diff options
context:
space:
mode:
authorRichard van der Hoff <richard@matrix.org>2018-05-23 15:39:52 +0100
committerRichard van der Hoff <richard@matrix.org>2018-05-23 15:39:52 +0100
commit2df8c3139ab7be10af4aaa750bbdc4ad39209583 (patch)
tree07974e70d7c40c6e38d9683280e5e305c5cdc14b
parentmention public_baseurl (diff)
downloadsynapse-2df8c3139ab7be10af4aaa750bbdc4ad39209583.tar.xz
minor post-review tweaks
Diffstat (limited to '')
-rw-r--r--docs/consent_tracking.md6
-rw-r--r--docs/server_notices.md4
2 files changed, 5 insertions, 5 deletions
diff --git a/docs/consent_tracking.md b/docs/consent_tracking.md
index 66beb9263b..9dc0093888 100644
--- a/docs/consent_tracking.md
+++ b/docs/consent_tracking.md
@@ -81,9 +81,9 @@ should be a matter of `pip install Jinja2`. On debian, try `apt-get install
 python-jinja2`.
 
 Once this is complete, and the server has been restarted, try visiting
-`https://<server>/_matrix/consent`. If configuration has been done correctly,
-this should give an error "Missing string query parameter 'u'". It is now
-possible to manually construct URIs where users can give their consent.
+`https://<server>/_matrix/consent`. If correctly configured, this should give
+an error "Missing string query parameter 'u'". It is now possible to manually
+construct URIs where users can give their consent.
 
 ### Constructing the consent URI
 
diff --git a/docs/server_notices.md b/docs/server_notices.md
index 9896881389..8e18e3d95d 100644
--- a/docs/server_notices.md
+++ b/docs/server_notices.md
@@ -4,7 +4,7 @@ Server Notices
 'Server Notices' are a new feature introduced in Synapse 0.30. They provide a
 channel whereby server administrators can send messages to users on the server.
 
-They are used as part of the communication of the server polices (see
+They are used as part of communication of the server polices(see
 [consent_tracking.md](consent_tracking.md)), however the intention is that 
 they may also find a use for features such as "Message of the day".
 
@@ -32,7 +32,7 @@ Synapse configuration
 Server notices come from a specific user id on the server. Server
 administrators are free to choose the user id - something like `server` is
 suggested, meaning the notices will come from
-`@server:<your_server_name>`. Once the server notices user is configured, that
+`@server:<your_server_name>`. Once the Server Notices user is configured, that
 user id becomes a special, privileged user, so administrators should ensure
 that **it is not already allocated**.