summaryrefslogtreecommitdiffstats
path: root/site
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-07-28 06:26:29 (EDT)
committer Francis Rowe <info@gluglug.org.uk>2015-07-28 06:26:29 (EDT)
commit561cfa8768099d50ebf3c859205596bccc6b35b4 (patch)
treef6cf3ba909ce0e3ea600d786dedf38226a07327a /site
parent80d5f6fe496bb0dcf0069f73e971f7497220f602 (diff)
downloadlibreboot.org-561cfa8768099d50ebf3c859205596bccc6b35b4.zip
libreboot.org-561cfa8768099d50ebf3c859205596bccc6b35b4.tar.gz
libreboot.org-561cfa8768099d50ebf3c859205596bccc6b35b4.tar.bz2
clarify
Diffstat (limited to 'site')
-rw-r--r--site/faq/index.php3
1 files changed, 2 insertions, 1 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index 944f361..5579623 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -291,7 +291,8 @@
<h2 id="writeprotect">How do I write-protect the flash chip?</h2>
<p>
By default, there is no write-protection on a libreboot system. This is for usability reasons,
- because most people do not have access to an external programmer for re-flashing their firmware.
+ because most people do not have easy access to an external programmer for re-flashing their firmware,
+ or they find it inconvenient to use.
</p>
<p>
On some systems, it is possible to write-protect the firmware, such that it is rendered read-only