doc: Latin overhaul.

* txr.1: Ensure all instances of vice versa are spellled
consistently without a dash and italicized. Italicize every
et cetera and one a priori.

1 files changed, 27 insertions, 16 deletions

diff --git a/txr.1 b/txr.1
index bebb783c..06266c8f 100644
--- a/txr.1
+++ b/txr.1
@@ -6512,7 +6512,7 @@ is a list, and
 occurs within
 .codn B .
 .IP -
-vice versa:
+.IR "vice versa" :
 .code B
 is text,
 .code A
@@ -6528,8 +6528,9 @@ are lists and are either identical, or one is
 found as substructure within the other.
 .PP
 The right hand side does not have to be a variable. It may be some other
-object, like a string, quasiliteral, regexp, or list of strings, et cetera. For
-instance
+object, like a string, quasiliteral, regexp, or list of strings,
+.IR "et cetera" .
+For instance
 
 .verb
   @(bind A "ab\etc")
@@ -7749,7 +7750,9 @@ This creates the possibility than an
 .code accept
 in horizontal context targets a vertical
 .code block
-or vice-versa, raising the question of how the input position
+or
+.IR "vice versa" ,
+raising the question of how the input position
 is treated.  The semantics of this is defined.
 
 If a horizontal-context
@@ -13671,7 +13674,7 @@ The
 operator produces a value which is a function.  Like in most other
 Lisps, functions are objects in \*(TL.  They can be passed to functions as
 arguments, returned from functions, aggregated into lists, stored in variables,
-et cetera.
+.IR "et cetera" .
 
 Note that the above syntax synopsis describes only the canonical
 parameter syntax which remains after parameter list macros are
@@ -14061,8 +14064,8 @@ If a symbol has bindings both in the variable and function namespace in scope,
 and is referenced by a dwim argument, this constitutes a conflict which is
 resolved according to two rules.  When nested scopes are concerned, then an
 inner binding shadows an outer binding, regardless of their kind.  An inner
-variable binding for a symbol shadows an outer or global function binding,
-and vice versa.
+variable binding for a symbol shadows an outer or global function binding, and
+.IR "vice versa" .
 
 If a symbol is bound to both a function and variable in the global namespace,
 then the variable binding is favored.
@@ -24664,7 +24667,8 @@ static slot, yet have that in their own instance.
 The slot type can be overridden. A structure type deriving from another
 type can introduce slots which have the same names as the supertype,
 but are of a different kind: an instance slot in the supertype
-can be replaced by a static slot in the derived type or vice versa.
+can be replaced by a static slot in the derived type or
+.IR "vice versa" .
 
 A structure type is associated with a static initialization function
 which may be used to store initial values into static slots. This function
@@ -24964,7 +24968,8 @@ these values to be stable can be defined with
 
 Initializers in base structures must be careful about assumptions about slot
 kinds, because derived structures can alter static slots to instance slots or
-vice versa. To avoid an unwanted initialization being applied to the
+.IR "vice versa" .
+To avoid an unwanted initialization being applied to the
 wrong kind of slot, initialization code can be made conditional on the
 outcome of
 .code static-slot-p
@@ -39004,7 +39009,9 @@ function performs a bitwise complement of
 When the one-argument form of lognot is used, then if
 .meta value
 is nonnegative,
-then the result is negative, and vice versa, according to the infinite-bit
+then the result is negative, and
+.IR "vice versa" ,
+according to the infinite-bit
 two's complement representation. For instance
 .code "(lognot -2)"
 is
@@ -47538,7 +47545,7 @@ value to be returned even though no operation has failed; that is to say, the
 streams "know" they are at the end of the data even though no read operation
 has failed. Code which depends on this will not work with streams which
 do not thus indicate the end-of-data
-.I a priori,
+.IR "a priori" ,
 but by means of a read operation which fails.
 
 The
@@ -57360,7 +57367,7 @@ function.
 These variables corresponds to the C constants
 .codn FTW_PHYS ,
 .codn FTW_MOUNT ,
-et cetera.
+.IR "et cetera" .
 
 Note that
 .code ftw-actionretval
@@ -57381,7 +57388,7 @@ error condition encountered.
 These variables correspond to the C constants
 .codn FTW_F ,
 .codn FTW_D ,
-et cetera.
+.IR "et cetera" .
 
 Not all of them are present. If the underlying platform doesn't have
 a given constant, then the corresponding variable doesn't exist in \*(TX.
@@ -57405,7 +57412,7 @@ the search and nonzero to stop.
 These variables correspond to the C constants
 .codn FTW_CONTINUE ,
 .codn FTW_STOP ,
-et cetera.
+.IR "et cetera" .
 
 .coNP Function @ ftw
 .synb
@@ -63318,7 +63325,9 @@ elements of this list specify the types of the fixed arguments;
 the remaining elements specify the variadic arguments.
 
 Note: variadic functions must not be called using a non-variadic
-descriptor, and vice versa, even if the return types and
+descriptor, and
+.IR "vice versa" ,
+even if the return types and
 argument types match.
 
 .TP* Example:
@@ -66378,7 +66387,9 @@ 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 vice versa. One example is code which modifies a string literal.
+compiled. Or
+.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
 expression like