aboutsummaryrefslogtreecommitdiff
path: root/docs/hcl/c201.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/hcl/c201.md')
-rw-r--r--docs/hcl/c201.md26
1 files changed, 13 insertions, 13 deletions
diff --git a/docs/hcl/c201.md b/docs/hcl/c201.md
index c8262d1f..ada724d1 100644
--- a/docs/hcl/c201.md
+++ b/docs/hcl/c201.md
@@ -20,7 +20,7 @@ Flashing instructions can be found at
-- [Google\'s intent with CrOS devices](#googlesintent)
+- [Google's intent with CrOS devices](#googlesintent)
- [Considerations about ChromeOS and free operating systems](#os)
- [Caution: Video acceleration requires a non-free blob, software
rendering can be used instead.](#videoblobs)
@@ -33,7 +33,7 @@ Flashing instructions can be found at
-Google\'s intent with CrOS devices {#googlesintent}
+Google's intent with CrOS devices {#googlesintent}
==================================
CrOS (Chromium OS/Chrome OS) devices, such as Chromebooks, were not
@@ -47,14 +47,14 @@ generally friendly to the free software movement and try to be good
members of the free software community, by contributing code back.
CrOS devices are designed (from the factory) to actually coax the user
-into using proprietary web services (SaaSS) that invade the user\'s
+into using proprietary web services (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).
+flash. It's only intended for SaaSS, not actual, real computing).
Google is even a member of the *PRISM* program, as outlined by Edward
Snowden. See notes about ChromeOS below. The libreboot project
recommends that the user replace the default *ChromeOS* with a
-distribution that can be used in freedom, without invading the user\'s
+distribution that can be used in freedom, without invading the user's
privacy.
We also use a similar argument for the MacBook and the ThinkPads that
@@ -70,8 +70,8 @@ Considerations about ChromeOS and free operating systems {#os}
========================================================
This laptop comes preinstalled (from the factory) with Google ChromeOS.
-This is a GNU+Linux distribution, but it\'s not general purpose and it
-comes with proprietary software. It\'s designed for SaaSS. Libreboot
+This is a GNU+Linux distribution, but it's not general purpose and it
+comes with proprietary software. It's designed for SaaSS. Libreboot
recommends that users of this laptop replace it with another
distribution.
@@ -101,7 +101,7 @@ tasks can still be performed without video acceleration, without any
noticeable performance penalty.
In practise, this means that certain things like games, blender and
-GNOME shell (or other fancy desktops) won\'t work well. The libreboot
+GNOME shell (or other fancy desktops) won't work well. The libreboot
project recommends a lightweight desktop which does not need video
acceleration, such as *XFCE* or *LXDE*.
@@ -143,7 +143,7 @@ too.
EC firmware is free software! {#ec}
=============================
-It\'s free software. Google provides the source. Build scripts will be
+It's free software. Google provides the source. Build scripts will be
added later, with EC sources provided in libreboot, and builds of the EC
firmware.
@@ -163,7 +163,7 @@ No microcode! {#microcode}
Unlike x86 (e.g. Intel/AMD) CPUs, ARM CPUs do not use microcode, not
even built in. On the Intel/AMD based libreboot systems, there is still
microcode in the CPU (not considered problematic by the FSF, provided
-that it is reasonably trusted to not be malicious, since it\'s part of
+that it is reasonably trusted to not be malicious, since it's part of
the hardware and read-only), but we exclude microcode updates (volatile
updates which are uploaded at boot time by the boot firmware, if
present), which are proprietary software.
@@ -187,8 +187,8 @@ software, maintained by Google.
Flash chip write protection: the screw {#thescrew}
======================================
-It\'s next to the flash chip. Unscrew it, and the flash chip is
-read-write. Screw it back in, and the flash chip is read-only. It\'s
+It's next to the flash chip. Unscrew it, and the flash chip is
+read-write. Screw it back in, and the flash chip is read-only. It's
called the screw.
*The screw* is accessible by removing other screws and gently prying off
@@ -203,7 +203,7 @@ of how to set up an SPI programmer.
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 *evil maid* attack. It\'s possible to write protect on
+firmware-level *evil maid* attack. It's 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.