From: David-Sarah Hopwood <david-sarah@jacaranda.org>
Date: Sun, 11 Nov 2012 16:04:23 +0000 (+0000)
Subject: docs/frontends/CLI.rst: fix markup of * and ?.
X-Git-Tag: allmydata-tahoe-1.10a1~42
X-Git-Url: https://git.rkrishnan.org/simplejson/components/%22file:/-?a=commitdiff_plain;h=4c91fa948df46110203f49221d18874eb8c9aca8;p=tahoe-lafs%2Ftahoe-lafs.git

docs/frontends/CLI.rst: fix markup of * and ?.

Signed-off-by: David-Sarah Hopwood <david-sarah@jacaranda.org>
---

diff --git a/docs/frontends/CLI.rst b/docs/frontends/CLI.rst
index 9783197b..34e90c94 100644
--- a/docs/frontends/CLI.rst
+++ b/docs/frontends/CLI.rst
@@ -56,7 +56,7 @@ functionality) and including versions for a number of dependent libraries,
 like Twisted, Foolscap, pycryptopp, and zfec. "``tahoe --version-and-path``"
 will also show the path from which each library was imported.
 
-On Unix systems, the shell expands filename wildcards (`` * and ? ``)
+On Unix systems, the shell expands filename wildcards — ``'*'`` and ``'?'`` —
 before the program is able to read them, which may produce unexpected
 results for many ``tahoe`` comands. We recommend, if you use wildcards,
 to start the path with "``./``", for example "``tahoe cp -r ./* somewhere:``".