From 4ea1f6c7f84a6f70a184a0e33a0b35ba4950839a Mon Sep 17 00:00:00 2001 From: Arash Esbati Date: Wed, 27 Jul 2022 19:59:25 +0200 Subject: [PATCH] ; * doc/lispref/tips.texi (Documentation Tips): Fix typos. (Bug#56802) --- doc/lispref/tips.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi index e15ed0cb7cd..1b256f752a3 100644 --- a/doc/lispref/tips.texi +++ b/doc/lispref/tips.texi @@ -692,7 +692,7 @@ with curved single quotes (@t{‘..’}). There are two exceptions: write @code{t} and @code{nil} without surrounding punctuation. For example: @example - CODE can be ‘lambda’, nil, or t. +CODE can be ‘lambda’, nil, or t. @end example @noindent @@ -851,7 +851,7 @@ find an alternate phrasing that conveys the meaning. @item Try to avoid using abbreviations such as ``e.g.'' (for ``for example''), ``i.e.'' (for ``that is''), ``no.'' (for ``number''), -``c.f.'' (for ``in contrast to'') and ``w.r.t.'' (for ``with respect +``cf.'' (for ``in contrast to'') and ``w.r.t.'' (for ``with respect to'') as much as possible. It is almost always clearer and easier to read the expanded version.@footnote{We do use these occasionally, but try not to overdo it.} -- 2.39.2