X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=docs%2Funderstanding_qmk.md;h=0d3d24017d6bbeaa1d7cc49568d2c88d02db8d5f;hb=7aaef1626693f4e4449946de025aa6175adcfa3d;hp=2ac4f3036504fdbf03b78986923a393c1ff1224e;hpb=9d1a08e38ac9937cff4e61abfd0acc26ad5fdf4a;p=qmk_firmware.git

diff --git a/docs/understanding_qmk.md b/docs/understanding_qmk.md
index 2ac4f3036..0d3d24017 100644
--- a/docs/understanding_qmk.md
+++ b/docs/understanding_qmk.md
@@ -2,7 +2,7 @@
 
 This document attempts to explain how the QMK firmware works from a very high level. It assumes you understand basic programming concepts but does not (except where needed to demonstrate) assume familiarity with C. It assumes that you have a basic understanding of the following documents:
 
-* [QMK Overview](qmk_overview.md)
+* [Introduction](getting_started_introduction.md)
 * [How Keyboards Work](how_keyboards_work.md)
 * [FAQ](faq.md)
 
@@ -147,6 +147,7 @@ The `process_record()` function itself is deceptively simple, but hidden within
     * [`bool process_unicode(uint16_t keycode, keyrecord_t *record)`](https://github.com/qmk/qmk_firmware/blob/master/quantum/process_keycode/process_unicode.c#L22)
     * [`bool process_ucis(uint16_t keycode, keyrecord_t *record)`](https://github.com/qmk/qmk_firmware/blob/master/quantum/process_keycode/process_ucis.c#L91)
     * [`bool process_printer(uint16_t keycode, keyrecord_t *record)`](https://github.com/qmk/qmk_firmware/blob/master/quantum/process_keycode/process_printer.c#L77)
+    * [`bool process_auto_shift(uint16_t keycode, keyrecord_t *record)`](https://github.com/qmk/qmk_firmware/blob/master/quantum/process_keycode/process_auto_shift.c#L47)
     * [`bool process_unicode_map(uint16_t keycode, keyrecord_t *record)`](https://github.com/qmk/qmk_firmware/blob/master/quantum/process_keycode/process_unicodemap.c#L47)
     * [Identify and process quantum specific keycodes](https://github.com/qmk/qmk_firmware/blob/master/quantum/quantum.c#L211)