From ccb2b71e42389ef35e96c75ae5b0f94375343620 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Wed, 11 Sep 2013 06:32:25 +0000
Subject: [PATCH] "lafs" is more the protocol, "tahoe" is more the Python
 implementation

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

diff --git a/NewCapDesign.md b/NewCapDesign.md
index e422575..db460d9 100644
--- a/NewCapDesign.md
+++ b/NewCapDesign.md
@@ -22,8 +22,8 @@ Ticket #432 was the starting point: it contained a list of features.
 Kevin Reid points out that the Tahoe calls URIs are not actually URIs (in the
 established sense). To make them real, we need to:
 
- * make them start with `x-tahoe:` or `tahoe:` (or `lafs:`),
-   register `tahoe:` with IANA (#418) (#683)
+ * make them start with `x-lafs:` or `lafs:`,
+   register `lafs:` with IANA (#418) (#683)
  * understand how URI/URL/URNs are built, decide about hierarchical segments
    vs non-hierarchical segments. What's magical about a leading double-slash?
    Do we need one?