From 854b649f2ea1c2c981a1e4e6fcd06d56ecb7400f Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Thu, 7 Jan 2010 07:36:32 +0000
Subject: [PATCH] added 'minimum' in wrong place

[Imported from Trac: page NewMutableEncodingDesign, version 12]
---
 NewMutableEncodingDesign.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/NewMutableEncodingDesign.md b/NewMutableEncodingDesign.md
index 8ffcb92..0ebf21e 100644
--- a/NewMutableEncodingDesign.md
+++ b/NewMutableEncodingDesign.md
@@ -166,7 +166,7 @@ Or, if the pubkey is short enough, include it in the cap rather than
 requiring the client to fetch a copy:
 
  * (1K) writecap = K-bit random string = privkey
- * (3K) readcap = H(writecap)[:K] + pubkey
+ * (minimum 3K) readcap = H(writecap)[:K] + pubkey
  * verifycap = pubkey
  * storage-index = H(pubkey)
 
@@ -183,7 +183,7 @@ is present in all caps, it's easy to insert arbitrary intermediate levels. It
 doesn't even change the way the existing caps are used:
 
  * (1K) writecap = K-bit random string = privkey
- * (minimum 3K) readcap = H(writecap)[:K] + H(pubkey)
+ * (3K) readcap = H(writecap)[:K] + H(pubkey)
  * (3K) traversalcap: H(readcap)[:K] + H(pubkey)
  * verifycap = H(pubkey)
  * storage-index = truncated verifycap