summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArash Esbati <arash@gnu.org>2022-07-27 19:59:25 +0200
committerEli Zaretskii <eliz@gnu.org>2022-07-27 22:20:41 +0300
commit4ea1f6c7f84a6f70a184a0e33a0b35ba4950839a (patch)
tree821838d49dc9c38a290d8c38746fd40592488d6a
parent970190b84485e4511b094546395a7e710f894fae (diff)
downloademacs-4ea1f6c7f84a6f70a184a0e33a0b35ba4950839a.tar.gz
; * doc/lispref/tips.texi (Documentation Tips): Fix typos. (Bug#56802)
-rw-r--r--doc/lispref/tips.texi4
1 files 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.}