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

Whitespace-only fixes. Translators, please ignore.

Browse source
This commit is contained in:
Warren Block 2013-06-20 16:46:55 +00:00
parent 0bd302297a
commit da1e22a104
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41971
1 changed files with 113 additions and 110 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml
View file

@ -108,8 +108,8 @@
<sect1 id="writing-style-guidelines">
<title>Guidelines</title>
<para>To promote consistency between the myriad authors of
the FreeBSD documentation, some guidelines have been drawn up for
<para>To promote consistency between the myriad authors of the
FreeBSD documentation, some guidelines have been drawn up for
authors to follow.</para>
<variablelist>
@ -124,11 +124,11 @@
<quote>rationalise</quote>, and so on.</para>
<note>
<para>The use of British English may be accepted in the case
of a contributed article, however the spelling must be
consistent within the whole document. The other documents
such as books, web site, manual pages, etc. will have to
use American English.</para>
<para>The use of British English may be accepted in the
case of a contributed article, however the spelling must
be consistent within the whole document. The other
documents such as books, web site, manual pages, etc.
will have to use American English.</para>
</note>
</listitem>
</varlistentry>
@ -137,12 +137,13 @@
<term>Do not use contractions</term>
<listitem>
<para>Do not use contractions. Always spell the phrase out in
full. <quote>Don't use contractions</quote> would be
<para>Do not use contractions. Always spell the phrase out
in full. <quote>Don't use contractions</quote> would be
wrong.</para>
<para>Avoiding contractions makes for a more formal tone, is
more precise, and is slightly easier for translators.</para>
more precise, and is slightly easier for
translators.</para>
</listitem>
</varlistentry>
@ -196,8 +197,8 @@
sources.</para>
</informalexample>
<para>These two examples show this for filenames. The second
example is preferred.</para>
<para>These two examples show this for filenames. The
second example is preferred.</para>
<informalexample>
<para>&hellip; in the filename
@ -209,8 +210,8 @@
<filename>/etc/rc.local</filename>&hellip;</para>
</informalexample>
<para>These two examples show this for manual references. The
second example is preferred (the second example uses
<para>These two examples show this for manual references.
The second example is preferred (the second example uses
<sgmltag>citerefentry</sgmltag>).</para>
<informalexample>
@ -223,6 +224,7 @@
</informalexample>
</listitem>
</varlistentry>
<varlistentry>
<term>Two spaces at the end of sentences</term>
@ -233,10 +235,11 @@
<para>While it may be argued that a capital letter following
a period denotes a new sentence, this is not the case,
especially in name usage. <quote>Jordan K. Hubbard</quote>
is a good example; it has a capital <literal>H</literal>
following a period and a space, and there certainly is not a
new sentence there.</para>
especially in name usage.
<quote>Jordan K. Hubbard</quote> is a good example; it has
a capital <literal>H</literal> following a period and a
space, and there certainly is not a new sentence
there.</para>
</listitem>
</varlistentry>
</variablelist>