From 6be3490d4d751eaa4af3823d3fd6eacb55a4b9bf Mon Sep 17 00:00:00 2001
From: Paul Kocialkowski <contact@paulk.fr>
Date: Fri, 6 Nov 2015 19:10:44 +0100
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>
---
 docs/depthcharge/index.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'docs/depthcharge')

diff --git a/docs/depthcharge/index.html b/docs/depthcharge/index.html
index d30c2e07..210cde55 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>
-- 
cgit v1.2.3-70-g09d2