os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix a variety of English style nits and other issues found with igor.

Browse source 
Reviewed by:	gabor
Approved by:	wblock
This commit is contained in:
Eitan Adler 2012-02-13 18:12:56 +00:00
parent 9c17dd697d
commit 31e8611f47
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=38451
2 changed files with 10 additions and 11 deletions
en_US.ISO8859-1/books/handbook
cutting-edge
chapter.sgml
desktop
chapter.sgml

16
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -766,7 +766,7 @@ Fetching 133 new ports or files... done.</screen>
<listitem>
<para>Some of the build options that are supported by the
build system of the documentation, i.e. the options that
build system of the documentation, i.e., the options that
build only some of the different language translations of
the documentation or the options that select a specific
output format.</para>
@ -886,7 +886,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
<listitem>
<para>The list of languages and encodings to build and
install, e.g. <literal>en_US.ISO8859-1</literal> for the
install, e.g., <literal>en_US.ISO8859-1</literal> for the
English documentation only.</para>
</listitem>
</varlistentry>
@ -1133,7 +1133,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
because we are installing a port, and ports are
usually installed under the <filename
class="directory">/usr/local</filename> directory.
This can overriden, by adding the
This can be overridden by adding the
<makevar>PREFIX</makevar> variable.</para>
</note>
</listitem>
@ -1181,7 +1181,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
from the corresponding port's name:
<literal><replaceable>lang</replaceable>-freebsd-doc</literal>.
Here <replaceable>lang</replaceable> is the short format of
the language code, i.e. <literal>hu</literal> for
the language code, i.e., <literal>hu</literal> for
Hungarian, or <literal>zh_cn</literal> for Simplified
Chinese.</para>
</note>
@ -1339,7 +1339,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
<listitem>
<para>Those who merely wish to keep an eye on things, or
to use the current sources for reference purposes
(e.g. for <emphasis>reading</emphasis>, not running).
(e.g., for <emphasis>reading</emphasis>, not running).
These people also make the occasional comment or
contribute code.</para>
</listitem>
@ -1982,7 +1982,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
</orderedlist>
<para>Note that if you're upgrading from one release of the same &os;
branch to a more recent release of the same branch, i.e. from 7.0 to
branch to a more recent release of the same branch, i.e., from 7.0 to
7.1, then this procedure may not be absolutely necessary, since
you're unlikely to run into serious mismatches between compiler,
kernel, userland and configuration files. The older approach
@ -1994,7 +1994,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
follow this procedure should expect some problems.</para>
<para>It is also worth noting that many upgrades
(i.e.&nbsp;4.<replaceable>X</replaceable> to 5.0) may require
(i.e.,&nbsp;4.<replaceable>X</replaceable> to 5.0) may require
specific additional steps (renaming or deleting specific files prior
to installworld, for instance). Read
the <filename>/usr/src/UPDATING</filename> file carefully,
@ -2026,7 +2026,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
<para>After <maketarget>installkernel</maketarget> finishes
successfully, you should boot in single user mode
(i.e.&nbsp;using <command>boot -s</command> from the loader
(i.e.,&nbsp;using <command>boot -s</command> from the loader
prompt). Then run:</para>
<screen>&prompt.root; <userinput>mount -u /</userinput>

5
en_US.ISO8859-1/books/handbook/desktop/chapter.sgml
View file

@ -816,12 +816,11 @@
<screen>&prompt.root; <userinput>pkg_add -r libreoffice</userinput></screen>
<note>
<para>When running a -RELEASE version of &os;, this should work.
<para>When running a -RELEASE version of &os;, this should work.</para>
</note>
<para>Once the package is installed, you need to type the following
command to run <application>LibreOffice</application>:
</para>
command to run <application>LibreOffice</application>:</para>
<screen>&prompt.user; <userinput>libreoffice</userinput></screen>