Adjust headings on unicode

docs/unicode_and_additional_language_support.md

@@ -1,20 +1,20 @@
-## Unicode support
+# Unicode support
 
 There are three Unicode keymap definition method available in QMK:
 
-### UNICODE_ENABLE
+## UNICODE_ENABLE
 
 Supports Unicode input up to 0xFFFF. The keycode function is `UC(n)` in
 keymap file, where *n* is a 4 digit hexadecimal.
 
-### UNICODEMAP_ENABLE
+## UNICODEMAP_ENABLE
 
 Supports Unicode up to 0xFFFFFFFF. You need to maintain a separate mapping
 table `const uint32_t PROGMEM unicode_map[] = {...}` in your keymap file.
 The keycode function is `X(n)` where *n* is the array index of the mapping
 table.
 
-### UCIS_ENABLE
+## UCIS_ENABLE
 
 TBD
 
@@ -28,11 +28,11 @@ This is the current list of Unicode input method in QMK:
 * 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.
 
-## Additional language support
+# Additional language support
 
 In `quantum/keymap_extras/`, you'll see various language files - these work the same way as the alternative layout ones do. Most are defined by their two letter country/language code followed by an underscore and a 4-letter abbreviation of its name. `FR_UGRV` which will result in a `ù` when using a software-implemented AZERTY layout. It's currently difficult to send such characters in just the firmware.
 
-## International Characters on Windows
+# International Characters on Windows
 
 [AutoHotkey](https://autohotkey.com) allows Windows users to create custom hotkeys among others.