doc/config: fix inline literals
Since commit 6cf378f, asciidoc backticks are now inline literals; therefore quoting {tilde} inside them is wrong (this instance was missed in 6cf378f because it happened on a parallel line of development). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
May 2, 2012 at 19:43 UTC
9a7b0bca366d8d9b3b26f1bb1a75885780c0f0e4
1 file changed
+2
-2
Documentation/config.txt
+2
-2
@@ -95,8 +95,8 @@ included file is expanded immediately, as if its contents had been
95
found at the location of the include directive. If the value of the
96
`include.path` variable is a relative path, the path is considered to be
97
relative to the configuration file in which the include directive was
98
-found. The value of `include.path` is subject to tilde expansion: `{tilde}/`
99
-is expanded to the value of `$HOME`, and `{tilde}user/` to the specified
98
+found. The value of `include.path` is subject to tilde expansion: `~/`
99
+is expanded to the value of `$HOME`, and `~user/` to the specified
100
user's home directory. See below for examples.
101
102
Example