Patrick Georgi has submitted this change and it was merged. ( https://review.coreboot.org/25571 )
Change subject: Documentation: Fix a bunch of typos ......................................................................
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 --- M Documentation/Intel/NativeRaminit/SandyBridge_registers.md M Documentation/Lesson2.md M Documentation/RFC/chip.tex M Documentation/cbfs.txt M Documentation/corebootBuildingGuide.tex 5 files changed, 11 insertions(+), 11 deletions(-)
Approvals: build bot (Jenkins): Verified Patrick Georgi: Looks good to me, approved Arthur Heymans: Looks good to me, approved
diff --git a/Documentation/Intel/NativeRaminit/SandyBridge_registers.md b/Documentation/Intel/NativeRaminit/SandyBridge_registers.md index 2dce11b..c961890 100644 --- a/Documentation/Intel/NativeRaminit/SandyBridge_registers.md +++ b/Documentation/Intel/NativeRaminit/SandyBridge_registers.md @@ -966,7 +966,7 @@
*Width:* 24 Bit
-*Desc:* TC_DBP - Timming of DDR - Bin Parameter Register, Channel 0 +*Desc:* TC_DBP - Timing of DDR - Bin Parameter Register, Channel 0
|Bit| Description | |---|-------------| diff --git a/Documentation/Lesson2.md b/Documentation/Lesson2.md index 0263ced..ec929c8 100644 --- a/Documentation/Lesson2.md +++ b/Documentation/Lesson2.md @@ -20,7 +20,7 @@ https://gerrit-documentation.storage.googleapis.com/Documentation/2.14.2/user-upload.html#configure_ssh) and follow the instructions there. Then, skip to Part 3.
-Additonally, that section of the Web site provides explanation on starting +Additionally, that section of the Web site provides explanation on starting an ssh-agent, which may be particularly helpful for those who anticipate frequently uploading changes.
@@ -110,7 +110,7 @@
git commit -s
-**Note:** The -s adds a signed-off-by line by the commiter. Your commit should be +**Note:** The -s adds a signed-off-by line by the committer. Your commit should be signed off with your name and email (i.e. **Your Name** **<Your Email>**, based on what you set with git config earlier).
@@ -236,7 +236,7 @@ git clone https://github.com/magicmonty/bash-git-prompt.git .bash-git-prompt --depth=1
**Note:** cd will change your directory to your home directory, so the -git clone commmand will be run there. +git clone command will be run there.
Finally, open the ~/.bashrc file and append the following two lines:
diff --git a/Documentation/RFC/chip.tex b/Documentation/RFC/chip.tex index 5e366b8..01f40c1 100644 --- a/Documentation/RFC/chip.tex +++ b/Documentation/RFC/chip.tex @@ -14,7 +14,7 @@ \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 @@ 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 diff --git a/Documentation/cbfs.txt b/Documentation/cbfs.txt index 6c5c228..7adae61 100644 --- a/Documentation/cbfs.txt +++ b/Documentation/cbfs.txt @@ -36,7 +36,7 @@ The header on each "file" (or component, as I like to style them) has been simplified - We now only store the length, the type, the checksum, and the offset to the data. The name scheme remains the same. The -addtional information, which is component specific, has been moved to +additional information, which is component specific, has been moved to the component itself (see below).
The components are arranged in the ROM aligned along the specified @@ -245,7 +245,7 @@ | ... | --------/ <- start + 'offset' + 'len'
-== Searching Alogrithm == +== Searching Algorithm ==
To locate a specific component in the ROM, one starts at the 'offset' specified in the CBFS master header. For this example, the offset will @@ -379,7 +379,7 @@
PAYLOAD_SEGMENT_CODE 0x45444F43 The segment contains executable code PAYLOAD_SEGMENT_DATA 0x41544144 The segment contains data -PAYLOAD_SEGMENT_BSS 0x20535342 The memory speicfied by the segment +PAYLOAD_SEGMENT_BSS 0x20535342 The memory specified by the segment should be zeroed PAYLOAD_SEGMENT_PARAMS 0x41524150 The segment contains information for the payload diff --git a/Documentation/corebootBuildingGuide.tex b/Documentation/corebootBuildingGuide.tex index 867891b..e451ad4 100644 --- a/Documentation/corebootBuildingGuide.tex +++ b/Documentation/corebootBuildingGuide.tex @@ -413,8 +413,8 @@ \end{verbatim} }
-% Does anyone have a better word to describe the phylosophy of spliting changes to patches? -You need to realize that the changes you have made should be well devided into +% Does anyone have a better word to describe the philosophy of splitting changes to patches? +You need to realize that the changes you have made should be well divided into several commits. Each of them has one and only one meaning. You could use git rebase -i to split, squash, remove, rewrite you comment.