Fix Typos (#17)

Co-authored-by: dizaumuna <cgorkm703@outlook.com>

Author: dizaumuna

DualBoot/Config.md

@@ -21,7 +21,7 @@ If you do not need it, set the two values to 0.
     + StackSize the right after the base address of `UEFI FD`.
 
   - `RestartReasonAddress`
-    + Comming Soon.
+    + Coming Soon.
     + RestartReasonAddress can be found in a Qualcomm device's device tree.
     + Enter android or recovery, run the following shell cmd with root permission.
     + Output should like this:

DualBoot/PatchKernel.md

@@ -112,4 +112,4 @@ Please do not patch a patched kernel.
   ```
 
 ## Remove dualboot
-Run `DualBootPatchRemover` on the patched kernel and rebuild the boot image. After flashing to boot parition the dualboot feature will disappear.
+Run `DualBootPatchRemover` on the patched kernel and rebuild the boot image. After flashing to boot partition the dualboot feature will disappear.

DualBoot/ShellCode.md

@@ -20,4 +20,4 @@ Shell Code is the key place why we patch kernel or what do we patch kernel for.
     - Handles unexceptional behavior in the end.
 
 ## DTB Wrapper
-  - Comming soon.
+  - Coming soon.

PortingGuides/SimpleGuide.md

@@ -143,7 +143,7 @@ ___
 ## **Part 3.** Patch binaries.
   - Which binary needs Patch ?
     * If your phone stack while loading PILDxe, patch UFSDxe.
-    * If your phone can not connect with PC via KDNET, or USB not working in windows(with externel power), patch UsbConfigDxe.
+    * If your phone can not connect with PC via KDNET, or USB not working in windows(with external power), patch UsbConfigDxe.
     * If your phone can not use button at uefi stage, please patch ButtonsDxe.
   - Where to patch ?
     * The most simple way to know where to patch:

README.md

@@ -29,4 +29,4 @@ Alternatively if you do not want to use vscode:
 - Run `npm run docs:dev` at the root of this repo.
 
 ### For More
-You can read [VitePress's Guides](https://vitepress.dev/guide/getting-started) if you want edit configurations here or want to use some speacial markdown feature provided by vitepress.
+You can read [VitePress's Guides](https://vitepress.dev/guide/getting-started) if you want edit configurations here or want to use some special markdown feature provided by vitepress.

WindowsDebug/SetupKDCOM.md

@@ -1,6 +1,6 @@
 # Setup Windbg KdCom
 ::: tip Tips
-Sugguest using KdNet for better experience if you can not access your device's uart pins easily.  
+Suggest using KdNet for better experience if you can not access your device's uart pins easily.  
 KdCom does not support rdp over it.
 :::
 
@@ -49,7 +49,7 @@ KdCom does not support rdp over it.
     ```
     ```bash
     # Execute on phone
-    # Backup nomal BCD
+    # Backup normal BCD
     cp /dev/esp_mnt/EFI/Microsoft/Boot/BCD /dev/esp_mnt/EFI/Microsoft/Boot/NMBCD
     # Backup kdnet enabled BCD
     cp /sdcard/BCD /dev/esp_mnt/EFI/Microsoft/Boot/DBGBCD
@@ -80,4 +80,4 @@ KdCom does not support rdp over it.
 
 ::: tip Notice
   - You can close Windbg and open a serial tool like PuTTY or SecureCRT to check if the phone printed some unrecognized messages while windows booting. If it isn't that means BCD configurations were wrong
-:::
+:::

WindowsDebug/SetupKDNET.md

@@ -45,7 +45,7 @@
     ```
     ```bash
     # Execute on phone
-    # Backup nomal BCD
+    # Backup normal BCD
     cp /dev/esp_mnt/EFI/Microsoft/Boot/BCD /dev/esp_mnt/EFI/Microsoft/Boot/NMBCD
     # Backup kdnet enabled BCD
     cp /sdcard/BCD /dev/esp_mnt/EFI/Microsoft/Boot/DBGBCD
@@ -54,7 +54,7 @@
     ```
 
 ### Setup KDNET in Windbg
-  - Opne Windbg(Preview)，Click the **File** button on the top left corner
+  - Open Windbg(Preview)，Click the **File** button on the top left corner
   - Click `Attach to kernel` under `Start debugging`(default section).
   - Click `Net`(default section)
     + Type `50000` in `Port Number`
@@ -76,4 +76,4 @@
   - Windows on phone will load once windbg connected.
   - You can press `Ctrl+Alt+V` to enable verbose mode for checking driver loading status.
   - End
-  
+