More text for relnote

ReleaseNotes_4.7.md

@@ -1,6 +1,6 @@
 # HAMLIB 4.7 - Release Notes
 
-The release brings new equipment support, bug fixes/code cleanups, and some
+This release brings new equipment support, bug fixes/code cleanups, and some
 changes to ease transition to 5.0
 
 ## New equipment support
@@ -13,21 +13,33 @@ changes to ease transition to 5.0
 ## Bug Fixes & Code cleanups
 - Codebase conforms to ISO/IEC 9899:2024 (-std=c23)
 - Reduce gripes from cppcheck and other static analyzers
-- Function rig_get_conf() is deprecated and will be removed in 5.0.
-  Use rig_get_conf2() instead.
+- Functions rig_get_conf(), rot_get_conf() and amp_get_conf() are deprecated and
+  will be removed in 5.0. Use xyz_get_conf2() instead. See issue #924
 - (TBD)
 
 ## Build/install Changes
-- POSIX thread(PTHREADS) support required
+- POSIX threads(PTHREADS) support required
 - C compiler - Supported compilers unchanged; c11 or c17 recommended,
   c23 optional. 5.0 will require at least c11.
 
 ## Changes for 5.0
+HAMLIB 5.0 will make some major changes to the Application Binary Interface(ABI) that will
+require changes to some applications, and at least recompilation/linking for all
+apps. Most(All, I hope) of these source changes can be made/tested/debugged incrementally
+with 4.7, making the transition much easier. The Application Programming Interface(API)
+does not change.
 
 ### Storage restructuring
-HAMLIB 5.0 will move many data items/structures out of rig_struct into
-separate, calloc'ed buffers. This changes many of the methods for accessing
-HAMLIB internal data.
+HAMLIB 5.0 will move many data items/structures out of rig_struct into separate,
+calloc'ed buffers. This changes many of the methods for accessing HAMLIB internal
+data. It also removes some obsolete items, and restructures/resizes others.
 
 ### Include files
+Along with the moves to separate storage, the definitions of these data structures
+will be moved out of hamlib/rig.h to their own include files. These `.h` files also
+define macros to get the address of said structures.
 
+### The good news
+If your application only calls the Hamlib API routines, then nothing needs to change.
+If your application only uses configuration items like names, speeds, etc, it may be
+easiest to change over to using rig_set_conf(). and let Hamlib handle the internals.

ReleaseNotes_5.0.md

@@ -7,7 +7,9 @@ changes to the Application Binary Interface(ABI).
 - TBD
 
 ## Build changes
-- No more K&R C - need at least c11 compiler support.
+- No more K&R C - C compiler needs at least c11 capability.
+- Functions rig_get_conf(), rot_get_conf() and amp_get_conf() have been removed.
+  See issue #924.
 - shortfreq_t changed to int?
 
 ## Application changes