aboutsummaryrefslogtreecommitdiff
path: root/proposals/187-allow-client-auth.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2011-10-25 19:09:37 -0400
committerRoger Dingledine <arma@torproject.org>2011-10-25 19:09:37 -0400
commit40b32dd1742753e5cf04d99a0f8852997975f084 (patch)
treeacdfda55961b4355bd323743f016212a7d585875 /proposals/187-allow-client-auth.txt
parent4036bd9cd1d43f9cfb28e4fdb198fbbce113c1fb (diff)
downloadtorspec-40b32dd1742753e5cf04d99a0f8852997975f084.tar.gz
torspec-40b32dd1742753e5cf04d99a0f8852997975f084.zip
fix a typo
Diffstat (limited to 'proposals/187-allow-client-auth.txt')
-rw-r--r--proposals/187-allow-client-auth.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/187-allow-client-auth.txt b/proposals/187-allow-client-auth.txt
index 5e71599..6a9e2da 100644
--- a/proposals/187-allow-client-auth.txt
+++ b/proposals/187-allow-client-auth.txt
@@ -27,7 +27,7 @@ Motivation:
easily. The client should prove to the bridge that it's
authorized to know about the bridge, before the bridge acts like a
bridge. If the client doesn't show knowledge of the proper
- secret, the bridge should at like an HTTPS server or a bittorrent
+ secret, the bridge should act like an HTTPS server or a bittorrent
tracker or something.
This proposal *does not* specify a way for clients to authorize