all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: 56802@debbugs.gnu.org
Subject: bug#56802: 29.0.50; [PATCH] Cosmetic change to doc/lispref/tips.texi
Date: Wed, 27 Jul 2022 19:59:25 +0200	[thread overview]
Message-ID: <864jz2e8si.fsf@gnu.org> (raw)

Hi all,

may I suggest this trivial change to tips.texi:

--8<---------------cut here---------------start------------->8---
diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index d03698d354..9faf3f33ba 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -712,7 +712,7 @@ Documentation Tips
 punctuation.  For example:

 @example
- CODE can be `lambda', nil, or t.
+CODE can be `lambda', nil, or t.
 @end example

 Note that when Emacs displays these doc strings, Emacs will usually
@@ -868,7 +868,7 @@ Documentation Tips
 @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.}
--8<---------------cut here---------------end--------------->8---

It deletes a leading space in an example and fixes the abbreviation
cf. which is to my knowledge short for the Latin confer/conferatur,
i.e., only one word.

Best, Arash





             reply	other threads:[~2022-07-27 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 17:59 Arash Esbati [this message]
2022-07-27 19:22 ` bug#56802: 29.0.50; [PATCH] Cosmetic change to doc/lispref/tips.texi Eli Zaretskii
2022-07-27 19:46   ` Arash Esbati

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864jz2e8si.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=56802@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.