From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: spelling; patch from jsg@
Date: Sun, 3 Jul 2022 09:36:30 -0500 (EST) [thread overview]
Message-ID: <33662efd6ca52cb4@mandoc.bsd.lv> (raw)
Log Message:
-----------
spelling; patch from jsg@
Modified Files:
--------------
mandoc:
mandoc.1
Revision Data
-------------
Index: mandoc.1
===================================================================
RCS file: /home/cvs/mandoc/mandoc/mandoc.1,v
retrieving revision 1.261
retrieving revision 1.262
diff -Lmandoc.1 -Lmandoc.1 -u -p -r1.261 -r1.262
--- mandoc.1
+++ mandoc.1
@@ -2320,7 +2320,7 @@ attempts to employ one of the characters
as an argument delimiter.
The escape sequence is ignored including the invalid opening delimiter
and the rest of the argument may appear as output text.
-While various charcters can be used as argument delimiters,
+While various characters can be used as argument delimiters,
using the apostrophe-quote character
.Pq Sq \(aq
is recommended for readability and robustness.
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2022-07-03 14:36 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=33662efd6ca52cb4@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/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 NNTP newsgroup(s).