Fixing docbook markup errors.

This commit is contained in:
emmajane 2003-12-14 20:58:51 +00:00
parent 41cc6c85bf
commit 09bc738c18
3 changed files with 4 additions and 4 deletions

View File

@ -16,8 +16,6 @@
Things that need fixing should be marked as such with either "TODO"
or "FIXME".
Multiple file searching can be done with a variation of this:
find . -name "*xml" -exec grep -n "TODO" {} \; -print
-->
<!-- Chapter One: About this guide -->
@ -379,7 +377,6 @@ what's on the LDP web site as I'm currently *gasp* offline. -->
&references;
<!-- Appendix: Sample Templates -->
<!-- TODO requires markup -->
&templates;
<!-- Appendix: Editors, Validation and System Setup -->

View File

@ -92,7 +92,8 @@
<para> <!--please check these changes for correctness!-->
At this point, if you wrote your document in another format, an LDP volunteer will translate
it into some form of markup language. The markup language format that is currently preferred is Docbook XML, see <xref likend="ag-markup" />. Your reviewer will send the finished document to you. In this guide, we assume the return format is Docbook XML. All subsequent revisions of your document to the LDP
it into some form of markup language. The markup language format
that is currently preferred is Docbook XML, see <xref linkend="ag-markup" />. Your reviewer will send the finished document to you. In this guide, we assume the return format is Docbook XML. All subsequent revisions of your document to the LDP
must be in the same format. If you have markup questions, you may ask the
volunteer who assisted you, or ask the LDP DocBook list. For
more information about the LDP DocBook list please read

View File

@ -89,6 +89,8 @@
<para>
If the HOWTO already in place is insufficient or needs updating,
contact the author and offer to help. See also <xref linkend="unmaintained" /> for taking over old or unmaintained documents.</para>
<para>
Most authors appreciate any help offered. Additionally, sending comments and remarks to the author is usually regarded both as a reassurance and an reward: to the author, feedback is the ultimate proof that writing the documentation was not a pointless effort.</para>
</listitem>