(small comment update)

Also, I just tested the scan rate without debounce (lol, should have
thought of that before) and it's about 471Hz.  This is much faster than
the 200Hz (every 5ms) that we need to limit ourselves to due to the
switches needing a 5ms debounce time.  It should be trivial to tune the
scan rate to closer to 200Hz once I get lib/timer implemented.

firmware/main.c

@@ -54,10 +54,11 @@ uint8_t col;
  * Mostly all that happens here after initialization is that current and
  * previous key states are tracked, keys that change state are "executed", the
  * USB report is sent, and the LEDs are updated.  We also have a delay, to make
- * sure the keys have time to debounce.  Almost everything interesting happens
- * somewhere else (especially in ".../firmware/keyboard/.../layout"); have a
- * look through the source, especially the documentation, to see how things are
- * defined and what's actually happening.
+ * sure we don't detect switch bounce from the keys.  Almost everything
+ * interesting happens somewhere else (especially in
+ * ".../firmware/keyboard/.../layout"); have a look through the source,
+ * especially the documentation, to see how things are defined and what's
+ * actually happening.
  */
 int main(void) {
     static bool (*temp)[OPT__KB__ROWS][OPT__KB__COLUMNS]; // for swapping below