Regenerate the laptop index and clean up the merged entries

Merging #12 and #13 together left the model-listing count at 31: both
PRs bumped it from 30 to 31 independently, so git took the identical
change once and the real total of 32 never landed. The repo-consistency
check caught it on master.

Also drops the empty patches/.gitkeep from the gxfp5187 entry, since
patches/README.md already keeps the directory, and replaces the em-dashes
the two entries brought in with plain punctuation.

Author: jedbillyb

devices/27c6:55b4/patches/0008-README-document-the-Goodix-55b4-fork-build-enroll-tu.patch

@@ -81,7 +81,7 @@ index 2e52403..41b8703 100644
 +
 +### If verify suddenly fails
 +
-+`verify-disconnected` / instant "Wrong" usually means a stale TLS session — run
++`verify-disconnected` / instant "Wrong" usually means a stale TLS session, so run
 +`sudo pkill -9 -x fprintd` to force a fresh cold handshake. If it persists, the
 +sensor PSK was likely rewritten (e.g. by a Windows Hello boot, which can't share
 +the sensor with Linux); re-enroll to re-provision it.

devices/gxfp5187/CREDITS

@@ -4,20 +4,20 @@ Driver and protocol reverse-engineering:
   Base: commit d7ed1db (branch main), against libfprint-2-tod1 1.94.7+tod1.
 
 Reference work this build relied on:
-  JJJollyjim — wireshark-goodix: Wireshark dissector for the GXFP5187 SPI
+  JJJollyjim - wireshark-goodix: Wireshark dissector for the GXFP5187 SPI
     protocol, with a sample SPI capture. The key protocol reference.
     https://github.com/JJJollyjim/wireshark-goodix
-  PeshalaDilshan — OpenGoodixSPI: experimental kernel driver for Goodix SPI
+  PeshalaDilshan - OpenGoodixSPI: experimental kernel driver for Goodix SPI
     sensors, GXFP5187 referenced.
     https://github.com/PeshalaDilshan/OpenGoodixSPI
-  lexakimov — goodix51c0_spi-reversing: Goodix 51C0 SPI protocol RE.
+  lexakimov - goodix51c0_spi-reversing: Goodix 51C0 SPI protocol RE.
     https://github.com/lexakimov/goodix51c0_spi-reversing
-  goodix-fp-linux-dev — goodix-fp-dump: Goodix USB protocol work, useful for
+  goodix-fp-linux-dev - goodix-fp-dump: Goodix USB protocol work, useful for
     comparison. https://github.com/goodix-fp-linux-dev/goodix-fp-dump
-  archshift — goodix_fingerprint_re: Goodix driver RE (Dell XPS 15 2019).
+  archshift - goodix_fingerprint_re: Goodix driver RE (Dell XPS 15 2019).
     https://github.com/archshift/goodix_fingerprint_re
 
 Matcher technique references:
   D. Lowe, "Distinctive Image Features from Scale-Invariant Keypoints" (2004).
   Arandjelović & Zisserman, "Three things everyone should know to improve
-    object retrieval" — RootSIFT (2012).
+    object retrieval" - RootSIFT (2012).

devices/gxfp5187/README.md

@@ -8,7 +8,7 @@ Enrols and verifies through `fprintd` and GNOME Settings; session unlock and
 Upstream libfprint has no driver for this sensor (tracked in
 [libfprint issue #112](https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/112)).
 This entry points at an out-of-tree **TOD** driver (a shared module libfprint
-loads at runtime), not a patch against libfprint's own sources — see
+loads at runtime), not a patch against libfprint's own sources. See
 [patches/](patches/) for the base version and where the code lives.
 
 The driver, its full protocol write-up and the reasoning behind the matcher are
@@ -24,7 +24,7 @@ are listed here.
 - **It is SPI, not USB.** libfprint reaches it through the `spidev` node. The
   `spidev` kernel module must be bound to the SPI device (`spi-GXFP5187:00`);
   the driver ships a udev rule that does this on every appearance. `spidev` has
-  no alias for this hardware, so nothing loads it on its own — the install
+  no alias for this hardware, so nothing loads it on its own, so the install
   step forces it.
 - **`spidev` must be given a larger buffer.** The image arrives as a single
   ~22 kB SPI transfer, above the 4096-byte default; `options spidev

devices/gxfp5187/patches/.gitkeep

@@ -1,7 +1,7 @@
 # Patches
 
-This sensor is served by an out-of-tree **TOD** driver — a shared module that
-libfprint loads at runtime — not by a patch series against libfprint's own
+This sensor is served by an out-of-tree **TOD** driver, a shared module that
+libfprint loads at runtime, not by a patch series against libfprint's own
 source tree. There are therefore no `.patch` files here; the code lives in its
 own repository and is built and installed as a module.
 

devices/gxfp5187/patches/README.md

@@ -17,7 +17,7 @@ lsusb        # find the reader, e.g. 27c6:55b4
 then look it up in the [main README](../README.md), or run
 `./tools/detect.sh` to have it matched for you.
 
-31 model listings map to a catalogued sensor; the rest are on the
+32 model listings map to a catalogued sensor; the rest are on the
 gap-map with no known fix, and a protocol dump for any of them is welcome.
 
 **Adding your machine** is the single most useful small contribution here.