summaryrefslogtreecommitdiff
path: root/Documentation/RFC
diff options
context:
space:
mode:
authorJonathan Neuschäfer <j.neuschaefer@gmx.net>2018-04-09 13:05:29 +0200
committerPatrick Georgi <pgeorgi@google.com>2018-04-10 10:50:06 +0000
commit8ee93ae26786c11f5169aedceb5b2670ff53568a (patch)
treeead95aded2e49b14c8500f23a4f9ac87487da5dd /Documentation/RFC
parent7fa9f73ac7b55272f15236a019f07c468b1f05c9 (diff)
Documentation: Fix a bunch of typos
Change-Id: I25dca2e231343cfdad61a638f0302726a6aa3f8b Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Reviewed-on: https://review.coreboot.org/25571 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'Documentation/RFC')
-rw-r--r--Documentation/RFC/chip.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/RFC/chip.tex b/Documentation/RFC/chip.tex
index 5e366b8461..01f40c1e80 100644
--- a/Documentation/RFC/chip.tex
+++ b/Documentation/RFC/chip.tex
@@ -14,7 +14,7 @@ as southbridges. Multiple chips of same or different type are supported.
\section{Goals}
The goals of the new chip architecture are these:
\begin{itemize}
-\item seperate implementation details from specification in the Config file
+\item separate implementation details from specification in the Config file
(translation: no more C code in Config files)
\item make the specification easier for people to use and understand
\item remove private details of a given chip to the chip file as much
@@ -223,7 +223,7 @@ struct configuration {
const char *value;
};
-These get filled in by the config tool as before. The linuxbios libary can
+These get filled in by the config tool as before. The linuxbios library can
then provide a generic parsing function for the superios to use.
The remaining question is how should the superio command look in