diff options
| author | fauxpark <fauxpark@gmail.com> | 2017-12-09 16:49:07 +1100 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-12-09 10:46:11 -0500 |
| commit | af37bb2f78c39c224c995eb57c757c63034a3d9c (patch) | |
| tree | 9ad591cb895d1ac13cce6145d11738569dff0a93 /docs/feature_unicode.md | |
| parent | 4c675a83ba1d3561bfd6baad57a250066f5db4d3 (diff) | |
Fix some of the more obvious typos
Diffstat (limited to 'docs/feature_unicode.md')
| -rw-r--r-- | docs/feature_unicode.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_unicode.md b/docs/feature_unicode.md index 24390631d3..ecad6c60c7 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. |