From bc3c7bd5daceb00a2cfda755a2ed751a86fd738a Mon Sep 17 00:00:00 2001
From: warner <>
Date: Mon, 7 Sep 2009 21:40:33 +0000
Subject: [PATCH] [Imported from Trac: page NewCapDesign, version 11]

---
 NewCapDesign.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/NewCapDesign.md b/NewCapDesign.md
index 9a690a2..2d005c2 100644
--- a/NewCapDesign.md
+++ b/NewCapDesign.md
@@ -87,13 +87,13 @@ established sense). To make them real, we need to:
 
 ## make them long enough to be secure
 
-We want filecaps to be as possible, but no shorter. There are
+We want filecaps to be as short as possible, but no shorter. There are
 several lower bounds on the length:
 
  * confidentiality: A large computing effort should not be able
    to obtain the plaintext of a tahoe file without knowing the
    readcap. We require reasonable margin against improvements in
-   hardware speed and organization efficiency/motivation of
+   hardware speed and organizational efficiency/motivation of
    distributed efforts (e.g. could a million PS3 owners break a
    filecap?). This currently implies a 128 bit confidentiality
    field.