aboutsummaryrefslogtreecommitdiff
path: root/proposals/001-process.txt
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2009-05-05 15:47:36 +0200
committerNick Mathewson <nickm@torproject.org>2009-05-05 11:12:41 -0400
commitefa8fceff925c598400aae44b16569647820f869 (patch)
tree6b5592394a6f34af5e3b3a28b12d063f92c3e499 /proposals/001-process.txt
parent6bd09d50762cf8a73d378a911817e540347361dd (diff)
downloadtorspec-efa8fceff925c598400aae44b16569647820f869.tar.gz
torspec-efa8fceff925c598400aae44b16569647820f869.zip
Fix typo in 001-process.txt
Diffstat (limited to 'proposals/001-process.txt')
-rw-r--r--proposals/001-process.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/001-process.txt b/proposals/001-process.txt
index 2ed0a30..636ba2c 100644
--- a/proposals/001-process.txt
+++ b/proposals/001-process.txt
@@ -93,7 +93,7 @@ What should go in a proposal:
what the proposal's about, what it does, and about what state it's in.
After the Overview, the proposal becomes more free-form. Depending on its
- the length and complexity, the proposal can break into sections as
+ length and complexity, the proposal can break into sections as
appropriate, or follow a short discursive format. Every proposal should
contain at least the following information before it is "ACCEPTED",
though the information does not need to be in sections with these names.