From 20db314e79ba5e8e3da635ff453cbcaa1e38e1d5 Mon Sep 17 00:00:00 2001
From: Francis Rowe <info@gluglug.org.uk>
Date: Sat, 12 Sep 2015 18:24:47 -0400
Subject: FAQ: ME: clearly explain where we mean the main OS, not the ME OS

---
(limited to 'site/faq/index.php')

diff --git a/site/faq/index.php b/site/faq/index.php
index 419384d..2691b91 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -120,7 +120,7 @@
 				<h3 id="intelme">Intel Management Engine (ME) <span class="ref">(<a href="#intelme">#intelme</a>)</span></h3>
 					<p>
 						The ME is a separate processor that exists in all Intel chipsets past the year ~2006, running its own embedded (and proprietary) operating system, referred to as the ME <i>firmware</i> in this article. It provides remote access capabilities,
-						independently from the running operating system, with full access to RAM, and full networking support. <i>With a functioning ME, your system
+						independently from the running operating system on the main CPU, with full access to RAM, and full networking support. <i>With a functioning ME, your system
 						is left wide open for attack. It can also phone home to Intel.</i> It also handles the
 						TPM, AMT (<a href="https://www.fsf.org/blogs/community/active-management-technology">Active Management Technology</a>), <a href="https://mjg59.dreamwidth.org/33981.html">Boot Guard</a> and various <a href="https://defectivebydesign.org/what_is_drm_digital_restrictions_management">DRM</a> mechanisms.
 						The ME also performs some basic hardware initialization and power management, on recent systems.
--
cgit v0.9.1