[groff] 02/31: HACKING: Bump copyright year.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 28dfa1ec5860cbdb38ac33005d03fbcb06869526
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Wed Jul 10 09:22:10 2024 -0500

    HACKING: Bump copyright year.
    
    ...to reflect substanial addition of material discussing...
    
    ...copyright, and when to bump the year in the copyright notice.
    
    :-|
    
    Continues commit 90b15242d0, 6 July.
    
    Also fix wordo and tighten language.
---
 HACKING | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/HACKING b/HACKING
index b51b0761b..faf40f29f 100644
--- a/HACKING
+++ b/HACKING
@@ -1,4 +1,4 @@
-    Copyright 2022-2023 Free Software Foundation, Inc.
+    Copyright 2022-2024 Free Software Foundation, Inc.
 
     Copying and distribution of this file, with or without
     modification, are permitted in any medium without royalty provided
@@ -118,7 +118,7 @@ Updating Copyright Notices
   instead of a comma-separated list.  As far as GBR knows there is no
   hard rule that such ranges are interpreted exhaustively, and unless
   someone has a chronological record of changes to the file, a broken
-  sequence of copyright overage years makes little practical difference.
+  sequence of copyright coverage years makes little difference.
   Copyright protection extends to those portions of the work fixed in a
   tangible medium in the years declared in the copyright notice, except
   for those portions whose copyright durations have elapsed.  But these