diff --git a/specification/rooms/v3.rst b/specification/rooms/v3.rst
index 040a7ff40..e5b0c44c7 100644
--- a/specification/rooms/v3.rst
+++ b/specification/rooms/v3.rst
@@ -63,7 +63,7 @@ Event IDs
    should be using. By removing the use of a dedicated event ID, servers are required
    to track the hashes on an event to determine its ID.
 
-The event ID is the reference hash of the event encoded using `Unpadded Base64`_,
+The event ID is the `reference hash`_ of the event encoded using `Unpadded Base64`_,
 prefixed with ``$``. A resulting event ID using this approach should look similar to
 ``$CD66HAED5npg6074c6pDtLKalHjVfYb2q4Q3LZgrW6o``.
 
@@ -108,13 +108,14 @@ to the change in event format:
   ``events_default`` in the power levels). However, servers should not apply or send
   redactions to clients until both the redaction event and original event have been
   seen, and are valid. Servers should only apply redactions to events where the
-  origin sender's domains match, or the sender has the appropriate permissions per
-  the power levels.
+  sender's domains match, or the sender of the redaction has the appropriate
+  permissions per the power levels.
 
 
-The remaining rules are the same as room version 1.
+The remaining rules are the same as `room version 1 <v1.html#authorization-rules>`_.
 
 
 .. _`Unpadded Base64`:  ../../appendices.html#unpadded-base64
 .. _`Canonical JSON`: ../../appendices.html#canonical-json
 .. _`Signing Events`: ../../server_server/unstable.html#signing-events
+.. _`reference hash`: ../../server_server/unstable.html#reference-hashes
diff --git a/specification/server_server_api.rst b/specification/server_server_api.rst
index 6eaf74e0d..f5831639c 100644
--- a/specification/server_server_api.rst
+++ b/specification/server_server_api.rst
@@ -281,6 +281,8 @@ Transactions are limited in size; they can have at most 50 PDUs and 100 EDUs.
 
 {{transactions_ss_http_api}}
 
+.. _`Persistent Data Unit schema`:
+
 PDUs
 ----
 
@@ -1050,11 +1052,13 @@ been given a redacted version of the event. To enforce this, the receiving
 server should use the redacted copy it calculated rather than the full copy it
 received.
 
+.. _`reference hashes`:
+
 Calculating the reference hash for an event
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The *reference hash* of an event covers the essential fields of an event,
-includuing content hashes. It is calculated as follows.
+including content hashes. It is calculated as follows.
 
 1. The event is put through the redaction algorithm.