Adding DOI of the next GIPPtools 2023.163 release.

src/docs/asciidoc/articles/ReleaseHistory.adoc

@@ -27,7 +27,12 @@ NOTE: Releases are named after the date of their release. The first number
 :Security:   pass:quotes[*Security:*]
 
 
-== Release {package-release}
+//== Release {package-release}
+
+== Release 2023.163
+
+Please cite this release as:  +
+_Lendl, Christof (2023), GIPPtools, Version 2023.163, doi:10.5281/zenodo.8027730_
 
 === {Fixed}
 
@@ -377,7 +382,7 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
 
 === {Changed}
 
-* Added a `config` subdirectory to the GIPPtools distribution. At the moment
+* Added a `config` subdirectory to the GIPPtools distribution. Currently,
   it only contains a copy of the latest `leap-seconds.list` file. In the
   future it will also contain things such as default settings or user
   preferences.
@@ -395,8 +400,8 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
 === {Changed}
 
 * Added an expiration date to the internal leap second table so that
-  GIPPtool utilities will not accidentally apply outdated leap second
-  corrections. As a consequence, the Cube conversion tools (`cube2ascii`,
+  GIPPtool utilities will not accidentally apply an outdated leap second
+  correction. As a consequence, the Cube conversion tools (`cube2ascii`,
   `cube2mseed` and `cube2segy`) will refuse to process a file if the
   available leap second information is outdated (with respect to the Cube
   input). The `cubeinfo` program will output a warning. Utilities processing
@@ -424,9 +429,8 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
   single precision floating-point encoding.
 
 * Repaired the `--record-size` command line option of the `cube2mseed`
-  utility, which was not accepting any number at all. Cause was an internal
-  integer overflow when comparing the given record size with a build-in,
-  upper limit.
+  utility, which was rejecting numbers. Cause was an internal integer
+  overflow when comparing the given record size with a build-in, upper limit.
 
 * Updated the `cube2segy` utility to use the same Cube I/O subroutines as
   `cube2ascii` and `cube2mseed`. Due to the (internal) change the utility
@@ -547,7 +551,7 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
   erroneously compensate a future leap second the moment it is announced via
   satellite and not starting at the time when the new leap second will happen.
   Unfortunately, pending (new) leap seconds are usually announce via GPS
-  satellite many weeks in advance of the actual change... +
+  satellite many weeks in advance of the actual change… +
   A workaround was added to the GIPPtools to compensate for the premature
   leap second correction.
 
@@ -641,7 +645,7 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
 === {Added}
 
 * `Mseed2mseed` now understands the keyword _RESET_ when parsing actions in
-  a rule file or at the command line. Use the new keyword to clear/remove id
+  a rule file or at the command line. Use the new keyword to clear/remove ID
   values in miniSEED header fields.
 
 * The utilities `cube2segy` and `mseed2segy` can now cache the (internal)
@@ -937,7 +941,7 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
 === {Added}
 
 * New `edl2edl` utility, which can be used to selectively modify miniSEED
-  header fields such as e.g. station, channel and network id. You can also
+  header fields such as e.g. station, channel and network ID. You can also
   use it to change the record size, byte order or encoding scheme of a
   miniSEED file.
 
@@ -1033,7 +1037,7 @@ CAUTION: Only use this algorithm for worst case scenarios, where a user
 
 ****
 NOTE: Everything before the year 2008 does not deserve the name "_release_",
-      was non-public, preliminary or only in use internally at the GFZ. More
+      was non-public, preliminary, or only in use internally at the GFZ. More
       detailed information is shrouded in the fog of history...
 ****