mirror of
https://github.com/gnustep/libs-base.git
synced 2025-04-25 01:31:08 +00:00
A few spelling fixes
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@6180 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Richard Frith-MacDonald
parent
6b575b7a2b
commit
29e35f3823
2 changed files with 15 additions and 15 deletions
|
|
@ -61,7 +61,7 @@
|
|||
using in Objective-C method names is used in info markup.
|
||||
</item>
|
||||
<item>
|
||||
LinuxDoc, while bening a nice basic system, seesm to be
|
||||
LinuxDoc, while being a nice basic system, seems to be
|
||||
in the process of being replaced by DocBook.
|
||||
</item>
|
||||
</list>
|
||||
|
|
@ -76,7 +76,7 @@
|
|||
Provide optimal support for GNUstep documentation.
|
||||
</item>
|
||||
<item>
|
||||
Minimise the amount of work needed for development of
|
||||
Minimize the amount of work needed for development of
|
||||
software tools.
|
||||
</item>
|
||||
<item>
|
||||
|
|
@ -101,7 +101,7 @@
|
|||
The gsdoc DTD defines an XML language - that is, a markup language
|
||||
that conforms to a specific subset of SGML features defined as XML.
|
||||
The advantage of XML is that it provides most of the useful features
|
||||
of SGML while being much more light-weight (easy to use) beacause
|
||||
of SGML while being much more light-weight (easy to use) because
|
||||
you can forget about the rest of SGML.
|
||||
As XML looks set to become increasingly popular, we can hope that
|
||||
documentation written with an XML language will be easily imported
|
||||
|
|
@ -142,8 +142,8 @@
|
|||
<term>base</term>
|
||||
<desc>
|
||||
This is optional, but recommended - it specifies the base name
|
||||
for the document. When the document is tranlated to another
|
||||
format, the outut file name should be based on this - eg.
|
||||
for the document. When the document is translated to another
|
||||
format, the output file name should be based on this - eg.
|
||||
if the base name of a document is <em>foo</em> then an html
|
||||
output for this file would be <em>foo.html</em>.
|
||||
</desc>
|
||||
|
|
@ -202,7 +202,7 @@
|
|||
</head>
|
||||
</example>
|
||||
<p>
|
||||
The above axample shows all the elements possible in a document head -
|
||||
The above example shows all the elements possible in a document head -
|
||||
</p>
|
||||
<deflist>
|
||||
<term><label id="title">title</label></term>
|
||||
|
|
@ -247,7 +247,7 @@
|
|||
consists of an optional front part (for contents pages, overview
|
||||
etc), a sequence of any number of chapters, and an optional back
|
||||
part (for indexes, appendices etc). Normally, each of these three
|
||||
parts of the document woudl be expected to have their own separate
|
||||
parts of the document would be expected to have their own separate
|
||||
page numbering schemes.
|
||||
</p>
|
||||
</section>
|
||||
|
|
@ -272,7 +272,7 @@
|
|||
<back>
|
||||
<!--
|
||||
<chapter>
|
||||
<heading>Afterword</heading>
|
||||
<heading>Afterward</heading>
|
||||
</chapter>
|
||||
-->
|
||||
<index type="label"/>
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@
|
|||
using in Objective-C method names is used in info markup.
|
||||
|
||||
<li>
|
||||
LinuxDoc, while bening a nice basic system, seesm to be
|
||||
LinuxDoc, while being a nice basic system, seems to be
|
||||
in the process of being replaced by DocBook.
|
||||
|
||||
</ul>
|
||||
|
|
@ -86,7 +86,7 @@
|
|||
Provide optimal support for GNUstep documentation.
|
||||
|
||||
<li>
|
||||
Minimise the amount of work needed for development of
|
||||
Minimize the amount of work needed for development of
|
||||
software tools.
|
||||
|
||||
<li>
|
||||
|
|
@ -108,7 +108,7 @@
|
|||
The gsdoc DTD defines an XML language - that is, a markup language
|
||||
that conforms to a specific subset of SGML features defined as XML.
|
||||
The advantage of XML is that it provides most of the useful features
|
||||
of SGML while being much more light-weight (easy to use) beacause
|
||||
of SGML while being much more light-weight (easy to use) because
|
||||
you can forget about the rest of SGML.
|
||||
As XML looks set to become increasingly popular, we can hope that
|
||||
documentation written with an XML language will be easily imported
|
||||
|
|
@ -153,8 +153,8 @@
|
|||
<dt>base
|
||||
<dd>
|
||||
This is optional, but recommended - it specifies the base name
|
||||
for the document. When the document is tranlated to another
|
||||
format, the outut file name should be based on this - eg.
|
||||
for the document. When the document is translated to another
|
||||
format, the output file name should be based on this - eg.
|
||||
if the base name of a document is <em>foo</em> then an html
|
||||
output for this file would be <em>foo.html</em>.
|
||||
<em>foo</em> then an html
|
||||
|
|
@ -222,7 +222,7 @@
|
|||
</pre>
|
||||
<p>
|
||||
|
||||
The above axample shows all the elements possible in a document head -
|
||||
The above example shows all the elements possible in a document head -
|
||||
</p>
|
||||
<dl>
|
||||
<dt><a name="title">title</a>
|
||||
|
|
@ -275,7 +275,7 @@
|
|||
consists of an optional front part (for contents pages, overview
|
||||
etc), a sequence of any number of chapters, and an optional back
|
||||
part (for indexes, appendices etc). Normally, each of these three
|
||||
parts of the document woudl be expected to have their own separate
|
||||
parts of the document would be expected to have their own separate
|
||||
page numbering schemes.
|
||||
</p>
|
||||
<h2><a name="cont-3">The gsdoc conversion tool</a></h2>
|
||||
|
|
|
|||
Loading…
Reference in a new issue