From: Bjarni Ingi Gislason <bjarniig@simnet.is>
To: util-linux@vger.kernel.org
Subject: documents (andoc files), spelling mistakes
Date: Mon, 31 Jul 2023 00:13:38 +0000 [thread overview]
Message-ID: <ZMb8snehCDMT4tS6@localhost> (raw)
From "codespell"
./misc-utils/uuidd.8.adoc:28: gurantees ==> guarantees
-.-.
./term-utils/scriptlive.1.andoc:
*Be careful!* Do not forget that the typescript may contains arbitrary
commands. It is recommended to use *"scriptreplay --stream in --log-in
typescript"* (or with *--log-io* instead of *--log-in*) to verify the
typescript before it is executed by *scriptlive*.
contains -> contain
-.-.
The distance between sentences is hardcoded in the sources.
-.-.
Separate the sentences and subordinate clauses;
each begins on a new line.
See man-pages(7) ("Conventions for source file layout") and "info
groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier,
when they belong to the same line,
and the same phrase.
Man pages (with groff, man (man-db)):
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
reply other threads:[~2023-07-31 0:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZMb8snehCDMT4tS6@localhost \
--to=bjarniig@simnet.is \
--cc=util-linux@vger.kernel.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.
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).