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

- Remove an useless </dd> in one example.

Browse source 
- Use of .cshrc as "startup" file for csh(1) and tcsh(1) instead of
  .login
- Some British English -> American English
  organise(d) -> organize(d)
  organisation -> organization
  generalised -> generalized

PR:		docs/54456
Submitted by:	Ken Smith <kensmith@cse.Buffalo.EDU>
This commit is contained in:
Marc Fonvieille 2003-07-20 20:55:18 +00:00
parent 3115460705
commit 803f927625
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17625
6 changed files with 19 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml
View file

@ -34,7 +34,7 @@
<title>The Documentation Build Process</title>
<para>This chapter's main purpose is to clearly explain <emphasis>how
the documentation build process is organised</emphasis>, and
the documentation build process is organized</emphasis>, and
<emphasis>how to affect modifications to this process</emphasis>.
</para>

2
en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml
View file

@ -39,7 +39,7 @@
is produced. Your contributions are very valuable.</para>
<para>This document's main purpose is to clearly explain <emphasis>how
the FDP is organised</emphasis>, <emphasis>how to write and submit
the FDP is organized</emphasis>, <emphasis>how to write and submit
documentation to the FDP</emphasis>, and <emphasis>how to
effectively use the tools available to you when writing
documentation</emphasis>.</para>

6
en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml
View file

@ -292,7 +292,7 @@
<programlisting><![ CDATA [<dl>
<dt>Term 1</dt>
<dd><p>Paragraph 1 of definition 1.</p></dd>
<dd><p>Paragraph 1 of definition 1.</p>
<p>Paragraph 2 of definition 1.</p></dd>
@ -729,7 +729,7 @@
ways. In the FreeBSD Documentation Project we are using two primary
types of DocBook document: the book and the article.</para>
<para>A book is organised into <sgmltag>chapter</sgmltag>s. This is a
<para>A book is organized into <sgmltag>chapter</sgmltag>s. This is a
mandatory requirement. There may be <sgmltag>part</sgmltag>s between
the book and the chapter to provide another layer of organisation.
The Handbook is arranged in this way.</para>
@ -742,7 +742,7 @@
<para>Chapters and sections contain the remainder of the content.</para>
<para>An article is simpler than a book, and does not use chapters.
Instead, the content of an article is organised into one or more
Instead, the content of an article is organized into one or more
sections, using the same <sgmltag>sect1</sgmltag> (and
<sgmltag>sect2</sgmltag> and so on) elements that are used in
books.</para>

8
en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml
View file

@ -119,7 +119,7 @@
these other markup languages. A <emphasis>meta markup
language</emphasis>.</para>
<para>This is exactly what the Standard Generalised Markup Language (SGML)
<para>This is exactly what the Standard Generalized Markup Language (SGML)
is. Many markup languages have been written in SGML, including the two
most used by the FDP, HTML and DocBook.</para>
@ -369,7 +369,7 @@ export SGML_CATALOG_FILES</programlisting>
</example>
<example>
<title><filename>.login</filename>, for &man.csh.1; and
<title><filename>.cshrc</filename>, for &man.csh.1; and
&man.tcsh.1; users</title>
<programlisting>setenv SGML_ROOT /usr/local/share/sgml
@ -442,7 +442,7 @@ setenv SGML_CATALOG_FILES /usr/doc/en_US.ISO8859-1/share/sgml/catalog:$SGML_CATA
nsgmls:example.sgml:5:4:E: character data is not allowed here
nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>The error output from &man.nsgmls.1; is organised into
<para>The error output from &man.nsgmls.1; is organized into
colon-separated groups, or columns.</para>
<informaltable frame="none">
@ -1104,7 +1104,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<sect2 id="sgml-primer-include-using-gen-entities">
<title>Using general entities to include files</title>
<para>Suppose you have some content for an SGML book organised into
<para>Suppose you have some content for an SGML book organized into
files, one file per chapter, called
<filename>chapter1.sgml</filename>,
<filename>chapter2.sgml</filename>, and so forth, with a

18
en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
View file

@ -33,8 +33,8 @@
<chapter id="structure">
<title>Structuring documents under <filename>doc/</filename></title>
<para>The <filename>doc/</filename> tree is organised in a particular
fashion, and the documents that are part of the FDP are in turn organised
<para>The <filename>doc/</filename> tree is organized in a particular
fashion, and the documents that are part of the FDP are in turn organized
in a particular fashion. The aim is to make it simple to add new
documentation into the tree and:</para>
@ -160,7 +160,7 @@
<para>The Handbook is written to comply with the FreeBSD DocBook
extended DTD.</para>
<para>The Handbook is organised as a DocBook <sgmltag>book</sgmltag>.
<para>The Handbook is organized as a DocBook <sgmltag>book</sgmltag>.
It is then divided into <sgmltag>part</sgmltag>s, each of which may
contain several <sgmltag>chapter</sgmltag>s.
<sgmltag>chapter</sgmltag>s are further subdivided into sections
@ -168,15 +168,15 @@
<sgmltag>sect3</sgmltag>) and so on.</para>
<sect3>
<title>Physical organisation</title>
<title>Physical organization</title>
<para>There are a number of files and directories within the
<filename>handbook</filename> directory.</para>
<note>
<para>The Handbook's organisation may change over time, and this
document may lag in detailing the organisational changes. If you
have any questions about how the Handbook is organised, please
<para>The Handbook's organization may change over time, and this
document may lag in detailing the organizational changes. If you
have any questions about how the Handbook is organized, please
contact the &a.doc;.</para>
</note>
@ -258,8 +258,8 @@
<important>
<para>Chapters and/or directories should not be named in a fashion
that reflects their ordering within the Handbook. This ordering
might change as the content within the Handbook is reorganised;
this sort of reorganisation should not (generally) include the
might change as the content within the Handbook is reorganized;
this sort of reorganization should not (generally) include the
need to rename files (unless entire chapters are being promoted
or demoted within the hierarchy).</para>
</important>

2
en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml
View file

@ -248,7 +248,7 @@
</question>
<answer>
<para>First, make sure your translation is organised properly. This
<para>First, make sure your translation is organized properly. This
means that it should drop into the existing documentation tree and
build straight away.</para>