From: Brian Gough <bjg@network-theory.co.uk>
To: emacs-orgmode@gnu.org
Cc: Barry Gidden <barryg@network-theory.co.uk>
Subject: final proofreading patches
Date: Wed, 08 Dec 2010 21:21:38 +0000 [thread overview]
Message-ID: <m3mxogq7tp.wl%bjg@network-theory.co.uk> (raw)
Hi. I just sent our final set of proofreading patches. For reference
the complete list is below, there were 25 in total.
--
Brian Gough
Network Theory Ltd,
Publishing Free Software Manuals --- http://www.network-theory.co.uk/
+ 03619e889bf061607785f092481dbfe36bcee9be correct doc typos
+ 04038c5a1f22ecf8219343e5ea80d1c7298edb90 more serious typos
+ 20ba1bd3800f5865cbbf27ae1d550efb892abd90 mismatched quotes
+ 67ff0e20cede3ae9afa332a6881184a5153c0881 make Nth consistent
+ 2c77e5b2a3b48708b2e0993fe773950332fd6dd2 correct language names, acronyms etc.
+ 246fdc680679a86c77c2736629711cd49e626fa2 correct grammar
+ e2a062e23efc44204a7ac124546f1f8b24524d32 use @result{} instead of --> (looks nicer)
+ c877cff82e6b88ddf8e0e3c8bfca08988aad2751 use macro for @LaTeX name
+ 993f9dc9423ffea980f74efea1adae152b7e7d05 make use of the provided @ie and @eg macros to fix the spacing
+ 03720efc58d37cbf16c6697d3647de7de144c32e fix commas that should be full stops, semicolons or emdashes
+ 4fe070423e44307dea9e37348187f7fa9985be34 fix plain text that looks better with markup
+ 3e3e3e036de59ab35147ede5f7f234626a4ae96b use kbd font
+ 20b1221c8ae3971bd34ea9f7b092944385935fa1 improvements to wording style
+ 07859f743f7c17bd1895feaa0fb4ac14cdeb9ed6 include explanations of how to look up a docstring
+ 62147b263d953cda67813e3ea914f2f6f67f4987 use a full sentence
+ bb75bc08045deda9d7216852b8c35d99faacdd97 tangling is not a widely-known term, describe it as literate programming
+ 19ba8a650b91265d31d0c5dfb20f67a872d4d6d0 make "time stamps" consistent with timestamps
+ 9e9260cd609f184d59207254737018dfab49f747 make explanation of keyword lines clearer
+ b3afbe555fdc233c5c1d84948b822421d091cebe use emdashes when needed
+ dc1d7e9c5300a043b7ed47728b2347dde7f6a290 put emacs functions in code font
+ c33bc9c261643853a3bf72b711d153cb78226a74 use code font for example footnote labels
+ c813b438bf54233f58c019fe67b13780a1cb69de fix missing word in math formatting section
+ b042807abbdd78a948c1f0d2e845836c208cb061 typo/grammar fix for .done CSS explanation
+ 54b3245810441906c8759bd82d251ef523ba8dbc explain how to check the default version of Org
+ cf1f46960b02b13ae704fdc1f29911c35f350724 add index entries
next reply other threads:[~2010-12-08 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 21:21 Brian Gough [this message]
2010-12-09 21:47 ` final proofreading patches Carsten Dominik
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=m3mxogq7tp.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=barryg@network-theory.co.uk \
--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).