From 8ee93ae26786c11f5169aedceb5b2670ff53568a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonathan=20Neusch=C3=A4fer?= Date: Mon, 9 Apr 2018 13:05:29 +0200 Subject: Documentation: Fix a bunch of typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I25dca2e231343cfdad61a638f0302726a6aa3f8b Signed-off-by: Jonathan Neuschäfer Reviewed-on: https://review.coreboot.org/25571 Tested-by: build bot (Jenkins) Reviewed-by: Arthur Heymans Reviewed-by: Patrick Georgi --- Documentation/RFC/chip.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Documentation/RFC') diff --git a/Documentation/RFC/chip.tex b/Documentation/RFC/chip.tex index 5e366b8461f0..01f40c1e803a 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 -- cgit v1.2.3