summaryrefslogtreecommitdiffstats
path: root/site
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-07-28 06:27:12 (EDT)
committer Francis Rowe <info@gluglug.org.uk>2015-07-28 06:27:12 (EDT)
commit2d281639cb81cc91f33a9c8861b1f0fa0a465503 (patch)
tree7aa6686b7e35532463c62f26f63c32e70991224b /site
parent561cfa8768099d50ebf3c859205596bccc6b35b4 (diff)
downloadlibreboot.org-2d281639cb81cc91f33a9c8861b1f0fa0a465503.zip
libreboot.org-2d281639cb81cc91f33a9c8861b1f0fa0a465503.tar.gz
libreboot.org-2d281639cb81cc91f33a9c8861b1f0fa0a465503.tar.bz2
clarify (2)
Diffstat (limited to 'site')
-rw-r--r--site/faq/index.php2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index 5579623..cea79d8 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -292,7 +292,7 @@
<p>
By default, there is no write-protection on a libreboot system. This is for usability reasons,
because most people do not have easy access to an external programmer for re-flashing their firmware,
- or they find it inconvenient to use.
+ or they find it inconvenient to use an external programmer.
</p>
<p>
On some systems, it is possible to write-protect the firmware, such that it is rendered read-only