Bring some things up to date.

Still nowhere close to done.

ReleaseNotes_4.7.md

@@ -1,32 +1,35 @@
 # HAMLIB 4.7 - Release Notes (WIP)                        2025-12-01(?)
 
+*This is very much a first cut - nothing is set in concrete or inviolate - n3gb*
+
 This release brings new equipment support, bug fixes/code cleanups, and some
 changes to ease transition to 5.0
 
 ## New equipment support
-- Yaesu FTX-1 Optima/Field - Work in progress, waiting for official
-  documentation from Yaesu
+- Yaesu FTX-1 Optima/Field - Work in progress
 - Drake R8/R8A/R8B - new, revised backend
 - AF6SA WRC rotator
 - GUOHETEC PMR-171 & Q900 moved to separate backend
 
-## Bug Fixes & Code cleanups
+## Bug fixes & code cleanups
 - Codebase conforms to ISO/IEC 9899:2024 (-std=c23)
 - Reduce gripes from cppcheck and other static analyzers
 - Functions `rig_get_conf()`, `rot_get_conf()` and `amp_get_conf()` are deprecated and
   will be removed in 5.0. Use `..._get_conf2()` instead. See issue
   [#924](https://github.com/Hamlib/Hamlib/issues/924).
+- Documentation brought up to date.
 - (TBD)
 
-## Build/install Changes
+## Build/install changes
 - POSIX threads(PTHREADS) support required
+- Many fixes for building the optional language bindings
 - 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
+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.
 
@@ -43,6 +46,8 @@ Along with the moves to separate storage, the definitions of these data structur
 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.
 
+Prelinary versions of these files are also part of 4.7 for pre-emptive use.
+
 ### 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

ReleaseNotes_5.0.md

@@ -1,5 +1,7 @@
 # HAMLIB 5.0 - Release Notes (DRAFT)                           2026-12-01(target)
 
+*This more of a list of possibilities than a true document - a strawman only*
+
 This major release includes a restructuring of HAMLIB internal storage, forcing
 changes to the Application Binary Interface(ABI).