From af37bb2f78c39c224c995eb57c757c63034a3d9c Mon Sep 17 00:00:00 2001 From: fauxpark Date: Sat, 9 Dec 2017 16:49:07 +1100 Subject: Fix some of the more obvious typos --- docs/feature_unicode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/feature_unicode.md') diff --git a/docs/feature_unicode.md b/docs/feature_unicode.md index 24390631d..ecad6c60c 100644 --- a/docs/feature_unicode.md +++ b/docs/feature_unicode.md @@ -24,7 +24,7 @@ sort of like macro. Unfortunately, each OS has different ideas on how Unicode is This is the current list of Unicode input method in QMK: * UC_OSX: MacOS Unicode Hex Input support. Works only up to 0xFFFF. Disabled by default. To enable: go to System Preferences -> Keyboard -> Input Sources, and enable Unicode Hex. -* UC_OSX_RALT: Same as UC_OSX, but sends the Rigt Alt key for unicode input +* UC_OSX_RALT: Same as UC_OSX, but sends the Right Alt key for unicode input * UC_LNX: Unicode input method under Linux. Works up to 0xFFFFF. Should work almost anywhere on ibus enabled distros. Without ibus, this works under GTK apps, but rarely anywhere else. * UC_WIN: (not recommended) Windows built-in Unicode input. To enable: create registry key under `HKEY_CURRENT_USER\Control Panel\Input Method\EnableHexNumpad` of type `REG_SZ` called `EnableHexNumpad`, set its value to 1, and reboot. This method is not recommended because of reliability and compatibility issue, use WinCompose method below instead. * UC_WINC: Windows Unicode input using WinCompose. Requires [WinCompose](https://github.com/samhocevar/wincompose). Works reliably under many (all?) variations of Windows. -- cgit v1.2.3-24-g4f1b