diff --git a/doxygen/dox/AppDbgging.dox b/doxygen/dox/AppDbgging.dox
index a4126965f55..d009b01ab54 100644
--- a/doxygen/dox/AppDbgging.dox
+++ b/doxygen/dox/AppDbgging.dox
@@ -26,11 +26,9 @@ performance, datatype conversion, data space conversion, and data filters. The c
 included on a per-package basis and enabled at runtime by an environment variable.
 
 \subsection subsec_adddbg_intro_trace API Tracing
-All API calls made by an application can be displayed and include formal argument names
-and actual values and the function return value. This code is also conditionally included
-at compile time and enabled at runtime.
+Tracing API calls has been removed from the library.
 
-The statistics and tracing can be displayed on any output stream (including streams opened by
+The statistics can be displayed on any output stream (including streams opened by
 the shell) with output from different packages even going to different streams.
 
 \section sec_adddbg_msg Error Messages
diff --git a/doxygen/dox/TableSpec.dox b/doxygen/dox/TableSpec.dox
index 79866043a92..dcc8a342a13 100644
--- a/doxygen/dox/TableSpec.dox
+++ b/doxygen/dox/TableSpec.dox
@@ -2,7 +2,7 @@
 /** \page TBLSPEC HDF5 Table Specification Version 1.0
 The HDF5 specification defines the standard objects and storage for the standard HDF5
 objects. (For information about the HDF5 library, model and specification, see the HDF
-documentation.) This document is an additional specification do define a standard profile
+documentation.) This document is an additional specification to define a standard profile
 for how to store tables in HDF5. Table data in HDF5 is stored as HDF5 datasets with standard
 attributes to define the properties of the tables.
 
diff --git a/doxygen/dox/Unicode.dox b/doxygen/dox/Unicode.dox
index fbb83f635b8..8195ccf4caa 100644
--- a/doxygen/dox/Unicode.dox
+++ b/doxygen/dox/Unicode.dox
@@ -111,7 +111,8 @@ predictable ways. There is an apparent consensus in the Linux community that "UT
 
 <b>Mac OS</b> systems generally handle UTF-8 encodings correctly.
 
-<b>Windows</b> systems use a different Unicode encoding, UCS-2 (discussed in this UTF-16 article) at
+<b>Windows</b> systems use a different Unicode encoding, <a href="https://en.wikipedia.org/wiki/UTF-16">UCS-2</a>
+(discussed in this UTF-16 article) at
 the system level. Within an HDF5 file and application on a Windows system, UTF-8 encoding should
 work correctly and as expected. Problems may arise, however, when that UTF-8 encoding is exposed
 directly to the Windows system. For example:
diff --git a/doxygen/dox/VFLTechNote.dox b/doxygen/dox/VFLTechNote.dox
index 130259baf9c..535001a2eb5 100644
--- a/doxygen/dox/VFLTechNote.dox
+++ b/doxygen/dox/VFLTechNote.dox
@@ -548,7 +548,7 @@ own free list is used. The special value H5MF_NOLIST indicates that the library
 attempt to maintain a free list for that particular object type, instead calling the file driver
 each time an object of that type is freed.
 
-Mappings predefined in the 'H5FDpublic.h' file are:
+Mappings predefined in the 'H5FDdevelop.h' file are:
 <table>
 <tr>
 <td>#H5FD_FLMAP_SINGLE</td><td>All memory usage types are mapped to a single free list.
@@ -661,7 +661,7 @@ A driver must specify two functions to transfer data from the library to the fil
 <table>
 <tr>
 <td><code>static herr_t read (H5FD_t *file, H5FD_mem_t type, hid_t dxpl, haddr_t addr, hsize_t size, void *buf)</code></td>
-<td>The read function reads data from file file beginning at address addr and continuing
+<td>The read function reads data from file beginning at address addr and continuing
 for size bytes into the buffer buf supplied by the caller.</td>
 </tr>
 <tr>