From 6be3490d4d751eaa4af3823d3fd6eacb55a4b9bf Mon Sep 17 00:00:00 2001
From: Paul Kocialkowski <contact@paulk.fr>
Date: Fri, 06 Nov 2015 13:10:44 -0500
Subject: Replace Chromebook mentions with CrOS, that is more generic

Not all CrOS devices are Chromebooks (laptops) or run on ARM, not all RK3288
CrOS devices are Chromebooks, either.

We want to support more CrOS devices, including some that are not Chromebooks,
such as the ASUS Chromebit!

Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
---
(limited to 'docs')

diff --git a/docs/depthcharge/index.html b/docs/depthcharge/index.html
index d30c2e0..210cde5 100644
--- a/docs/depthcharge/index.html
+++ b/docs/depthcharge/index.html
@@ -26,7 +26,7 @@
 		</p>
 
 		<ul>
-			<li><a href="#chromebook_security_model">Chromebook security model</a></li>
+			<li><a href="#cros_security_model">CrOS security model</a></li>
 			<li><a href="#developer_mode_screen">Developer mode screen</a>
 				<ul>
 					<li><a href="#holding_developer_mode_screen">Holding the developer mode screen</li>
@@ -49,18 +49,18 @@
 
 	<div class="section">
 
-		<h1 id="chromebook_security_model">Chromebook security model</h1>
+		<h1 id="cros_security_model">CrOS security model</h1>
 
 		<p>
-			Chromebooks implement a strict security model to ensure that these devices do not become compromised,
+			CrOS (Chromium OS/Chrome OS) devices such as Chromebooks implement a strict security model to ensure that these devices do not become compromised,
 			that is implemented as the verified boot (vboot) reference, most of which is executed within depthcharge.
-			A detailed overview of the Chromebook security model is available on the dedicated page.
+			A detailed overview of the CrOS security model is available on the dedicated page.
 		</p>
 
 		<div class="subsection">
 
 			<p>
-				In spite of the Chromebook security model, depthcharge won't allow booting kernels without verifying their signature and booting from external media or legacy payload unless explicitly allowed: see <a href="#configuring_verified_boot_parameters">configuring verified boot parameters</a>.
+				In spite of the CrOS security model, depthcharge won't allow booting kernels without verifying their signature and booting from external media or legacy payload unless explicitly allowed: see <a href="#configuring_verified_boot_parameters">configuring verified boot parameters</a>.
 			</p>
 
 		</div>
diff --git a/docs/gnulinux/grub_boot_installer.html b/docs/gnulinux/grub_boot_installer.html
index 6ba5704..ee833e2 100644
--- a/docs/gnulinux/grub_boot_installer.html
+++ b/docs/gnulinux/grub_boot_installer.html
@@ -34,7 +34,7 @@
 
 	<div class="section">
 		<p>
-			<b>This section is only for the *GRUB* payload. For depthcharge (used on ARM chromebooks in libreboot), instructions
+			<b>This section is only for the GRUB payload. For depthcharge (used on CrOS devices in libreboot), instructions
 			have yet to be written in the libreboot documentation.</b>
 		</p>
 	</div>
diff --git a/docs/hcl/c201.html b/docs/hcl/c201.html
index ab51a96..65d78b5 100644
--- a/docs/hcl/c201.html
+++ b/docs/hcl/c201.html
@@ -17,7 +17,7 @@
 		<h1 id="pagetop">ASUS Chromebook C201</h1>
 
 			<p>
-				This is a chromebook, using the Rockchip RK3288 SoC. It uses
+				This is a Chromebook, using the Rockchip RK3288 SoC. It uses
 				an ARM CPU, and has free EC firmware (unlike some other laptops).
 				More RK3288-based laptops will be added to libreboot at a later date.
 			</p>
@@ -51,7 +51,7 @@
 
 	<div class="section">
 		<ul>
-			<li><a href="#googlesintent">Google's intent with Chromebooks</a></li>
+			<li><a href="#googlesintent">Google's intent with CrOS devices</a></li>
 			<li><a href="#os">Considerations about ChromeOS and free operating systems</a></li>
 			<li><a href="#videoblobs">Caution: Video acceleration requires a non-free blob, software rendering can be used instead.</a></li>
 			<li><a href="#wifiblobs">Caution: WiFi requires a non-free blob, a USB dongle can be used instead.</a></li>
@@ -63,17 +63,17 @@
 	</div>
 	
 	<div class="section">
-		<h1 id="googlesintent">Google's intent with Chromebooks</h1>
+		<h1 id="googlesintent">Google's intent with CrOS devices</h1>
 			<p>
-				Chromebooks were not designed with the intent of bringing more freedom to users.
-				However, Chromebooks run with a lot of free software at the boot software and embedded controller levels,
+				CrOS (Chromium OS/Chrome OS) devices, such as Chromebooks, were not designed with the intent of bringing more freedom to users.
+				However, they run with a lot of free software at the boot software and embedded controller levels,
 				since free software gives Google enough flexibility to optimize various aspects such as boot time
-				and most importantly, to implement the Chromebook security system, that involves various aspects of the software.
+				and most importantly, to implement the CrOS security system, that involves various aspects of the software.
 				Google does hire a lot of Coreboot developers, who are generally friendly to the free software movement
 				and try to be good members of the free software community, by contributing code back.
 			</p>
 			<p>
-				Chromebooks are designed (from the factory) to actually coax the user into using
+				CrOS devices are designed (from the factory) to actually coax the user into using
 				<a href="https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html">proprietary web services</a>
 				(SaaSS) that invade the user's privacy (ChromeOS is literally just the Google Chrome browser when you boot up, itself proprietary
 				and comes with proprietary add-ons like flash. It's only intended for SaaSS, not actual, real computing).
@@ -101,7 +101,7 @@
 			<h2>No FSF-endorsed distros available</h2>
 				<p>
 					The FSF has a <a href="https://www.gnu.org/distros/free-distros.html">list of distributions</a> that are 100% free software. None of these
-					are confirmed to work on ARM chromebooks yet. Parabola looks hopeful:
+					are confirmed to work on ARM CrOS devices yet. Parabola looks hopeful:
 					<a href="https://www.parabola.nu/news/parabola-supports-armv7/">https://www.parabola.nu/news/parabola-supports-armv7/</a>
 				</p>
 				<p>
@@ -199,7 +199,7 @@
 		<h1 id="depthcharge">Depthcharge payload</h1>
 			<p>
 				These systems do not use the GRUB payload. Instead, they use a payload called depthcharge,
-				which is common on Chromebooks. This is free software, maintained by Google.
+				which is common on CrOS devices. This is free software, maintained by Google.
 			</p>
 	</div>
 
@@ -219,8 +219,8 @@
 			<p>
 				Write protection is useful, because it prevents the firmware from being re-flashed by any malicious software that
 				might become executed on your GNU/Linux system, as root. In other words, it can prevent a firmware-level <i>evil maid</i> attack. It's
-				possible to write protect on all current libreboot systems, but chromebooks make it easy. The screw is such a stupidly
-				simple idea, which all laptop designs should implement.
+				possible to write protect on all current libreboot systems, but CrOS devices make it easy. The screw is such a stupidly
+				simple idea, which all designs should implement.
 			</p>
 	</div>
 
diff --git a/docs/install/c201.html b/docs/install/c201.html
index f0e7616..d0a8085 100644
--- a/docs/install/c201.html
+++ b/docs/install/c201.html
@@ -158,7 +158,7 @@
 		<h1 id="installing_libreboot_spi_flash">Installing Libreboot to the SPI flash</h1>
 
 		<p>
-			The SPI flash (that holds Libreboot) is divided into various partitions that are used to implement parts of the Chromebook security system.
+			The SPI flash (that holds Libreboot) is divided into various partitions that are used to implement parts of the CrOS security system.
 			Libreboot is installed in the <i>read-only</i> coreboot partition, that becomes writable after removing the write-protect screw.
 		</p>
 
diff --git a/docs/tasks.html b/docs/tasks.html
index 4054749..3121e54 100644
--- a/docs/tasks.html
+++ b/docs/tasks.html
@@ -102,7 +102,7 @@
 						</li>
 						<li>
 							<ul>
-								<li>ASUS Chromebook C201 was added, but there are also other RK3288 based laptops in coreboot. Port them all!</li>
+								<li>ASUS Chromebook C201 was added, but there are also other RK3288 based devices in coreboot. Port them all!</li>
 								<li>Other ARM based systems; tegra124 chromebooks, Jetson TK1 (non-free GPU microcode in kernel needs replacing. also xhci firmware, but optional (can still use ehci, we think))</li>
 							</ul>
 						</li>
@@ -442,7 +442,7 @@
 				have EC in the main chip, some don't use SPI flash at all but have the firmware inside the EC chip itself.
 				If the EC has integrated flash then you need to be able to get to the pins on the chip or be able to program them over LPC or SPI (if they have that feature).
 				The lenovo laptops currently supported in libreboot all use H8 EC chips (contains flash inside the chip).
-				Read the datasheets on how to externally flash the EC. Chromebooks seem to have free EC
+				Read the datasheets on how to externally flash the EC. Most CrOS devices run with a free EC firmware
 				(<a href="https://chromium.googlesource.com/chromiumos/platform/ec/+/master/chip/">https://chromium.googlesource.com/chromiumos/platform/ec/+/master/chip/</a>).
 				- see
 				<a href="http://blogs.coreboot.org/blog/2015/05/28/progress-gsoc-week-1/">http://blogs.coreboot.org/blog/2015/05/28/progress-gsoc-week-1/</a> (H8S EC, applies to thinkpads)
--
cgit v0.9.1