Attached is a typo patch [EMAIL PROTECTED]:~/debiandoc/ddp$ cvs diff -u > ddp.typos.diff
Spell-checking was done using en_US. Helmut Wollmersdorfer
? ddp.typos.diff Index: manuals.sgml/ddp-policy/en/articles.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/articles.sgml,v retrieving revision 1.2 diff -u -r1.2 articles.sgml --- manuals.sgml/ddp-policy/en/articles.sgml 28 Oct 2002 10:22:49 -0000 1.2 +++ manuals.sgml/ddp-policy/en/articles.sgml 20 Jun 2005 13:16:51 -0000 @@ -5,15 +5,15 @@ developers (or other people that want to contribute it to the Debian Documentation Project). Articles are not in-depth documents (manuals are). However, it is not uncommon for Debian developers to write articles -for magazine (online or paper-based) or to analyse a given aspect in Debian +for magazine (on-line or paper-based) or to analyze a given aspect in Debian (usually for conferences).</p> <p>Articles can, unlike manuals, get out of date and not be updated. That is not an issue since the knowledge they hold might be useful even if in such state. The intention include them in the DDP and make them available through CVS is so that it is possible to publish them on the WWW -(like other DDP documentation) and to povide a repository -of knowledge for later use. After all, articles, even if outdate, can be +(like other DDP documentation) and to provide a repository +of knowledge for later use. After all, articles, even if outdated, can be used to write new articles or might reflect an important epoch of the Debian project. </p> @@ -38,7 +38,7 @@ is still preferred, but, due to its limitation (described previously) sometimes authors might prefer other formats (such as Docbook-xml or LaTeX). These can be used for articles. -However note that if the author users a format which cannot be +However note that if the author uses a format which cannot be easily compiled on the documentation server for publishing, the DDP might not dedicate effort to have the documents published. Formats that can be readily compiled from source format into the publishing @@ -50,7 +50,7 @@ debiandoc-sgml). Some articles might be found, however in linuxdoc-sgml. These articles need to be translated to debiandoc-sgml <strong>before</strong> publishing is made. This is because -there are no fundamental differences between both format to justify +there are no fundamental differences between both formats to justify using linuxdoc-sgml. </p> </sect> Index: manuals.sgml/ddp-policy/en/common.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/common.sgml,v retrieving revision 1.12 diff -u -r1.12 common.sgml --- manuals.sgml/ddp-policy/en/common.sgml 9 Sep 2003 14:10:06 -0000 1.12 +++ manuals.sgml/ddp-policy/en/common.sgml 20 Jun 2005 13:16:51 -0000 @@ -8,17 +8,17 @@ much out-of-date). Also, optionally there might be many <em>Translators</em>. </p> <p>Interested translators are encouraged to contact first the author of a -document and then, if it exists, the localisation team for the language +document and then, if it exists, the localization team for the language the translator wants to translate too. This helps authors keep track of who is translating the document (in case somebody else volunteers) -and also prevents for duplicate effor (maybe somebody in the localisation +and also prevents for duplicate effort (maybe somebody in the localization team is currently translating it and has not contacted the main author). </p> <sect>License <p>All documention of the Debian Documentation Project (DDP) must be -released under a free license (free to use, modify and distribute) +released under a free license (free to use, modify and distribute). <footnote> Note that there is currently disagreement regarding wether or not documentation can be asked to be <em>free in the DFSG sense</em>. @@ -31,7 +31,7 @@ </footnote> for the Debian project to use. This is true not only for documentation provided by the DDP authors themselves but for documentation provided in the Debian -operating system by packages (including FAQs, manpages, help pages, etc..)</P> +operating system by packages (including FAQs, manpages, help pages, etc.).</P> <P>The recommended license for any (new) document in Debian is the Index: manuals.sgml/ddp-policy/en/feedback.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/feedback.sgml,v retrieving revision 1.5 diff -u -r1.5 feedback.sgml --- manuals.sgml/ddp-policy/en/feedback.sgml 23 Jan 2003 19:54:19 -0000 1.5 +++ manuals.sgml/ddp-policy/en/feedback.sgml 20 Jun 2005 13:16:51 -0000 @@ -13,12 +13,12 @@ <p>Please avoid sending bug reports (or requests) to the document maintainers directly. Maintainers are already subscribed to the BTS and sending them the bugs directly only increases that chances that -the mail might get lost (forgotten, deleted accidentaly) if the +the mail might get lost (forgotten, deleted accidentally) if the maintainer is managing a big mailbox <footnote> Which will unfortunately include usually also a lot of spam due to his name being published in many -places and making it a target for mail harversters :-( +places and making it a target for mail harvesters :-( </footnote> Also, your requests and suggestions might be lost if the document switches maintainers (due to inactivity, lack @@ -28,7 +28,7 @@ to the debian-doc mailing list unless you want to discuss some issue before submitting a bug report. After all, the Bug Tracking system is better suited to track bugs (it was designed for that). -ou can, using the BTS, receive a report when the bug is fixed and +You can, using the BTS, receive a report when the bug is fixed and a new document version is released.</p> <p>Documentation maintainers and active authors <em>should be</em> subscribed @@ -87,7 +87,7 @@ Document maintainers can also use the WNPP to submit information on documentation under development or that it's going to be orphaned.</p> -<p>The following tags of the WNPP are appropiate for this task: +<p>The following tags of the WNPP are appropriate for this task: <list> Index: manuals.sgml/ddp-policy/en/manpages.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/manpages.sgml,v retrieving revision 1.2 diff -u -r1.2 manpages.sgml --- manuals.sgml/ddp-policy/en/manpages.sgml 28 Oct 2002 10:22:49 -0000 1.2 +++ manuals.sgml/ddp-policy/en/manpages.sgml 20 Jun 2005 13:16:51 -0000 @@ -1,16 +1,16 @@ <chapt id="manpages">Manpages -<p><em>FIXME:</em> Explain why manpages are part of the DDP</p> +<p><em>FIXME:</em> Explain why manpages are part of the DDP</p> <p><em>FIXME:</em> Describe the use of the DDP CVS for manpages and their translations.</p> <p><em>FIXME:</em> Is there a way to detect manpages changes such as there is for the wml web pages?</p> -<p><em>FIXME:</em> are we going to provide a framework for translating +<p><em>FIXME:</em> Are we going to provide a framework for translating and updating non-Debian manpages?</p> -<p><em>FIXME:</em> Are we going to provide localised manpages +<p><em>FIXME:</em> Are we going to provide localized manpages together with programs or in a single package (i.e. manpages-es is useful?). How is coordination going to be done with other projects?</p> Index: manuals.sgml/ddp-policy/en/manuals.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/manuals.sgml,v retrieving revision 1.17 diff -u -r1.17 manuals.sgml --- manuals.sgml/ddp-policy/en/manuals.sgml 23 Jan 2003 08:11:03 -0000 1.17 +++ manuals.sgml/ddp-policy/en/manuals.sgml 20 Jun 2005 13:16:51 -0000 @@ -23,7 +23,7 @@ <item>Debian GNU/Linux FAQ <item>Debian Installation Manual (*) <item>Debian Release Notes (*) -<item>Debian Rererence +<item>Debian Reference <item>APT HOWTO <item>dselect Documentation for Beginners (*) <item>User's Guide @@ -143,7 +143,7 @@ <p>When to you use which format? Docbook needs not be the chosen always as the only documentation format. <em>Debiandoc-sgml</em> -is prefered for most manuals since: +is preferred for most manuals since: <list> <item>it's simpler (46 elements versus 300+) and thus easier to use. <item>output is (currently) better for some purposes, it is also @@ -159,7 +159,7 @@ (see <url id="http://bugs.debian.org/140684"; name="Bug #140684">) or tables (see <url id="http://bugs.debian.org/141727"; name="Bug #141727">) -<item>it is not internationalised completely +<item>it is not internationalized completely (see <url id="http://bugs.debian.org/31266"; name="Bug #31266">) <item>there are some layout issues when generating some formats. </list> @@ -171,7 +171,7 @@ LaTeX, HTML, texinfo, groff and several other minor formats. Even if some of these were used at some point by DDP documents their use is not supported. <em>All</em> DDP manuals must -be provided eitheri in <em>debiandoc-sgml</em> or +be provided either in <em>debiandoc-sgml</em> or <em>docbook</em> (sgml or xml) format (this rule does not necessarily apply to other documentation that is handled by the DDP)</p> @@ -207,7 +207,7 @@ similar to the one you want to work in. <item>ask for <url id="http://cvs.debian.org/?cvsroot=debian-doc"; name="CVS access"> to the DDP area -<footnote>If you are a Debian developer you will acess it through +<footnote>If you are a Debian developer you will access it through the <em>:ext:ssh</em> method, otherwise a <em>pserver</em> account will be created for you</footnote> <item>(once the document compiles properly) ask for it to be published under @@ -217,11 +217,11 @@ <item>create new packages (preferably using <package>cvs-buildpackage</package>) and submit it to the debian upload queue. <item>ask for translations at the -<url id="http://lists.debian.org/debian-i18n/"; name="internationalisation mailing list"> +<url id="http://lists.debian.org/debian-i18n/"; name="internationalization mailing list"> (and keep track of those that volunteered as translators) <item>attend to bugs either sent directly to your mail address (if published in the document's author field), through the BTS (if packages are available) -or through the appropiate mailing lists (you should subscribe to +or through the appropriate mailing lists (you should subscribe to the <url id="http://lists.debian.org/debian-doc"; name="DDP mailing list">,. </list> @@ -397,7 +397,7 @@ include all the formats for which the document compiles. As for translations, they should be provided as separate packages if the binary (with all the available translations) exceeds -five megabytes in size (see below for the appropiate naming +five megabytes in size (see below for the appropriate naming for these binary packages).</p> <p>Depending on wether or not translations are provided in different binary packages the package naming will be: @@ -567,7 +567,7 @@ to DDP web page with a script un-compressing files. </p> -<P><em>FIXME:</em> How is thist install automated? Explain the +<P><em>FIXME:</em> How is this install automated? Explain the process. We might need ftp-masters to allow access without an upload. @@ -671,10 +671,10 @@ documentation to be placed in the CD-ROMs so that users can access this documentation without needing to install Debian at all (even if later on they could install the same documentation just by -installing the appropiate packages). +installing the appropriate packages). <p>Not all DDP documents are placed on the CD-ROMs since once of the -issues on these ISO images is how to distibute the available size +issues on these ISO images is how to distribute the available size so that all the necessary software is available in the first CD-ROMs (so that users do not need to download all the CD-ROMs in order to have a functioning Debian installation). Thus, only important @@ -692,7 +692,7 @@ <p>Note: Providing a sensible location of documentation in the packages as well as translations makes it possible to have -<package>debian-cd</package> make localised CD-ROMs that not only +<package>debian-cd</package> make localized CD-ROMs that not only include the installation in a given language but provide the documentation in that language too! @@ -708,7 +708,7 @@ Currently, many generated HTML files still create index.html or index.&langname;.html as the starting page but these are discouraged practices since they hide other files. (<em>FIXME:</em> This is -debatable. It is implimented for the Debian Reference but makefile +debatable. It is implemented for the Debian Reference but makefile is a mess.) </p> </sect1> Index: manuals.sgml/ddp-policy/en/preface.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/preface.sgml,v retrieving revision 1.6 diff -u -r1.6 preface.sgml --- manuals.sgml/ddp-policy/en/preface.sgml 23 May 2003 07:34:33 -0000 1.6 +++ manuals.sgml/ddp-policy/en/preface.sgml 20 Jun 2005 13:16:52 -0000 @@ -22,7 +22,7 @@ associated mirrors) and even CD images of Debian distributions. Even if packages are involved (since it's the mechanism for distributing any piece of data in a Debian distribution) it is not a tutorial on how -to build packages and it will not go into lenghts describing how the +to build packages and it will not go into lengths describing how the packaging system works. </p> @@ -30,7 +30,7 @@ project. Some of the documentation might be handled by people who are not directly in the DDP, but who maintain a set of documentation. To make it short the DDP might be considered a reduced version of the -famouse phrase cutting it into: <em>all your documents are belong to us</em>. +famous phrase cutting it into: <em>all your documents are belong to us</em>. That is, any and all document that is either prepared or supported by the Debian project (included in the distribution, published in the web site) is managed through the DDP. This includes: Index: manuals.sgml/ddp-policy/en/presentations.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/ddp-policy/en/presentations.sgml,v retrieving revision 1.3 diff -u -r1.3 presentations.sgml --- manuals.sgml/ddp-policy/en/presentations.sgml 28 Oct 2002 10:32:47 -0000 1.3 +++ manuals.sgml/ddp-policy/en/presentations.sgml 20 Jun 2005 13:16:52 -0000 @@ -3,7 +3,7 @@ <p><em>FIXME:</em> More content needed here. Why slides? What use?</p> <p><em>FIXME:</em> Proposed a layout on presentations based on topics. -Describe prefered formats for presentations (Magic Point? LaTeX with +Describe preferred formats for presentations (Magic Point? LaTeX with Prosper?)</p> <p><em>FIXME:</em> Encourage Debian developers to submit presentations
