Update `CHANGES` files, other minor whitespace and documentation issues.

2 files changed, 34 insertions, 14 deletions

diff --git a/docs/CHANGES b/docs/CHANGES
index 958845114..5eb8cdb94 100644
--- a/docs/CHANGES
+++ b/docs/CHANGES
@@ -8,6 +8,26 @@ CHANGES BETWEEN 2.11.0 and 2.11.1
       additional means to protect against malformed input.
 
 
+  II. MISCELLANEOUS
+
+    - Cmake support  has been  further improved.   To do  that various
+      backward-incompatible  changes were  necessary; please  see file
+      `CMakeLists.txt` for more details.
+
+    - Since version  2.11.0, a  C99 compiler  is necessary  to compile
+      FreeType.
+
+    - The experimental  'COLR' v1 API  has been updated to  the latest
+      OpenType standard 1.9.
+
+    - The `apinames` tool got a new  option `-wV` to output an OpenVMS
+      Linker Option File.
+
+    - VMS support was updated.
+
+    - MS Visual Studio support was added to build the demo programs.
+
+
 ======================================================================
 
 CHANGES BETWEEN 2.10.4 and 2.11.0
diff --git a/docs/INSTALL b/docs/INSTALL
index d53b8ff5e..be56e02c5 100644
--- a/docs/INSTALL
+++ b/docs/INSTALL
@@ -9,19 +9,19 @@ I. Prerequisites and dependencies
 
   FreeType is a low level C library  that only depends on the standard
   C library with very few platform-dependent optimizations utilized at
-  build time.  Any  C89-compliant compiler  should be able  to compile
+  build time.  Any  C99-compliant compiler  should be able  to compile
   FreeType.  System libraries,  such as  zlib,  Gzip,  bzip2,  Brotli,
   and libpng,  might  be  used  to handle  compressed fonts  or decode
   embedded PNG glyphs.
 
   FreeType  auto-configuration scripts  should be  able to detect  the
   prerequisites if the necessary headers are available  at the default
-  locations.  Otherwise,  modify  `include/freetype/config/ftoption.h'
+  locations.  Otherwise,  modify  `include/freetype/config/ftoption.h`
   to control how the FreeType library gets built.  Normally, you don't
   need to change anything.
 
   Applications have very limited control over FreeType's behaviour  at
-  run-time;  look at the documentation of function `FT_Property_Set'.
+  run-time;  look at the documentation of function `FT_Property_Set`.
 
 
 II. Normal installation and upgrades
@@ -32,7 +32,7 @@ II. Normal installation and upgrades
     This also includes MacOS, Cygwin, MinGW + MSYS, Mingw-w64 + MSYS2,
     and possibly other, similar environments.
 
-    Please read `INSTALL.UNIX' to install or upgrade FreeType  2 on  a
+    Please read `INSTALL.UNIX` to install or upgrade FreeType  2 on  a
     Unix system.   Note  that  you  *need*  GNU  Make   for  automatic
     compilation,  since other make tools won't work (this includes BSD
     Make).
@@ -48,7 +48,7 @@ II. Normal installation and upgrades
     Windows, OS/2, and BeOS,  including MinGW* (without MSYS*), Visual
     C++, Borland C++, and more.
 
-    Instructions are provided in the file `INSTALL.GNU'.
+    Instructions are provided in the file `INSTALL.GNU`.
 
 
   3. Other build tools and platforms.
@@ -57,27 +57,27 @@ II. Normal installation and upgrades
     the  corresponding instruction files  in  the FreeType root folder
     or the builds/ sub-folder.
 
-      CMake   :: see CMakeLists.txt for more information
-      Meson   :: see meson.build for more information
-      MSBuild :: see builds/windows/vc2010/freetype.vcxproj
-      MMS     :: see vms_make.com and docs/INSTALL.VMS
+      CMake   :: see `CMakeLists.txt` for more information
+      Meson   :: see `meson.build` for more information
+      MSBuild :: see `builds/windows/vc2010/freetype.vcxproj`
+      MMS     :: see `vms_make.com` and `docs/INSTALL.VMS`
 
 
   4. With an IDE Project File (e.g., for Visual Studio or CodeWarrior)
 
-    We provide a  small number of `project files'  for various IDEs to
+    We provide a  small number of 'project files'  for various IDEs to
     automatically build  the library as  well.  Note that  these files
     are not actively supported by FreeType developers,  they can break
     or become obsolete.
 
-    To find them, have a  look at the content of the `builds/<system>'
+    To find them, have a  look at the content of the `builds/<system>`
     directory, where <system> stands for your OS or environment.
 
 
   5. From you own IDE, or own Makefiles
 
     If  you  want  to  create   your  own  project  file,  follow  the
-    instructions   given  in  the   `INSTALL.ANY'  document   of  this
+    instructions   given  in  the   `INSTALL.ANY`  document   of  this
     directory.
 
 
@@ -86,7 +86,7 @@ III. Custom builds of the library
 
   Customizing the compilation  of FreeType is easy, and  allows you to
   select only the components of  the font engine that you really need.
-  For more details read the file `CUSTOMIZE'.
+  For more details read the file `CUSTOMIZE`.
 
 
 ----------------------------------------------------------------------
@@ -97,7 +97,7 @@ III. Custom builds of the library
       https://makepp.sourceforge.net
 
     for more information;  you need version 2.0 or newer, and you must
-    pass option `--norc-substitution'.
+    pass option `--norc-substitution`.
 
 ----------------------------------------------------------------------