From: Ian Nehera <delta29@shaw.ca>
To: emacs-orgmode@gnu.org
Subject: Possible small formatting change in manual (section 15.1)
Date: Tue, 13 Apr 2021 15:59:49 -0700 [thread overview]
Message-ID: <44928C24-3BE1-488A-8C9F-6F05ADAC01AF@shaw.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Hi, I was reading the org manual section on source code blocks and I
think there’s a small section where the clarity can be improved.
Section 15.1: Features Overview, first paragraph (line 16396 of org.org)
original: …Users can control how live they want each source code block…
proposed change 1: …control how [“live”] they want…
proposed change 2: …control [the “liveliness” of] each source…
When the paragraph first introduces the term “live code block”, it’s italicized. I think
it should stay italicized for the rest of that paragraph since it’s the introduction of the
term (I had to re-read the sentence a few times myself before it fully made sense).
Just a small suggestion; it wasn’t detrimental to my understanding or anything but
more of a small hiccup.
Best,
Ian
[-- Attachment #2: Type: text/html, Size: 2137 bytes --]
next reply other threads:[~2021-04-13 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 22:59 Ian Nehera [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-15 7:59 Possible small formatting change in manual (section 15.1) autofrettage
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44928C24-3BE1-488A-8C9F-6F05ADAC01AF@shaw.ca \
--to=delta29@shaw.ca \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).