summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-01-29 10:04:04 (EST)
committer Francis Rowe <info@gluglug.org.uk>2015-01-29 10:04:04 (EST)
commit3ec7d19de31d26e41ad5124f4f13cc1d3743071a (patch)
treec3f7d39a03cec37ae0629d5d52c9c400237e3eac
parent4e0e050a5ff09045a66f81dc3c3740f8828f8ce1 (diff)
downloadlibreboot-3ec7d19de31d26e41ad5124f4f13cc1d3743071a.zip
libreboot-3ec7d19de31d26e41ad5124f4f13cc1d3743071a.tar.gz
libreboot-3ec7d19de31d26e41ad5124f4f13cc1d3743071a.tar.bz2
typo.
-rw-r--r--docs/index.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/index.html b/docs/index.html
index 54c8d75..214f2e5 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -162,7 +162,7 @@
<b>
As such, all new coreboot development should be done in coreboot, not libreboot!
Libreboot is about deblobbing, and packaging coreboot in a user-friendly way, where most work is already done for the user!
- If, for example you wanted to attempt porting a new motherboard then you should do that in coreboot. Libreboot will (as a downstream)
+ If, for example you wanted to attempt porting a new motherboard then you should do that in coreboot. Libreboot will (as a downstream supplier)
receive your change at some point in the future, in a future release.
</b>
</p>