summaryrefslogtreecommitdiff
path: root/users/gourdo1/autocorrect/autocorrection.c
diff options
context:
space:
mode:
Diffstat (limited to 'users/gourdo1/autocorrect/autocorrection.c')
-rw-r--r--users/gourdo1/autocorrect/autocorrection.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/users/gourdo1/autocorrect/autocorrection.c b/users/gourdo1/autocorrect/autocorrection.c
index bc711016d9..dae62d37a2 100644
--- a/users/gourdo1/autocorrect/autocorrection.c
+++ b/users/gourdo1/autocorrect/autocorrection.c
@@ -71,7 +71,7 @@ bool process_autocorrection(uint16_t keycode, keyrecord_t* record) {
break;
// NOTE: Space Cadet keys expose no info to check whether they are being
- // tapped vs. held. This makes autocorrection ambiguous, e.g. KC_LCPO might
+ // tapped vs. held. This makes autocorrection ambiguous, e.g. SC_LCPO might
// be '(', which we would treat as a word break, or it might be shift, which
// we would treat as having no effect. To behave cautiously, we allow Space
// Cadet keycodes to fall to the logic below and clear autocorrection state.