From 6fcbd71b18ff550c1c2aafff11c658e59af03855 Mon Sep 17 00:00:00 2001
From: warner <>
Date: Wed, 15 Jul 2009 08:03:36 +0000
Subject: [PATCH] minor formatting changes

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

diff --git a/NewCapDesign.md b/NewCapDesign.md
index cdf0566..e92df5c 100644
--- a/NewCapDesign.md
+++ b/NewCapDesign.md
@@ -18,11 +18,11 @@ established sense). To make them real, we need to:
  * 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?
- * according to #683, a URI !!!identifies!!! a resource, but does not
+ * according to #683, a URI **identifies** a resource, but does not
    necessarily provide enough information to actually access it (i.e. if you
    have a URI and somebody pointed you at a file, you could confidently tell
    them whether or not it was the right file, but if you only have the URI,
-   nyou might not be able to find the file without additional information). If
+   then you might not be able to find the file without additional information). If
    the cap has both identifying and location information, it's called a URL.
  * Tahoe filecaps are meant to be URLs (they are intended to provide location
    information), but to really make that work, you also need to define which
@@ -52,7 +52,8 @@ established sense). To make them real, we need to:
    precise about that drag. The best design would be a single short
    non-word-breaking string. The next best will be to have a large
    non-word-breaking string at the start and end, with smaller segments (if
-   necessary) in the middle.
+   necessary) in the middle. Note that `tahoe:` is an easy target, but
+   `x-tahoe:` is not (you'd have to double-click on the "x").
  * Usable in a browser. Specifically, it should be easy to actually use a
    filecap that you get in email or IM, and many email/IM clients will look
    for http URLs and make them clickable. If tahoe filecaps start with
@@ -115,5 +116,5 @@ established sense). To make them real, we need to:
    mean `tahoe://grid1234/IR/cryptobits`. Something like
    `tahoe://grid1234/D/MR/cryptobits` should reference
    `tahoe://grid1234/MR/cryptobits`. (#403)
- * #102 has notes on dircaps
+ * #102 and #217 have notes on dircaps