Grammar Corrections

cosmetic/gui.md

@@ -9,13 +9,13 @@ Main thing this guide will go over:
 
 So to get started, we're gonna need 0.5.7 or newer as these builds have the GUI included with the rest of the files. If you're on an older version, I recommend updating: [Updating OpenCore](../universal/update.md)
 
-Once that's done, we'll need a couple things:
+Once that's done, we'll need a couple of things:
 
 * [Binary Resources](https://github.com/acidanthera/OcBinaryData)
 * [OpenCanopy.efi](https://github.com/acidanthera/OpenCorePkg/releases)
   * Note: OpenCanopy.efi must be from the same build as your OpenCore files, as mismatched files can cause boot issues
 
-Once you have both of these, we'll next want to add it to our EFI partition:
+Once you have both of these, we'll next want to add them to our EFI partition:
 
 * Add the [Resources folder](https://github.com/acidanthera/OcBinaryData) to EFI/OC
 * Add OpenCanopy.efi to EFI/OC/Drivers
@@ -25,8 +25,8 @@ Once you have both of these, we'll next want to add it to our EFI partition:
 Now in our config.plist, we have 4 things we need to fix:
 
 * `Misc -> Boot -> PickerMode`: `External`
-* `Misc -> Boot -> PickerAttributes`: `17`
-  * This enables mouse/trackpad support as well as .VolumeIcon.icns reading from the drive, allows for macOS installer icons to appear in the picker
+* `Misc -> Boot -> PickerAttributes`: `17`.
+  * This enables mouse/trackpad support as well as .VolumeIcon.icns reading from the drive, allows for macOS installer icons to appear in the picker.
     * Other settings for PickerAttributes can be found in the [Configuration.pdf](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf)
 * `Misc -> Boot -> PickerVariant`: `Acidanthera\GoldenGate`
   * Applicable variables:
@@ -44,7 +44,7 @@ Once all this is saved, you can reboot and be greeted with a true Mac-like GUI:
 
 ## Setting up Boot-chime with AudioDxe
 
-So to start, we'll need a couple things:
+So to start, we'll need a couple of things:
 
 * Onboard audio output
   * USB DACs will not work
@@ -87,7 +87,7 @@ So to start, we'll need a couple things:
     * ex: `PciRoot(0x0)/Pci(0x1f,0x3)`
 
 * **AudioOut:**
-  * The specific output of your Audio controller, easiest way to find the right one is to go through each one(from 0 to N - 1, where N is the number of outputs listed in your log)
+  * The specific output of your Audio controller, the easiest way to find the right one is to go through each one(from 0 to N - 1, where N is the number of outputs listed in your log)
   * ex: 5 outputs would translate to 0-4 as possible values
     * You can find all the ones for your codec in the OpenCore debug logs:
 

cosmetic/verbose.md

@@ -1,6 +1,6 @@
 # Fixing Resolution and Verbose
 
-Wanting a more clean booting experience with macOS without all that verbose text while booting? Well you need a couple things:
+Wanting a more clean booting experience with macOS without all that verbose text while booting? Well, you need a couple of things:
 
 ## macOS Decluttering
 

gpu-patching/intel-patching/README.md

@@ -1,6 +1,6 @@
 # Intel iGPU Patching
 
-This guide will be a more in-depth look into patching macOS to support more hardware variations of Intel's iGPUs including proper display out, fixing color tint issues, HiDPI issues and etc. Note this guide is **not** a beginners tutorial, we recommend you follow the recommend iGPU properties listed in the config.plist section of the guide to start off.
+This guide will be a more in-depth look into patching macOS to support more hardware variations of Intel's iGPUs including proper display out, fixing color tint issues, HiDPI issues etc. Note this guide is **not** a beginner's tutorial, we recommend you follow the recommend iGPU properties listed in the config.plist section of the guide to start off.
 
 This guide supports:
 
@@ -89,13 +89,13 @@ From here, lets open up our config.plist and head to DeviceProperties -> Add. No
 
 To determine whether you need a new `device-id` injected, you'll want to compare [WhateverGreen's list of supported IDs](https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md) to what you have.
 
-For this example, lets take a look at the i3-4150 with an HD 4400 iGPU. Using [Intel's ARK page](https://ark.Intel.com/content/www/us/en/ark/products/77486/Intel-core-i3-4150-processor-3m-cache-3-50-ghz.html), we can see the following:
+For this example, let's take a look at the i3-4150 with an HD 4400 iGPU. Using [Intel's ARK page](https://ark.Intel.com/content/www/us/en/ark/products/77486/Intel-core-i3-4150-processor-3m-cache-3-50-ghz.html), we can see the following:
 
 ```
 Device ID = 0x41E
 ```
 
-Now that we have our actual Device ID, lets compare it to [WhateverGreen's list](https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md):
+Now that we have our actual Device ID, let's compare it to [WhateverGreen's list](https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md):
 
 ```
 Native supported DevIDs:
@@ -107,7 +107,7 @@ Native supported DevIDs:
  0x0412
 ```
 
-Unfortunately the ID is not present in macOS, so we'll need to find a similar iGPU to ours and use their Device ID. The HD 4600 found in the [i3-4330](https://ark.Intel.com/content/www/us/en/ark/products/77769/Intel-core-i3-4330-processor-4m-cache-3-50-ghz.html) is a very close match, so we'll use its Device ID:
+Unfortunately, the ID is not present in macOS, so we'll need to find a similar iGPU to ours and use their Device ID. The HD 4600 found in the [i3-4330](https://ark.Intel.com/content/www/us/en/ark/products/77769/Intel-core-i3-4330-processor-4m-cache-3-50-ghz.html) is a very close match, so we'll use its Device ID:
 
 ```
 Device ID = 0x412

gpu-patching/intel-patching/busid.md

@@ -72,7 +72,7 @@ Here we have 2 sections:
 
 Mapping videos in macOS is fairly easy, as we can assume that one of our ports is mapped correctly in the framebuffer.
 
-For this example, we'll explain the common [HDMI-hotplug fix for Kaby lake users](https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/kaby-lake.html#deviceproperties). To start, lets look at the 0x591B0000 framebuffer:
+For this example, we'll explain the common [HDMI-hotplug fix for Kaby lake users](https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/kaby-lake.html#deviceproperties). To start, let's look at the 0x591B0000 framebuffer:
 
 ```
 ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B
@@ -109,7 +109,7 @@ So since entry 2 is the second in the list, we'll want to use con1:
 
 * framebuffer-con2-enable
 
-Next lets make the patch, we know that port needs to be patched to 01 and BusID changed to 05:
+Next let's make the patch, we know that port needs to be patched to 01 and BusID changed to 05:
 
 * **0105**0A00 00080000 87010000
 

gpu-patching/intel-patching/connector.md

@@ -1,8 +1,8 @@
 # Patching Connector Types
 
-* Images and info based off [CorpNewt's Vanilla Guide](https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake#pink-purple-tint)
+* Images and info based on [CorpNewt's Vanilla Guide](https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake#pink-purple-tint)
 
-This section is mainly relevant for users who either get black screen or incorrect color output on their displays(usually HDMI ports). This is due to Apple forcing display types onto your hardware,. To work around it, we'll patch Apple's connector types to properly respect our hardware.
+This section is mainly relevant for users who either get a black screen or incorrect color output on their displays(usually HDMI ports). This is due to Apple forcing display types onto your hardware,. To work around it, we'll patch Apple's connector types to properly respect our hardware.
 
 For this example, let's take a UHD 630 system with an HDMI display attached. The machine has already been correctly setup however there's a Pink/Purple tint on the HDMI display.
 

gpu-patching/legacy-intel/README.md

@@ -13,7 +13,7 @@ Please note this page is more of an info dump, we won't be going to too great of
 
 ## Prerequisites
 
-Unfortunately GMA support is a bit more complicated with PCs, and because of this we need to force a 32-Bit kernelspace as the 64-Bit GMA drivers are known for weird GPU corruption and sleep issues. To do this:
+Unfortunately, GMA support is a bit more complicated with PCs, and because of this we need to force a 32-Bit kernelspace as the 64-Bit GMA drivers are known for weird GPU corruption and sleep issues. To do this:
 
 * Ensure all your kexts are either 32-Bit or FAT
   * Run `lipo -archs` on the kext's binary to verify

gpu-patching/nvidia-patching/README.md

@@ -72,7 +72,7 @@ GeForce GT 220
 
 Amount of VRAM present on your card, in hexadecimal.
 
-For this example, lets convert 1024MB to hexadecimal:
+For this example, let's convert 1024MB to hexadecimal:
 
 ```md
 # Convert 1024MB Megabytes to Bytes
@@ -129,7 +129,7 @@ Now press enter, and return to the main menu. Once there, enter `3` to take you
 
 ![](../../images/gpu-patching/nvidia/nvcap-initial-nvcap.png)
 
-Here you can see the connectors that NVCAP-Calculator was able to find. Each Display may represent multiple DCB Entries, such as DVI (normally represented as two entries) or duplicate DCB entries. The goal here is to assign each display to a head. Each head can only output to one display at a time. For example, if your using 2 DVI ports, each should be on their own head to have proper dual monitor support.
+Here you can see the connectors that NVCAP-Calculator was able to find. Each Display may represent multiple DCB Entries, such as DVI (normally represented as two entries) or duplicate DCB entries. The goal here is to assign each display to a head. Each head can only output to one display at a time. For example, if you're using 2 DVI ports, each should be on their own head to have proper dual monitor support.
 
 Note that some displays may be assigned automatically. An LVDS display will be put on it's own head automatically, and TV displays will be put on the TV head automatically.
 

laptop-specific/battery.md

@@ -4,7 +4,7 @@ While at the moment battery patching is not something covered in this guide, we'
 
 ## DSDT Patching
 
-While custom DSDT injection should be avoided as to prevent issues with Windows and firmware updates, it can be quite helpful as a starting point since it's a bit easier to grasp and do yourself:
+While custom DSDT injection should be avoided to prevent issues with Windows and firmware updates, it can be quite helpful as a starting point since it's a bit easier to grasp and do yourself:
 
 **[Rehabman's how to patch DSDT for working battery status](https://www.tonymacx86.com/threads/guide-how-to-patch-dsdt-for-working-battery-status.116102/)**
 

misc/msr-lock.md

@@ -6,7 +6,7 @@ This guide is only recommended for users who have already installed macOS, for u
 
 ## What is CFG-Lock
 
-CFG-Lock is a setting in your BIOS that allows for a specific register(in this case the MSR 0xE2) to be written to. By default, most motherboards lock this variable with many even hiding the option outright in the GUI. And why we care about it is that macOS actually wants to write to this variable, and not just one part of macOS. Instead both the Kernel(XNU) and AppleIntelPowerManagement want this register.
+CFG-Lock is a setting in your BIOS that allows for a specific register(in this case the MSR 0xE2) to be written to. By default, most motherboards lock this variable with many even hiding the option outright in the GUI. And why we care about it is that macOS actually wants to write to this variable, and not just one part of macOS. Instead, both the Kernel(XNU) and AppleIntelPowerManagement want this register.
 
 So to fix it we have 2 options:
 
@@ -26,7 +26,7 @@ Note: Penyrn based machines actually don't need to worry about unlocking this re
 ## Checking if your firmware supports CFG Lock unlocking
 
 Before proceeding with the rest of this guide, you'll first need to check if your firmware supports CFG Lock unlocking.
-To check it, you can proceed into two ways:
+To check it, you can proceed in two ways:
 
 1. [Use the DEBUG version of OpenCore and check what the log says about CFG Lock](#checking-via-opencore-logs)
 2. [Use a tool called `VerifyMsrE2` which will speed up the whole checking process](#checking-via-verifymsre2)
@@ -67,7 +67,7 @@ For the latter, you don't need to do any CFG-Lock patches and can simply disable
 
 ## Disabling CFG Lock
 
-So you've created the EFI folder but you can't still boot without unlocking before CFG Lock. In order to do this you'll need the following:
+So you've created the EFI folder but you can't still boot without unlocking before CFG Lock. To do this you'll need the following:
 
 Inside your `EFI/OC/Tools` folder and `config.plist`, add the following tool(this can be done with ProperTree's snapshot function(ie. Cmd+R)):
 

misc/rtc.md

@@ -19,9 +19,9 @@ So with OpenCore, we've got a few options to choose:
   * Much easier for the end user to patch
   * Prevents EfiBoot from breaking your system as well
 
-The former is actually already integrated into OpenCore with the `DisableRtcChecksum` quirk, but has the downfall of only blocking regions 0x58-0x59 and only working in the kernel level. Best way to know if this option is best, enable it and try. If this doesn't work, disable as it's an unnecessary patch.
+The former is actually already integrated into OpenCore with the `DisableRtcChecksum` quirk, but has the downfall of only blocking regions 0x58-0x59 and only working in the kernel level. The best way to know if this option is best, enable it and try. If this doesn't work, disable it as it's an unnecessary patch.
 
-With the latter, we're able to block very specific regions of our choice that match our exact model. And we're able to do this both in the kernel level and firmware aiding with hibernation support. This however will requires much more time and [RTCMemoryFixup](https://github.com/acidanthera/RTCMemoryFixup/releases/tag/1.0.6).
+With the latter, we're able to block very specific regions of our choice that match our exact model. And we're able to do this both at the kernel level and firmware aiding with hibernation support. This however will require much more time and [RTCMemoryFixup](https://github.com/acidanthera/RTCMemoryFixup/releases/latest).
 
 ## Finding our bad RTC region
 
@@ -32,7 +32,7 @@ For the rest of this guide, we're going to assume you've tested option 1(`Disabl
 * To omit bad regions, we use the boot-arg `rtcfx_exclude=00-FF`
   * Replace `00-FF` with your bad region (or regions)
   * Reminder that `boot-args` is located under `NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82` in your config.plist
-  * This will also require you to have [RTCMemoryFixup](https://github.com/acidanthera/RTCMemoryFixup/releases/tag/1.0.6) in your config.plist and EFI/OC/Kexts folder.
+  * This will also require you to have [RTCMemoryFixup](https://github.com/acidanthera/RTCMemoryFixup/releases/latest) in your config.plist and EFI/OC/Kexts folder.
 * There can be multiple bad regions
 * To find the bad region, we'll want to split out search into chunks
 
@@ -51,7 +51,7 @@ Regarding splitting out chunks, what we'll be doing is omitting chunks of RTC re
   * Note you may also get a bad range of 7F-80, or even bad regions split into multiple sections(ex. 0x00-0x01 **and** 0x80-0x81)
   * You can use `rtcfx_exclude=00-01,7F-80` to resolve this
 
-#### 3. After testing which regions is bad, shrink even more
+#### 3. After testing which regions are bad, shrink even more
 
 * Assuming our bad region was within 0x80-0xFF, you'd next split that into 2:
 * 0x80-0xBF and 0xC0-0xFF
@@ -66,7 +66,7 @@ Regarding splitting out chunks, what we'll be doing is omitting chunks of RTC re
 
 * `(x + y) / 2`
 
-Now lets try to use this with step 1 from earlier:
+Now let's try to use this with step 1 from earlier:
 
 * 0x00-0xFF -> 0-255 -> `(0 + 255) / 2` = 127.5
 
@@ -84,7 +84,7 @@ Once you've found the bad RTC region, you can now finally add it to OpenCore its
 
 For this, open up your config.plist and head to the `NVRAM -> Add` section. Here under the `4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102` GUID, you'll want to add a new entry called `rtc-blacklist`
 
-Next you'll want to add our bad RTC region as an array, so `rtcfx_exclude=85-86` will become `rtc-blacklist | Data | 8586`. This will also work with longer ranges such as 85-89 and such however with `rtc-blacklist` you must include every entry(ie. `<85 86 87 88 89>`). Remember to remove the boot-arg once you're set `rtc-blacklist`
+Next, you'll want to add our bad RTC region as an array, so `rtcfx_exclude=85-86` will become `rtc-blacklist | Data | 8586`. This will also work with longer ranges such as 85-89 and such however with `rtc-blacklist` you must include every entry(ie. `<85 86 87 88 89>`). Remember to remove the boot-arg once you're set `rtc-blacklist`
 
 Next ensure you have `NVRAM -> Delete` also set as NVRAM variables will not be overwritten by OpenCore unless explicitly told so.
 

multiboot/bootcamp.md

@@ -1,6 +1,6 @@
 # Installing and using BootCamp utilities
 
-So a neat feature of OpenCore is the ability to avoid the BIOS entirely and use Startup disk solely for multiboot. Problem comes in when we try to boot windows and have no way of setting the boot option back to macOS. That's where the BootCamp utilities come in.
+So a neat feature of OpenCore is the ability to avoid the BIOS entirely and use Startup disk solely for multiboot. The problem comes in when we try to boot windows and have no way of setting the boot option back to macOS. That's where the BootCamp utilities come in.
 
 * Note: This guide will not cover the creation of the Windows installer, only the installation of BootCamp drivers.
   * Example of Windows installer creation: [Build a Bootable Windows ISO](https://www.freecodecamp.org/news/how-make-a-windows-10-usb-using-your-mac-build-a-bootable-iso-from-your-macs-terminal/)
@@ -32,7 +32,7 @@ path/to/Brigadier --model MacPro7,1
 
 ![](../images/bootcamp-md/extension.png)
 
-Next you will find our bootcamp drivers under either:
+Next, you will find our bootcamp drivers under either:
 
 * Windows:
 
@@ -50,11 +50,11 @@ macOS users will next need to expand WindowsSupport.dmg and place it somewhere W
 
 ![](../images/bootcamp-md/done.png)
 
-Next navigate to the `bootcamp-{filename}\BootCamp` folder and run the Setup.exe:
+Next, navigate to the `bootcamp-{filename}\BootCamp` folder and run the Setup.exe:
 
 ![](../images/bootcamp-md/location.png)
 
-Once all is finished, you now have BootCamp switching! There should be a little BootCamp icon in you tray now that you can select which drive to boot to.
+Once all is finished, you now have BootCamp switching! There should be a little BootCamp icon in your tray now that you can select which drive to boot to.
 
 * Note: For those no needing the extra drivers BootCamp provides, you can delete the following:
   * `$WinPEDriver$`: **DO NOT** delete the folder itself, just the drivers inside

multiboot/bootstrap.md

@@ -46,7 +46,7 @@ Because the LauncherOption entry is a protected entry when resetting NVRAM, you'
 * `Misc -> Security -> AllowNvramReset -> True`
 * `Misc -> Boot -> LauncherOption -> Disabled`
 
-Once these are set, you can reboot into the OpenCore picker and select the `Reset NVRAM` entry to clear your NVRAM, which will remove the LauncherOption entry too..
+Once these are set, you can reboot into the OpenCore picker and select the `Reset NVRAM` entry to clear your NVRAM, which will remove the LauncherOption entry too.
 
 ## Updating Bootstrap in 0.6.6
 

universal/audio.md

@@ -19,7 +19,7 @@ So for this example, we'll assume your codec is ALC1220. To verify yours, you ha
 * Run `cat` in terminal on Linux
   * `cat /proc/asound/card0/codec#0 | less`
 
-Now with a codec, we'll want to cross reference it with AppleALC's supported codec list:
+Now with a codec, we'll want to cross-reference it with AppleALC's supported codec list:
 
 * [AppleALC Supported Codecs](https://github.com/acidanthera/AppleALC/wiki/Supported-codecs)