Proofing done

2 views
Skip to first unread message

Gary Hinson

unread,
Sep 30, 2025, 12:20:53 AMSep 30
to hyperg...@googlegroups.com
Last week was intensive - hard work yet satisfying: I completed a painstaking check of the page proofs and submitted a tidy stack of corrections at the weekend ... so now I look forward to hearing from you and other readers about the remaining errors that evidently escaped my notice and ended up in print.

This week, I am correcting my working copy of the hyperglossary for the errors located by proofreading that were in my original manuscript submitted back in May (oops), as opposed to those accidentally created by the editors and typesetters (who have a tough job!).  On top of that, I'm continuing to add new entries as they emerge from the mists.  Not so intensive, the routine maintenance counts as fun for this self-confessed word-geek.  

I'm not sure, yet, how to handle corrections, additions and other changes post-publication.  What do you think?  Ideas welcome.

Kind regards/Ngā mihi,

________________________________________

Gary Hinson CEO of IsecT Ltd

Information risk and security consulting

ISO27k  Audit  ISMS templates and policies
Pragmatic Security Metrics (with Krag Brotby)
Cybersecurity Hyperglossary (forthcoming!)

________________________________________

Joel McLean

unread,
Sep 30, 2025, 1:31:43 AMSep 30
to hyperg...@googlegroups.com

Boardgames do this by having a published errata on the website.

You could do the same; maintain a digital errata PDF that acts as supplementary to the book – but then also when Edition 2 is ready, you can incorporate the errata.

The errata would always need to be published, as obviously people’s first edition books will not change; but you could stop maintaining an errata for first edition, and if applicable, only maintain an errata for second edition.

 

Kind Regards,

 

Joel McLean

Cyber Security and Product Development Manager

Australia’s First Tier IV Data Centre

https://www.micron21.com/

  1300 769 972

  03 9751 7618

  0407 888 429

  joel....@micron21.com


 

Follow us on Twitter and https://m21status.com for important service and system updates.

This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must not use, copy, distribute or disclose it to anyone other than the addressee. If you have received this message in error please return the message to the sender by replying to it and then delete the message from your computer.

--
You received this message because you are subscribed to the Google Groups "Cybersecurity hyperglossary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hyperglossar...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hyperglossary/CAPRmHF5jG%3DLtAbmuSKi2HXaeZgeQLyy-7sd%3DJimSRMx6sY3hYQ%40mail.gmail.com.

Rob Slade, greatgrandpa and widower

unread,
Sep 30, 2025, 11:54:24 AMSep 30
to hyperg...@googlegroups.com
On Mon, Sep 29, 2025 at 9:20 PM Gary Hinson <ga...@isect.com> wrote:

This week, I am correcting my working copy of the hyperglossary for the errors located by proofreading that were in my original manuscript submitted back in May (oops), as opposed to those accidentally created by the editors and typesetters

My favorite (from my first book) was when the typesetters "corrected" "80x86" (those old enough to remember pre-Pentium Intel CPUs will understand) to "80[multiplication sign]86." 

--
Psalm 142:4, Ezekiel 24:16,18; Matthew 13:12; Isaiah 57:1; Genesis 2:18; 2 Corinthians 2:7,8; John 13:35; Proverbs 25:20; James 2:15,16; Proverbs 24:11-12, Jeremiah 45:3, Deuteronomy 28: 65-67, Isaiah 38:15, Psalm 69:20, Revelation 9:6, Number 11:15
Uuk klah ma, Rob.  U huk witas hluucsma, Gloria  Wikaah chachimhiy.

======================

Rob Slade, greatgrandpa and widower

unread,
Sep 30, 2025, 11:56:51 AMSep 30
to hyperg...@googlegroups.com
On Mon, Sep 29, 2025 at 10:31 PM Joel McLean <joel....@micron21.com> wrote:


You could do the same; maintain a digital errata PDF that acts as supplementary to the book – but then also when Edition 2 is ready, you can incorporate the errata.

The errata would always need to be published, as obviously people’s first edition books will not change; but you could stop maintaining an errata for first edition, and if applicable, only maintain an errata for second edition.


I maintained the dictionary in HTML, and did this when it was published.  (Unfortunately, they never did publish a second edition ...)

Gary Hinson

unread,
Sep 30, 2025, 8:19:06 PMSep 30
to hyperg...@googlegroups.com
Thanks guys.

Yes, some form of online corrections/amendment thing for the published book is a good idea Joel.  

A second edition depends on how well the first is received by the community, and sales of course.  But I already know for sure there will be plenty of changes and who-knows-how-many newly-coined terms to add.  Keeping up is all part of the fun!

Kind regards/Ngā mihi,

PS  Rob I'm just popping out on the number four[multuplication sign]number four farm bike to check on the animals.

________________________________________

Gary Hinson CEO of IsecT Ltd

Information risk and security consulting

ISO27k  Audit  ISMS templates and policies
Pragmatic Security Metrics (with Krag Brotby)
Cybersecurity Hyperglossary (forthcoming!)

________________________________________

--
You received this message because you are subscribed to the Google Groups "Cybersecurity hyperglossary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hyperglossar...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages