diff --git a/docs/altos.md b/docs/altos.md
index b3bf520e..88a10d4b 100644
--- a/docs/altos.md
+++ b/docs/altos.md
@@ -18,9 +18,9 @@ Pros:
Cons:
* Audio driver is paid (10 USD) for Skylake (6th generation) and newer devices
-* Thunderbolt driver is paid (20 USD) for certain generations
+* USB4/Thunderbolt driver is paid (20 USD) for **TigerLake** (11th generation Intel processors) and **newer** generations on devices that require them
* Requires the user to install many drivers
-* AVS and SOF users experience instability at times
+* AVS and SOF users may experience instability at times
### [Installing Windows →](installing-windows.html)
diff --git a/docs/bootableusb.md b/docs/bootableusb.md
index 3f708b5c..2c420b7a 100644
--- a/docs/bootableusb.md
+++ b/docs/bootableusb.md
@@ -20,9 +20,9 @@ nav_order: 25
2. Place the ISO in a safe place.
-### Flashing using Rufus
+### Flashing using Rufus (Windows)
-For this guide, we will be using Rufus to create our bootable USBs.
+For this guide, we will be using Rufus to create our bootable USB.
1. Download Rufus from [here](https://rufus.ie/en/). The standard Windows x64 version will do.
@@ -31,7 +31,10 @@ For this guide, we will be using Rufus to create our bootable USBs.
2. Plug in your USB.
3. Locate and launch Rufus. It should ask you to launch with administrator privileges, select YES.
4. On the right hand side, there should be a button with the words `SELECT` on it.
-5. A File Explorer window should pop up, find your ISO of choie, then click `Open`.
+5. A File Explorer window should pop up, find your ISO of choice, then click `Open`.
6. Click `Start`. The default options should work just fine.
7. Wait for the green bar to say `READY`, then click `Close` and eject your newly made USB
8. Profit
+
+### Flashing on other opperating systems
+1. Due to dd only able to flash unix-based opperating systems, we reccomend using [Ventoy](https://www.ventoy.net/en/index.html)
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 5e258911..3059fd05 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -10,9 +10,9 @@ nav_order: 4
| **Term** | **Description** |
| - | - |
-| chrultrabook | A modified Chromebook/box designed to run Windows, Linux, or even macOS |
+| chrultrabook | A modified ChromeOS device designed to run Windows, Linux, or even macOS |
| coreboot | UEFI firmware firmware replacement |
-| UEFI | The Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the legacy Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers, with most UEFI firmware implementations providing support for legacy BIOS services. UEFI can support remote diagnostics and repair of computers, even with no operating system installed. (source: Wikipedia) |
+| UEFI | The Unified Extensible Firmware Interface (UEFI) is a new method by which OSes and platform firmware communicate, providing an alternative that uses only the information needed to launch the OS boot process. |
-------------
@@ -36,10 +36,12 @@ Please refer to [this chart](supported-devices.html) for a full list of supporte
* Your iGPU
* Your storage devices (HDD/SSD, eMMC, NVMe, etc.)
* **Your boardname**
+ * For example, the boardname for Asus Chromebook C302CA is ```Cave```
* If you don't know where to find this info, take a look at the [System Info Page.](system-info.html)
* **A basic knowledge of command lines and how to use a terminal/command prompt.**
- * We can't help you if you don't know how to cd to a directory or delete a file.
+ * We cannot help you if you do not know how to go to a directory or delete a file from a terminal.
* A minimum of an 8GB USB drive or SD Card for creating a bootable OS installer.
+* A Chromebook running Ventoy (read [Ventoy](ventoy.html), or another computer running Rufus (read [Making a Bootable USB](bootableusb.html)
------
@@ -49,7 +51,9 @@ If you are facing a issue, please read the [FAQ](faq.html) first.
{: .important }
> When asking for help, ask in English. We can't help you if we don't understand the question. Using a translator is fine.
-**Do not use manufacturer's model name or serial number when asking for help** (i.e: HP Chromebook 14a), it doesn't help with identifying the machine. Provide the boardname, otherwise your support request will be ignored. If you don't know where to find your boardname, take a look [here.](system-info.html)
+**Do not use manufacturer's model name or serial number when asking for help** (i.e: HP Chromebook 14a), it doesn't help with identifying the machine. Provide the boardname, otherwise your support request will be ignored.
+
+If you don't know where to find your boardname, take a look [here](system-info.html)
diff --git a/docs/installing-linux.md b/docs/installing-linux.md
index 337a860d..2661e02a 100644
--- a/docs/installing-linux.md
+++ b/docs/installing-linux.md
@@ -33,6 +33,8 @@ Ubuntu and Ubuntu-based distributions, such as Mint or ElementaryOS are unsuppor
2. Plug the USB Drive into the Chromebook.
3. Turn on the Chromebook, press `ESC` at the POST screen (when the boot logo appears), and select your USB to boot from.
4. Install as you would on any other computer.
+5. (Optional) Install Chultrabook Tools for fan controls, backlight controls, system information and more
+ See [Chrultrabook Controller](https://github.com/death7654/Chrultrabook-Controller)
--------------
diff --git a/docs/installing-windows.md b/docs/installing-windows.md
index 310c14a9..8855ab8e 100644
--- a/docs/installing-windows.md
+++ b/docs/installing-windows.md
@@ -32,7 +32,15 @@ If you want to create a Windows installer from ChromeOS, see the [Installing Ven
{: .warning }
**Do NOT** unplug the install USB until the installation has completed. If you do so, the installation will fail as the Windows install file won't exist anymore.
-3. Bypassing Windows 11 installation checks:
+2. Bypassing Windows 11 installation checks using Rufus (Windows on an another computer):
+ 1. Select your Flashdrive
+ 2. Select your Windows 11 iso in rufus
+ 3. Change Partition Scheme from MBR to GPT
+ 4. Click on ```Start```
+ 5. On the Window named ```Windows User Experience``` click on the option labed ```Remove Requirement for 4GB+ Ram, Secure Boot, and TPM 2.0```
+ 6. Click on ```ok```
+ 7. You can now install Windows 11 normally without extra steps
+4. Bypassing Windows 11 installation checks:
1. At the Windows installer, press Shift + F10 (Volume Up) to open command prompt
2. Type in "regedit" and press enter
3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup
@@ -41,9 +49,12 @@ If you want to create a Windows installer from ChromeOS, see the [Installing Ven
6. Right click LabConfig and create new DWORD (32 bit) called "BypassTPMCheck" and set it to 1
7. Close regedit and command prompt and proceed with installation normally
-4. Install drivers:
+5. Install drivers:
See [Coolstar's Windows Install Helper](https://coolstar.org/chromebook/windows-install.html) for drivers.
+6. (Optional) Install Chultrabook Tools for fan controls, backlight controls, system information and more
+ see [Chrultrabook Controller](https://github.com/death7654/Chrultrabook-Controller)
+
---
### Paid Drivers
diff --git a/docs/unbricking.md b/docs/unbricking.md
index 1c62a38e..a1dc255d 100644
--- a/docs/unbricking.md
+++ b/docs/unbricking.md
@@ -60,7 +60,7 @@ Googling should locate a disassembly guide for most models. If you can't find on
**Prepping to Flash**
-Once you have your device disassembled and flash chip located, time to boot up the flashing environment. Most any Linux setup should do as long as either flashrom is available from the distro's software repositories, or it's 64-bit x86 (in which case you can download a statically compiled build of flashrom from mrchromebox.tech). This guide will use a Ubuntu 23.04 live session booted from USB.
+Once you have your device disassembled and flash chip located, boot up the flashing environment. Most any Linux setup should do as long as either flashrom is available from the distro's software repositories, or it's 64-bit x86 (in which case you can download a statically compiled build of flashrom from mrchromebox.tech). This guide will use a Ubuntu 23.04 live session booted from USB.
So let's get to it:
diff --git a/index.md b/index.md
index 4c639151..a0550051 100644
--- a/index.md
+++ b/index.md
@@ -4,11 +4,11 @@ layout: home
nav_order: 1
---
-Welcome to the Chrultrabook Docs!
+Welcome to the chrultrabook Docs!
-### What is a Chrultrabook and who is this guide for?
+### What is a chrultrabook and who is this guide for?
-A chrultrabook is a modified Chromebook designed to run Windows, Linux, or even macOS by utilizing MrChromebox coreboot firmware. The purpose of this site is to provide comprehensive and user-friendly documentation on hardware, firmware, and operating systems.
+A chrultrabook is a modified Chromebook that is able to run Windows, Linux, or even macOS by using MrChromebox's coreboot firmware. The purpose of this site is to provide documentation that is detailed, user-friendly, and has up to date information about the hardware, software, and firmware on Chromebooks
@@ -21,10 +21,10 @@ A chrultrabook is a modified Chromebook designed to run Windows, Linux, or even
**The docs focuses on two main things:**
-* Installing altOS on your Chromebook.
+* Installing an altOS on your Chromebook.
* Learning in-depth information about your Chromebook.
-Because of this, you will be expected to read, learn, and even use Google. This is not a one click procedure.
+Because of this, you **are** expected to read, learn, and use Google. This is **NOT** a one click procedure.
--------------------------------------
diff --git a/supported-devices/template.md b/supported-devices/template.md
index 4532181b..0e5ee025 100644
--- a/supported-devices/template.md
+++ b/supported-devices/template.md
@@ -3,14 +3,16 @@ NOTE - do not edit the supported-devices.md file, edit the template file in the
-->
## Supported Devices and Platforms
-
-Supported devices are listed in the table below, grouped by platform/family, roughly in chronological order. To reiterate, support is determined entirely and exclusively by the Board Name. Device Names are just for reference, and may be incomplete as many models/sub-models may use the same Board Name. Figure out the Board Name and then locate it in the table. If it's not listed, it's not supported.
+Supported devices are listed in the table below, grouped by platform/family. If your device is not listed, it is not supported. Support is determined entirely and exclusively by the boardname. Use your Chromebook's boardname to see if it has support.
### Determining Device Support
+What's in a name? All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID).
+
+The chart below provides a full list of all ChromeOS devices currently supported by MrChromebox's Firmware Utility Script, the firmware types available for each, the hardware write-protect method used, and notes for Windows, Linux, and macOS operating systems.
-What's in a name? All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID). Your device's board name is what determines if it's supported or not -- not the make, model, CPU, or anything else. The only thing that matters is the name, so use that when determining support in the table below (or for anything else really).
+In most cases, all of the devices in a given platform/family are supported, but sometimes there are exceptions (especially with older or newer devices). The goal is to offer both RW_LEGACY and UEFI Full ROM firmware for all devices, so you may have the option of dual booting ChromeOS, or liberating your device completely :)
-The chart below provides a full, authoritative list of all ChromeOS devices currently supported by MrChromebox's Firmware Utility Script, the firmware types available for each, and the hardware write-protect method used. In most cases, all of the devices in a given platform/family are supported identically, but sometimes there are outliers (esp with older or newer devices). The goal is to offer both RW_LEGACY and UEFI Full ROM firmware for all devices wherever possible, so you have the option of dual booting ChromeOS, or liberating your device completely :)
+Be aware that EOL (End Of Life) devices **DO NOT** have RW_Legacy avaliable
### OS Support