Skip to content

Commit f7add9a

Browse files
committed
doc: Fix 2 typos.
1 parent a84174b commit f7add9a

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

docs/avr-libc-user-manual-2.3.0/FAQ.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1267,7 +1267,7 @@ <h1><a class="anchor" id="faq_toolchain_version"></a>
12671267
<td>AVR-LibC </td><td><code>echo "#include &lt;avr/version.h&gt;" | avr-gcc -xc - -E -dM | grep AVR_LIBC_VERSION_STRING</code> </td></tr>
12681268
</table>
12691269
<p>Linker<sup>1</sup> is the linker as called directly (<code>avr-ld</code>) whereas Linker<sup>2</sup> is the linker as called though the compiler driver <code>avr-gcc</code>. The latter is the usual way to invoke the linker. When these two versions are not the same, then the resulting toolchain may have inconsistencies.</p>
1270-
<p>When you have more then one toolchain installed, then make sure you are calling the command from the intended toolchain, e.g. by specifying the absolute path to the tool.</p>
1270+
<p>When you have more than one toolchain installed, then make sure you are calling the command from the intended toolchain, e.g. by specifying the absolute path to the tool.</p>
12711271
<p>Also notice that software may come with vendor specific patches, so that the tool behaves differently than the stock version.</p>
12721272
<p><small>Back to <a class="el" href="FAQ.html#faq_index">FAQ Index</a>.</small></p>
12731273
<h1><a class="anchor" id="faq_toolchain_sources"></a>

docs/avr-libc-user-manual-2.3.0/install_tools.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,7 @@ <h2><a class="anchor" id="install_avr_gcc"></a>
285285
<h2><a class="anchor" id="install_avr_libc"></a>
286286
AVR-LibC</h2>
287287
<p><a id="a9_installation:2C:20avr-libc" name="a9_installation:2C:20avr-libc"></a></p>
288-
<dl class="section warning"><dt>Warning</dt><dd>You <b>must</b> install <a class="el" href="install_tools.html#install_avr_binutils">avr-binutils</a>, <a class="el" href="install_tools.html#install_avr_gcc">avr-gcc</a> and make sure your <a class="el" href="install_tools.html#path">path is set</a> properly before configuring abd building AVR-LibC.</dd></dl>
288+
<dl class="section warning"><dt>Warning</dt><dd>You <b>must</b> install <a class="el" href="install_tools.html#install_avr_binutils">avr-binutils</a>, <a class="el" href="install_tools.html#install_avr_gcc">avr-gcc</a> and make sure your <a class="el" href="install_tools.html#path">path is set</a> properly before configuring and building AVR-LibC.</dd></dl>
289289
<p>If you have obtained the latest AVR-LibC from <a class="el" href="install_tools.html#using_git">git</a>, you will have to run the <code>./bootstrap</code> script before using either of the build methods described below.</p>
290290
<p>To build and install AVR-LibC:</p>
291291
<pre class="fragment">$ # in ./source

docs/avr-libc-user-manual/FAQ.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1267,7 +1267,7 @@ <h1><a class="anchor" id="faq_toolchain_version"></a>
12671267
<td>AVR-LibC </td><td><code>echo "#include &lt;avr/version.h&gt;" | avr-gcc -xc - -E -dM | grep AVR_LIBC_VERSION_STRING</code> </td></tr>
12681268
</table>
12691269
<p>Linker<sup>1</sup> is the linker as called directly (<code>avr-ld</code>) whereas Linker<sup>2</sup> is the linker as called though the compiler driver <code>avr-gcc</code>. The latter is the usual way to invoke the linker. When these two versions are not the same, then the resulting toolchain may have inconsistencies.</p>
1270-
<p>When you have more then one toolchain installed, then make sure you are calling the command from the intended toolchain, e.g. by specifying the absolute path to the tool.</p>
1270+
<p>When you have more than one toolchain installed, then make sure you are calling the command from the intended toolchain, e.g. by specifying the absolute path to the tool.</p>
12711271
<p>Also notice that software may come with vendor specific patches, so that the tool behaves differently than the stock version.</p>
12721272
<p><small>Back to <a class="el" href="FAQ.html#faq_index">FAQ Index</a>.</small></p>
12731273
<h1><a class="anchor" id="faq_toolchain_sources"></a>

docs/avr-libc-user-manual/install_tools.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,7 @@ <h2><a class="anchor" id="install_avr_gcc"></a>
285285
<h2><a class="anchor" id="install_avr_libc"></a>
286286
AVR-LibC</h2>
287287
<p><a id="a9_installation:2C:20avr-libc" name="a9_installation:2C:20avr-libc"></a></p>
288-
<dl class="section warning"><dt>Warning</dt><dd>You <b>must</b> install <a class="el" href="install_tools.html#install_avr_binutils">avr-binutils</a>, <a class="el" href="install_tools.html#install_avr_gcc">avr-gcc</a> and make sure your <a class="el" href="install_tools.html#path">path is set</a> properly before configuring abd building AVR-LibC.</dd></dl>
288+
<dl class="section warning"><dt>Warning</dt><dd>You <b>must</b> install <a class="el" href="install_tools.html#install_avr_binutils">avr-binutils</a>, <a class="el" href="install_tools.html#install_avr_gcc">avr-gcc</a> and make sure your <a class="el" href="install_tools.html#path">path is set</a> properly before configuring and building AVR-LibC.</dd></dl>
289289
<p>If you have obtained the latest AVR-LibC from <a class="el" href="install_tools.html#using_git">git</a>, you will have to run the <code>./bootstrap</code> script before using either of the build methods described below.</p>
290290
<p>To build and install AVR-LibC:</p>
291291
<pre class="fragment">$ # in ./source

0 commit comments

Comments
 (0)