summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2021-04-04 08:39:48 -0700
committerKaz Kylheku <kaz@kylheku.com>2021-04-04 08:39:48 -0700
commit00e219c51f256a5f716c15fdf1e03d00f4a9e894 (patch)
treecaaf5c0d9c1c31020bc8fd461564d0a7d42cf3b8
parentd6ed9b823336c7d03b41a4ebb793232362c4aec9 (diff)
downloadtxr-00e219c51f256a5f716c15fdf1e03d00f4a9e894.tar.gz
txr-00e219c51f256a5f716c15fdf1e03d00f4a9e894.tar.bz2
txr-00e219c51f256a5f716c15fdf1e03d00f4a9e894.zip
doc: vice versa formatting.
* txr.1: Under "Treatment of Literals", fix lack of close double quote in italicization of vice versa.
-rw-r--r--txr.12
1 files changed, 1 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index 7e7dcd7e..40bdf2ed 100644
--- a/txr.1
+++ b/txr.1
@@ -75199,7 +75199,7 @@ No such de-duplication is performed for interpreted code.
Consequently, code which depends on multiple occurrences of these objects to be
distinct objects may behave correctly when interpreted, but misbehave when
compiled. Or
-.IR "vice versa .
+.IR "vice versa" .
One example is code which modifies a string literal.
Under compilation, the change will affect all occurrences of that literal
that have been merged into one object. Another example is an