aboutsummaryrefslogtreecommitdiff
path: root/proposals/326-tor-relay-well-known-uri-rfc8615.md
diff options
context:
space:
mode:
Diffstat (limited to 'proposals/326-tor-relay-well-known-uri-rfc8615.md')
-rw-r--r--proposals/326-tor-relay-well-known-uri-rfc8615.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/proposals/326-tor-relay-well-known-uri-rfc8615.md b/proposals/326-tor-relay-well-known-uri-rfc8615.md
index 2f820ea..7648162 100644
--- a/proposals/326-tor-relay-well-known-uri-rfc8615.md
+++ b/proposals/326-tor-relay-well-known-uri-rfc8615.md
@@ -1,6 +1,6 @@
```
Filename: 326-tor-relay-well-known-uri-rfc8615.md
-Title: The "tor-relay" Well-Known Resource Identifier
+Title: The "tor-relay" Well-Known Resource Identifier
Author: nusenu
Created: 14 August 2020
Status: Open
@@ -23,7 +23,7 @@ organization by pointing to its website: Tor relay/bridge contact information fi
under the specified URI, because attackers can not easily place these files at the given location.
* By publishing Tor relay IDs or hashed bridge IDs under this URI the website operator claims to be the responsible entity for these Tor relays/bridges.
-The verification of listed Tor relay/bridge IDs only succeeds if the claim can be verified bidirectionally
+The verification of listed Tor relay/bridge IDs only succeeds if the claim can be verified bidirectionally
(website -> relay/bridge and relay/bridge -> website).
* This URI is not related to Tor onion services.