<p>Patrick Georgi <strong>merged</strong> this change.</p><p><a href="https://review.coreboot.org/25571">View Change</a></p><div style="white-space:pre-wrap">Approvals:
build bot (Jenkins): Verified
Patrick Georgi: Looks good to me, approved
Arthur Heymans: Looks good to me, approved
</div><pre style="font-family: monospace,monospace; white-space: pre-wrap;">Documentation: Fix a bunch of typos<br><br>Change-Id: I25dca2e231343cfdad61a638f0302726a6aa3f8b<br>Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net><br>Reviewed-on: https://review.coreboot.org/25571<br>Tested-by: build bot (Jenkins) <no-reply@coreboot.org><br>Reviewed-by: Arthur Heymans <arthur@aheymans.xyz><br>Reviewed-by: Patrick Georgi <pgeorgi@google.com><br>---<br>M Documentation/Intel/NativeRaminit/SandyBridge_registers.md<br>M Documentation/Lesson2.md<br>M Documentation/RFC/chip.tex<br>M Documentation/cbfs.txt<br>M Documentation/corebootBuildingGuide.tex<br>5 files changed, 11 insertions(+), 11 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;"><span>diff --git a/Documentation/Intel/NativeRaminit/SandyBridge_registers.md b/Documentation/Intel/NativeRaminit/SandyBridge_registers.md</span><br><span>index 2dce11b..c961890 100644</span><br><span>--- a/Documentation/Intel/NativeRaminit/SandyBridge_registers.md</span><br><span>+++ b/Documentation/Intel/NativeRaminit/SandyBridge_registers.md</span><br><span>@@ -966,7 +966,7 @@</span><br><span> </span><br><span> *Width:* 24 Bit</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-*Desc:* TC_DBP - Timming of DDR - Bin Parameter Register, Channel 0</span><br><span style="color: hsl(120, 100%, 40%);">+*Desc:* TC_DBP - Timing of DDR - Bin Parameter Register, Channel 0</span><br><span> </span><br><span> |Bit| Description |</span><br><span> |---|-------------|</span><br><span>diff --git a/Documentation/Lesson2.md b/Documentation/Lesson2.md</span><br><span>index 0263ced..ec929c8 100644</span><br><span>--- a/Documentation/Lesson2.md</span><br><span>+++ b/Documentation/Lesson2.md</span><br><span>@@ -20,7 +20,7 @@</span><br><span> <https://gerrit-documentation.storage.googleapis.com/Documentation/2.14.2/user-upload.html#configure_ssh)></span><br><span> and follow the instructions there. Then, skip to Part 3.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Additonally, that section of the Web site provides explanation on starting</span><br><span style="color: hsl(120, 100%, 40%);">+Additionally, that section of the Web site provides explanation on starting</span><br><span> an ssh-agent, which may be particularly helpful for those who anticipate</span><br><span> frequently uploading changes.</span><br><span> </span><br><span>@@ -110,7 +110,7 @@</span><br><span> </span><br><span> git commit -s</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-**Note:** The -s adds a signed-off-by line by the commiter. Your commit should be</span><br><span style="color: hsl(120, 100%, 40%);">+**Note:** The -s adds a signed-off-by line by the committer. Your commit should be</span><br><span> signed off with your name and email (i.e. **Your Name** **<Your Email>**, based on</span><br><span> what you set with git config earlier).</span><br><span> </span><br><span>@@ -236,7 +236,7 @@</span><br><span> git clone https://github.com/magicmonty/bash-git-prompt.git .bash-git-prompt --depth=1</span><br><span> </span><br><span> **Note:** cd will change your directory to your home directory, so the</span><br><span style="color: hsl(0, 100%, 40%);">-git clone commmand will be run there.</span><br><span style="color: hsl(120, 100%, 40%);">+git clone command will be run there.</span><br><span> </span><br><span> Finally, open the ~/.bashrc file and append the following two lines:</span><br><span> </span><br><span>diff --git a/Documentation/RFC/chip.tex b/Documentation/RFC/chip.tex</span><br><span>index 5e366b8..01f40c1 100644</span><br><span>--- a/Documentation/RFC/chip.tex</span><br><span>+++ b/Documentation/RFC/chip.tex</span><br><span>@@ -14,7 +14,7 @@</span><br><span> \section{Goals}</span><br><span> The goals of the new chip architecture are these:</span><br><span> \begin{itemize}</span><br><span style="color: hsl(0, 100%, 40%);">-\item seperate implementation details from specification in the Config file</span><br><span style="color: hsl(120, 100%, 40%);">+\item separate implementation details from specification in the Config file</span><br><span> (translation: no more C code in Config files)</span><br><span> \item make the specification easier for people to use and understand</span><br><span> \item remove private details of a given chip to the chip file as much</span><br><span>@@ -223,7 +223,7 @@</span><br><span> const char *value;</span><br><span> };</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-These get filled in by the config tool as before. The linuxbios libary can</span><br><span style="color: hsl(120, 100%, 40%);">+These get filled in by the config tool as before. The linuxbios library can</span><br><span> then provide a generic parsing function for the superios to use.</span><br><span> </span><br><span> The remaining question is how should the superio command look in</span><br><span>diff --git a/Documentation/cbfs.txt b/Documentation/cbfs.txt</span><br><span>index 6c5c228..7adae61 100644</span><br><span>--- a/Documentation/cbfs.txt</span><br><span>+++ b/Documentation/cbfs.txt</span><br><span>@@ -36,7 +36,7 @@</span><br><span> The header on each "file" (or component, as I like to style them) has</span><br><span> been simplified - We now only store the length, the type, the checksum,</span><br><span> and the offset to the data. The name scheme remains the same. The</span><br><span style="color: hsl(0, 100%, 40%);">-addtional information, which is component specific, has been moved to</span><br><span style="color: hsl(120, 100%, 40%);">+additional information, which is component specific, has been moved to</span><br><span> the component itself (see below).</span><br><span> </span><br><span> The components are arranged in the ROM aligned along the specified</span><br><span>@@ -245,7 +245,7 @@</span><br><span> | ... |</span><br><span> \--------/ <- start + 'offset' + 'len'</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-== Searching Alogrithm ==</span><br><span style="color: hsl(120, 100%, 40%);">+== Searching Algorithm ==</span><br><span> </span><br><span> To locate a specific component in the ROM, one starts at the 'offset'</span><br><span> specified in the CBFS master header. For this example, the offset will</span><br><span>@@ -379,7 +379,7 @@</span><br><span> </span><br><span> PAYLOAD_SEGMENT_CODE 0x45444F43 The segment contains executable code</span><br><span> PAYLOAD_SEGMENT_DATA 0x41544144 The segment contains data</span><br><span style="color: hsl(0, 100%, 40%);">-PAYLOAD_SEGMENT_BSS 0x20535342 The memory speicfied by the segment</span><br><span style="color: hsl(120, 100%, 40%);">+PAYLOAD_SEGMENT_BSS 0x20535342 The memory specified by the segment</span><br><span> should be zeroed</span><br><span> PAYLOAD_SEGMENT_PARAMS 0x41524150 The segment contains information for</span><br><span> the payload</span><br><span>diff --git a/Documentation/corebootBuildingGuide.tex b/Documentation/corebootBuildingGuide.tex</span><br><span>index 867891b..e451ad4 100644</span><br><span>--- a/Documentation/corebootBuildingGuide.tex</span><br><span>+++ b/Documentation/corebootBuildingGuide.tex</span><br><span>@@ -413,8 +413,8 @@</span><br><span> \end{verbatim}</span><br><span> }</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-% Does anyone have a better word to describe the phylosophy of spliting changes to patches?</span><br><span style="color: hsl(0, 100%, 40%);">-You need to realize that the changes you have made should be well devided into</span><br><span style="color: hsl(120, 100%, 40%);">+% Does anyone have a better word to describe the philosophy of splitting changes to patches?</span><br><span style="color: hsl(120, 100%, 40%);">+You need to realize that the changes you have made should be well divided into</span><br><span> several commits. Each of them has one and only one meaning. You could use git rebase -i to</span><br><span> split, squash, remove, rewrite you comment.</span><br><span> </span><br><span></span><br></pre><p>To view, visit <a href="https://review.coreboot.org/25571">change 25571</a>. To unsubscribe, or for help writing mail filters, visit <a href="https://review.coreboot.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://review.coreboot.org/25571"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: coreboot </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-MessageType: merged </div>
<div style="display:none"> Gerrit-Change-Id: I25dca2e231343cfdad61a638f0302726a6aa3f8b </div>
<div style="display:none"> Gerrit-Change-Number: 25571 </div>
<div style="display:none"> Gerrit-PatchSet: 2 </div>
<div style="display:none"> Gerrit-Owner: Jonathan Neuschäfer <j.neuschaefer@gmx.net> </div>
<div style="display:none"> Gerrit-Reviewer: Arthur Heymans <arthur@aheymans.xyz> </div>
<div style="display:none"> Gerrit-Reviewer: Patrick Georgi <pgeorgi@google.com> </div>
<div style="display:none"> Gerrit-Reviewer: build bot (Jenkins) <no-reply@coreboot.org> </div>