[doc] miscellaneous punctuation fixes

doc/faq.rst

@@ -47,7 +47,7 @@ Is a passed-through GPU required?
 
 No. The IDD can create an SDR display using software processing when it cannot
 use a Windows render adapter. A hardware adapter is strongly recommended for
-lower latency, higher refresh rates, HDR and cadence scheduling.
+lower latency, higher refresh rates, HDR, and cadence scheduling.
 
 The Linux client still needs an EGL-capable host graphics driver. Direct
 DMA-BUF import depends on the host GPU and driver; the client falls back to a

doc/idd_diagnostics.rst

@@ -13,11 +13,11 @@ Right-click the helper and open the log directory. The files are stored in:
 
 Collect these files when reporting an IDD fault:
 
-* ``looking-glass-idd.txt`` -- display creation, GPU selection, modes,
+* ``looking-glass-idd.txt``: display creation, GPU selection, modes,
   transport and frame scheduling;
-* ``looking-glass-input.txt`` -- direct keyboard and mouse device activity;
-* ``looking-glass-idd-service.txt`` -- service and driver control requests;
-* ``looking-glass-idd-helper.txt`` -- configuration, topology and user
+* ``looking-glass-input.txt``: direct keyboard and mouse device activity;
+* ``looking-glass-idd-service.txt``: service and driver control requests; and
+* ``looking-glass-idd-helper.txt``: configuration, topology and user
   notifications.
 
 Each log rotates through suffixes ``.1`` to ``.4``. Include the current file

doc/overview.rst

@@ -60,7 +60,7 @@ For a new installation, use:
 * the matching Looking Glass IDD in the Windows guest; and
 * SPICE only for the fallback or convenience services you need.
 
-Use matching Looking Glass releases for the current client, IDD and OBS plugin.
+Use matching Looking Glass releases for the current client, IDD, and OBS plugin.
 The shared-memory protocol changes between releases and incompatible components
 will not connect. Users of the legacy host application must use the complete
 matching B7 stack described below.