Modernize comment

Author: mdboom

Include/internal/pycore_magic_number.h

@@ -10,25 +10,20 @@ extern "C" {
 
 /*
 
-Magic word to reject .pyc files generated by other Python versions.
+Magic number to reject .pyc files generated by other Python versions.
 It should change for each incompatible change to the bytecode.
 
+PYC_MAGIC_NUMBER must change whenever the bytecode emitted by the compiler may
+no longer be understood by older implementations of the eval loop (usually due
+to the addition of new opcodes).
+
 The value of CR and LF is incorporated so if you ever read or write
 a .pyc file in text mode the magic number will be wrong; also, the
 Apple MPW compiler swaps their values, botching string constants.
 
-There were a variety of old schemes for setting the magic number.
-The current working scheme is to increment the previous value by
-10.
-
-Starting with the adoption of PEP 3147 in Python 3.2, every bump in magic
-number also includes a new "magic tag", i.e. a human readable string used
-to represent the magic number in __pycache__ directories.  When you change
-the magic number, you must also set a new unique magic tag.  Generally this
-can be named after the Python major version of the magic number bump, but
-it can really be anything, as long as it's different than anything else
-that's come before.  The tags are included in the following table, starting
-with Python 3.2a0.
+There were a variety of old schemes for setting the magic number. Starting with
+Python 3.11, Python 3.n starts with magic number 2900+50n. Within each minor
+version, the magic number is incremented by 1 each time the file format changes.
 
 Known values:
  Python 1.5:   20121
@@ -86,9 +81,7 @@ Known values:
                         introduce POP_JUMP_IF_FALSE and POP_JUMP_IF_TRUE
                           #4715)
     Python 3.2a1: 3160 (add SETUP_WITH #6101)
-                  tag: cpython-32
     Python 3.2a2: 3170 (add DUP_TOP_TWO, remove DUP_TOPX and ROT_FOUR #9225)
-                  tag: cpython-32
     Python 3.2a3  3180 (add DELETE_DEREF #4617)
     Python 3.3a1  3190 (__class__ super closure changed)
     Python 3.3a1  3200 (PEP 3155 __qualname__ added #13448)
@@ -269,14 +262,8 @@ Known values:
     You should always use the *upcoming* tag. For example, if 3.12a6 came out
     a week ago, I should put "Python 3.12a7" next to my new magic number.
 
-MAGIC must change whenever the bytecode emitted by the compiler may no
-longer be understood by older implementations of the eval loop (usually
-due to the addition of new opcodes).
-
-Starting with Python 3.11, Python 3.n starts with magic number 2900+50n.
-
-Whenever MAGIC_NUMBER is changed, the ranges in the magic_values array
-in PC/launcher.c must also be updated.
+Whenever PYC_MAGIC_NUMBER is changed, the ranges in the magic_values array in
+PC/launcher.c must also be updated.
 
 */