[Docs] Fixed minor typos (#8860)

docs/syllabus.md

@@ -4,7 +4,7 @@ This page helps you build up your QMK knowledge by introducing the basics first
 
 # Beginning Topics
 
-If you read nothing else you should read the documents in this section. After reading the [Tutorial](newbs.md) you should be able to create a basic keymap, complie it, and flash it to your keyboard. The remaining documents will flesh out your knowledge of these basics.
+If you read nothing else you should read the documents in this section. After reading the [Tutorial](newbs.md) you should be able to create a basic keymap, compile it, and flash it to your keyboard. The remaining documents will flesh out your knowledge of these basics.
 
 * **Learn How To Use QMK Tools**
     * [Tutorial](newbs.md)
@@ -20,7 +20,7 @@ If you read nothing else you should read the documents in this section. After re
 
 # Intermediate Topics
 
-These topics start dig into some of the features that QMK supports. You don't have to read all of these documents, but some of the documents in the Advanced Topics section won't make sense if you skip over some of these.
+These topics start to dig into some of the features that QMK supports. You don't have to read all of these documents, but some of the documents in the Advanced Topics section won't make sense if you skip over some of these.
 
 * **Learn How To Configure Features**
     <!-- * Configuration Overview  FIXME(skullydazed/anyone): write this document -->
@@ -62,9 +62,9 @@ Everything below here requires a lot of foundational knowledge. Besides being ab
     * [Pointing Devices](feature_pointing_device.md)
 * **Core Development**
     * [Coding Conventions](coding_conventions_c.md)
-    * [Compatible Microcontrolers](compatible_microcontrollers.md)
+    * [Compatible Microcontrollers](compatible_microcontrollers.md)
     * [Custom Matrix](custom_matrix.md)
-    * [Understandnig QMK](understanding_qmk.md)
+    * [Understanding QMK](understanding_qmk.md)
 * **CLI Development**
     * [Coding Conventions](coding_conventions_python.md)
     * [CLI Development Overview](cli_development.md)

docs/tap_hold.md

@@ -12,7 +12,7 @@ As of [PR#1359](https://github.com/qmk/qmk_firmware/pull/1359/), there is a new
 #define PERMISSIVE_HOLD
 ```
 
-This makes tap and hold keys (like Mod Tap) work better for fast typist, or for high `TAPPING_TERM` settings. 
+This makes tap and hold keys (like Mod Tap) work better for fast typists, or for high `TAPPING_TERM` settings. 
 
 If you press a Mod Tap key, tap another key (press and release) and then release the Mod Tap key, all within the tapping term, it will output the "tapping" function for both keys.
 
@@ -35,7 +35,7 @@ To enable this setting, add this to your `config.h`:
 #define IGNORE_MOD_TAP_INTERRUPT
 ```
 
-Similar to Permissive Hold, this alters how the firmware processes input for fast typist. If you press a Mod Tap key, press another key, release the Mod Tap key, and then release the normal key, it would normally output the "tapping" function for both keys. This may not be desirable for rolling combo keys. 
+Similar to Permissive Hold, this alters how the firmware processes inputs for fast typists. If you press a Mod Tap key, press another key, release the Mod Tap key, and then release the normal key, it would normally output the "tapping" function for both keys. This may not be desirable for rolling combo keys. 
 
 Setting `Ignore Mod Tap Interrupt` requires  holding both keys for the `TAPPING_TERM` to trigger the hold function (the mod).
 

tmk_core/common/action.c

@@ -870,7 +870,7 @@ void tap_code(uint8_t code) {
 
 /** \brief Adds the given physically pressed modifiers and sends a keyboard report immediately.
  *
- * \param mods A bitfield of modifiers to unregister.
+ * \param mods A bitfield of modifiers to register.
  */
 void register_mods(uint8_t mods) {
     if (mods) {