Rearrange canonical crosslinks

1 files changed, 5 insertions, 5 deletions

diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md
index e503ece..394999d 100644
--- a/spec/tor-spec/negotiating-channels.md
+++ b/spec/tor-spec/negotiating-channels.md
@@ -483,8 +483,6 @@ relays SHOULD send the addresses that they have advertised
 in their router descriptors.
 Bridges and clients SHOULD send none of their own addresses.
 
-> The OTHERADDR and 
-
 For the `TIME` field,
 relays send a (big-endian) integer
 holding the number of seconds since the Unix epoch.
@@ -504,7 +502,9 @@ clocks are skewed.
 Initiators MAY use "other OR's address" field
 to help learn which address their connections may be originating from,
 if they do not know it;
-and to learn whether the peer will treat the current connection as canonical.
+and to learn whether the peer will treat the current connection as
+canonical.
+(See [Canonical connections](./creating-circuits.md#canonical-connections))
 
 Implementations SHOULD NOT trust these values unconditionally,
 especially when they come from non-authorities,
@@ -512,5 +512,5 @@ since the other party can lie about the time
 or the IP addresses it sees.
 
 Initiators SHOULD use "this OR's address" to make sure
-that they have connected to another OR at its canonical address.
-(See [Canonical connections](./creating-circuits.md#canonical-connections))
+that they have connected to another OR at its
+[canonical address](./creating-circuits.md#canonical-connections).