summaryrefslogtreecommitdiff
path: root/doc/spec/proposals
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
commitdeea710cdcbbcdafa9fd67f8f9a7e85f7fdbb652 (patch)
treec543cb2ca5444ce688ab5cab9a3a851b2ebd4a31 /doc/spec/proposals
parentd2308279120276720281472005b3beea39798634 (diff)
downloadtor-deea710cdcbbcdafa9fd67f8f9a7e85f7fdbb652.tar.gz
tor-deea710cdcbbcdafa9fd67f8f9a7e85f7fdbb652.zip
Fix typo in 001-process.txt
Diffstat (limited to 'doc/spec/proposals')
-rw-r--r--doc/spec/proposals/001-process.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt
index 2ed0a3066b..636ba2c2fa 100644
--- a/doc/spec/proposals/001-process.txt
+++ b/doc/spec/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.