docs: fix typos under defunct/ via codespell

LDP/defunct/LDP-Admin-Guide/docmanagement.txt

@@ -47,7 +47,7 @@ collection (and deleted from the CVS tree--copy will be archived in the
 Attic). A note should be added to the CVS tree, and public web site, which
 is plain HTML and states: 
 	- the title of the document that was removed
-	- why the document was removed (e.g. did not pass Techical Review)
+	- why the document was removed (e.g. did not pass Technical Review)
 	- where readers can go to find more information about this topic
 	- whether or not we are looking for a replacement document.
 

LDP/defunct/plone/requirements.txt

@@ -1,4 +1,4 @@
-Reqirements for a plone based documentation infrastructure for the LDP
+Requirements for a plone based documentation infrastructure for the LDP
 (in no particular order, "from the moon" level view).
 
 - Implement the following workflows:

LDP/defunct/scrollserver/CHANGELOG

@@ -47,7 +47,7 @@ Unreleased	0.6		ScrollKeeper access is locale aware
 				Caching temporarily disabled for testing.
 
 2001-09-10	0.1		Initial release. All existing ScrollKeeper
-				documents are loading and dislaying.
+				documents are loading and displaying.
 				Internal links work unless they use ghelp:foo
 				URIs. Caching is in place.
 

LDP/defunct/scrollserver/README

@@ -18,7 +18,7 @@ In later releases searching should be powerful but easy. It's a classic trade
 off, but I'm going to try. It will probably mean writing my own DocBook-aware
 search library. Right now there is no search functionality.
 
-There are more ambitious goals in the long term. Eventally, ScrollServers will
+There are more ambitious goals in the long term. Eventually, ScrollServers will
 be able to talk to one another, and to share information with each other. One
 ScrollServer will `publish' a document or five hundred, and another will
 `subscribe' to the `publication'. This is mainly for the benefit of the Linux

LDP/defunct/scrollserver/config.py

@@ -28,7 +28,7 @@ def parseConfig():
 		1. The command line (--option)
 		2. The config file specified in the $SCROLLSERVER_CONFIG
 		environment variable.
-		3. The config file specificed in the 'defaultConfigFile'
+		3. The config file specified in the 'defaultConfigFile'
 		variable.
 		4. A hardcoded default from 'configOptions'.
 	"""

LDP/defunct/scrollserver/stylesheets/common/common.xsl

@@ -1260,22 +1260,22 @@ is false.</para>
 </varlistentry>
 <varlistentry><term>label-wrapper</term>
 <listitem>
-<para>If <parameter>label-wrapper</parameter> is not the emtpy string,
+<para>If <parameter>label-wrapper</parameter> is not the empty string,
 it must be the name of an element. The element so named will be wrapped
 around labels on output.</para>
 </listitem>
 </varlistentry>
 <varlistentry><term>title-wrapper</term>
 <listitem>
-<para>If <parameter>title.wrapper</parameter> is not the emtpy string,
+<para>If <parameter>title.wrapper</parameter> is not the empty string,
 it must be the name of an element. The element so named will be wrapped
 around titles on output.</para>
 </listitem>
 </varlistentry>
 <varlistentry><term>label-wrapper-class</term>
 <listitem>
 <para>If a <parameter>label-wrapper</parameter> is provided and
-<parameter>label-wrapper-class</parameter> is not the emtpy string,
+<parameter>label-wrapper-class</parameter> is not the empty string,
 it be used as the value for a <sgmltag class="attribute">class</sgmltag>
 attribute on the <parameter>label-wrapper</parameter> element.</para>
 <para>This is a dirty hack because it only makes sense for the HTML
@@ -1287,7 +1287,7 @@ set as a parameter, but I can't.</para>
 <varlistentry><term>title-wrapper-class</term>
 <listitem>
 <para>If a <parameter>title-wrapper</parameter> is provided and
-<parameter>title-wrapper-class</parameter> is not the emtpy string,
+<parameter>title-wrapper-class</parameter> is not the empty string,
 it be used as the value for a <sgmltag class="attribute">class</sgmltag>
 attribute on the <parameter>title-wrapper</parameter> element.</para>
 <para>This is a dirty hack because it only makes sense for the HTML

LDP/defunct/scrollserver/stylesheets/docbook/README

@@ -80,7 +80,7 @@ advertising or otherwise to promote the sale, use or other
 dealings in this Software without prior written authorization
 from the individuals in question.
 
-Any stylesheet derived from this Software that is publically
+Any stylesheet derived from this Software that is publicly
 distributed will be identified with a different name and the
 version strings in any derived Software will be changed so that
 no possibility of confusion between the derived package and this

LDP/defunct/scrollserver/stylesheets/docbook/WhatsNew

@@ -78,7 +78,7 @@ Changes to xsl/htmlhelp/*
   | 
   | 2001-08-08  Jirka Kosek <kosek@users.sourceforge.net>
   | 
-  | 	* htmlhelp-common.xsl: Added new parameters for controling
+  | 	* htmlhelp-common.xsl: Added new parameters for controlling
   | 	  filenames of project and output files. New parameter
   | 	  htmlhelp.hhp.tail for specifying user content for project
   | 	  file.

LDP/defunct/scrollserver/stylesheets/docbook/doc/copyright.html

@@ -12,7 +12,7 @@
 credited with contribution to this software shall not be used in
 advertising or otherwise to promote the sale, use or other dealings in
 this Software without prior written authorization from the individuals
-in question.</p><p>Any stylesheet derived from this Software that is publically
+in question.</p><p>Any stylesheet derived from this Software that is publicly
 distributed will be identified with a different name and the version
 strings in any derived Software will be changed so that no possibility
 of confusion between the derived package and this Software will

LDP/defunct/scrollserver/stylesheets/docbook/doc/html/param.html

@@ -133,9 +133,9 @@ <h2 class="title" style="clear: both"><a name="d0e24"></a>Introduction
                   </dt>
                   <dt><a href="#param.using.chunker">using.chunker</a> - Will the output be chunked?
                   </dt>
-                  <dt><a href="#param.generate.component.toc">generate.component.toc</a> - Should TOCs be genereated in components (Chapters, Appendixes, etc.)?
+                  <dt><a href="#param.generate.component.toc">generate.component.toc</a> - Should TOCs be generated in components (Chapters, Appendixes, etc.)?
                   </dt>
-                  <dt><a href="#param.generate.division.toc">generate.division.toc</a> - Should TOCs be genereated in divisions (Books, Parts, etc.)?
+                  <dt><a href="#param.generate.division.toc">generate.division.toc</a> - Should TOCs be generated in divisions (Books, Parts, etc.)?
                   </dt>
                   <dt><a href="#param.link.mailto.url">link.mailto.url</a> - Mailto URL for the LINK REL=made HTML HEAD element
                   </dt>
@@ -798,7 +798,7 @@ <h1 class="title"><a name="param.using.chunker"></a>using.chunker
          <div class="refentry">
             <h1 class="title"><a name="param.generate.component.toc"></a>generate.component.toc
             </h1>
-            <div class="refnamediv"><a name="d0e554"></a><h2>Name</h2>generate.component.toc &#8212; Should TOCs be genereated in components (Chapters, Appendixes, etc.)?
+            <div class="refnamediv"><a name="d0e554"></a><h2>Name</h2>generate.component.toc &#8212; Should TOCs be generated in components (Chapters, Appendixes, etc.)?
             </div>
             <div class="refsynopsisdiv"><a name="d0e559"></a><h2>Synopsis</h2><pre class="synopsis">
 &lt;xsl:param name="generate.component.toc" select="1" doc:type="boolean"/&gt;</pre></div>
@@ -816,7 +816,7 @@ <h1 class="title"><a name="param.generate.component.toc"></a>generate.component.
          <div class="refentry">
             <h1 class="title"><a name="param.generate.division.toc"></a>generate.division.toc
             </h1>
-            <div class="refnamediv"><a name="d0e568"></a><h2>Name</h2>generate.division.toc &#8212; Should TOCs be genereated in divisions (Books, Parts, etc.)?
+            <div class="refnamediv"><a name="d0e568"></a><h2>Name</h2>generate.division.toc &#8212; Should TOCs be generated in divisions (Books, Parts, etc.)?
             </div>
             <div class="refsynopsisdiv"><a name="d0e573"></a><h2>Synopsis</h2><pre class="synopsis">
 &lt;xsl:param name="generate.division.toc" select="1" doc:type="boolean"/&gt;</pre></div>

LDP/defunct/scrollserver/stylesheets/docbook/doc/lib/lib.html

@@ -79,7 +79,7 @@ <h1 class="title"><a name="template.string.subst"></a>string.subst
 
 
                <p>The <tt>string.subst</tt> template replaces all
-                  occurances of <i><tt>target</tt></i> in <i><tt>string</tt></i>
+                  occurrences of <i><tt>target</tt></i> in <i><tt>string</tt></i>
                   with <i><tt>replacement</tt></i> and returns the result.
 
                </p>

LDP/defunct/scrollserver/stylesheets/docbook/doc/tools/profiling.html

@@ -81,7 +81,7 @@
 new standalone document now. Big advantage of this method is
 compatibility with all DocBook tools. Filtered document is normal
 DocBook document and it does not require any special processing. Of
-course, there is also one disadvantage – formating is now two
+course, there is also one disadvantage – formatting is now two
 stage process – first you must filter source document and in
 second step you could apply normal stylesheets on result of filtering.
 This may be little bit inconvenient for many users, but whole task can
@@ -94,7 +94,7 @@
 <tt>tools/profile.xsl</tt>.</p></div><div class="section"><a name="d0e85"></a><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="d0e85"></a>Usage</h2></div></div><p>If you want to generate Unix specific guide from our sample
 document (<a href="#ex:doc" title="Example 1. Sample DocBook document with profiling information">Example 1</a>) you can do it in the following
 way. (We assume, that command <b>saxon</b> is able to run
-XSLT processor on your machine. You can use your preffered XSLT
+XSLT processor on your machine. You can use your preferred XSLT
 processor instead.)</p><pre class="screen"><b>saxon</b> <tt>-o</tt> unixsample.xml sample.xml profile.xsl "os=unix"</pre><p>We are processing source document
 <tt>sample.xml</tt> with profiling stylesheet
 <tt>profile.xsl</tt>. Result of transformation is stored
@@ -139,7 +139,7 @@
 <tt>;</tt>.</p></dd></dl></div><p>Current implementation is able to handle multiple profiling
 targets in one attribute. In that case you must separate identifiers
 by semicolon:</p><pre class="programlisting">&lt;para os="unix;mac;win"&gt;...&lt;/para&gt;</pre><p>It is possible to use different separator than semicolon by
-setting <i><tt>sep</tt></i> parameter. There cann't be spaces
+setting <i><tt>sep</tt></i> parameter. There can't be spaces
 between separator and target names.</p><p>You can also perform profiling based on several profiling
 attributes in a single step as stylesheet can handle all parameters
 simultaneously. For example to get hypothetical guide for Windows

LDP/defunct/scrollserver/stylesheets/docbook/docsrc/copyright.xml

@@ -22,7 +22,7 @@ advertising or otherwise to promote the sale, use or other dealings in
 this Software without prior written authorization from the individuals
 in question.</para>
 
-<para>Any stylesheet derived from this Software that is publically
+<para>Any stylesheet derived from this Software that is publicly
 distributed will be identified with a different name and the version
 strings in any derived Software will be changed so that no possibility
 of confusion between the derived package and this Software will

LDP/defunct/scrollserver/stylesheets/docbook/docsrc/html/param.xml

@@ -554,7 +554,7 @@ in browsers.
 <refentry id="param.generate.component.toc">
 <refnamediv>
 <refname>generate.component.toc</refname>
-<refpurpose>Should TOCs be genereated in components (Chapters, Appendixes, etc.)?</refpurpose>
+<refpurpose>Should TOCs be generated in components (Chapters, Appendixes, etc.)?</refpurpose>
 </refnamediv>
 <refsynopsisdiv>
 <synopsis>
@@ -570,7 +570,7 @@ in browsers.
 <refentry id="param.generate.division.toc">
 <refnamediv>
 <refname>generate.division.toc</refname>
-<refpurpose>Should TOCs be genereated in divisions (Books, Parts, etc.)?</refpurpose>
+<refpurpose>Should TOCs be generated in divisions (Books, Parts, etc.)?</refpurpose>
 </refnamediv>
 <refsynopsisdiv>
 <synopsis>

LDP/defunct/scrollserver/stylesheets/docbook/docsrc/legalnotice.xml

@@ -18,7 +18,7 @@ advertising or otherwise to promote the sale, use or other dealings in
 this Software without prior written authorization from the individuals
 in question.</para>
 
-<para>Any stylesheet derived from this Software that is publically
+<para>Any stylesheet derived from this Software that is publicly
 distributed will be identified with a different name and the version
 strings in any derived Software will be changed so that no possibility
 of confusion between the derived package and this Software will

LDP/defunct/scrollserver/stylesheets/docbook/docsrc/lib/lib.xml

@@ -53,7 +53,7 @@ to be incomplete. Don't forget to read the source, too :-)</para>
 <refdescription>
 
 <para>The <function>string.subst</function> template replaces all
-occurances of <parameter>target</parameter> in <parameter>string</parameter>
+occurrences of <parameter>target</parameter> in <parameter>string</parameter>
 with <parameter>replacement</parameter> and returns the result.
 </para>
 

LDP/defunct/scrollserver/stylesheets/docbook/docsrc/tools/profiling.xml

@@ -124,7 +124,7 @@ DocBook tool or stylesheet you will get always correct output from the
 new standalone document now. Big advantage of this method is
 compatibility with all DocBook tools. Filtered document is normal
 DocBook document and it does not require any special processing. Of
-course, there is also one disadvantage – formating is now two
+course, there is also one disadvantage – formatting is now two
 stage process – first you must filter source document and in
 second step you could apply normal stylesheets on result of filtering.
 This may be little bit inconvenient for many users, but whole task can
@@ -154,7 +154,7 @@ distribution and can be found in file
 <para>If you want to generate Unix specific guide from our sample
 document (<xref linkend="ex:doc"/>) you can do it in the following
 way. (We assume, that command <command>saxon</command> is able to run
-XSLT processor on your machine. You can use your preffered XSLT
+XSLT processor on your machine. You can use your preferred XSLT
 processor instead.)</para>
 
 <screen><command>saxon</command> <option>-o</option> unixsample.xml sample.xml profile.xsl "os=unix"</screen>
@@ -260,7 +260,7 @@ by semicolon:</para>
 <programlisting><![CDATA[<para os="unix;mac;win">...</para>]]></programlisting>
 
 <para>It is possible to use different separator than semicolon by
-setting <parameter>sep</parameter> parameter. There cann't be spaces
+setting <parameter>sep</parameter> parameter. There can't be spaces
 between separator and target names.</para>
 
 <para>You can also perform profiling based on several profiling

LDP/defunct/scrollserver/stylesheets/docbook/extensions/doc/saxon5/com/nwalsh/saxon/Verbatim.html

@@ -356,7 +356,7 @@ <H2>
  <tt>areaset</tt> get the same number.</p>
 
  <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
- supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+ supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
  If only a line is specified, the callout decoration appears in
  the defaultColumn. Lines will be padded with blanks to reach the
  necessary column, but callouts that are located beyond the last
@@ -403,7 +403,7 @@ <H2>
  parenthesis.</p>
 
  <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
- supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+ supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
  If only a line is specified, the callout decoration appears in
  the defaultColumn. Lines will be padded with blanks to reach the
  necessary column, but callouts that are located beyond the last

LDP/defunct/scrollserver/stylesheets/docbook/extensions/doc/saxon5/com/nwalsh/saxon/package-summary.html

@@ -116,7 +116,7 @@ <H2>
 in this Software without prior written authorization from the
 individuals in question.</p>
 
-<p>Anything derived from this Software that is publically
+<p>Anything derived from this Software that is publicly
 distributed will be identified with a different name and the
 version strings in any derived Software will be changed so that no
 possibility of confusion between the derived package and this

LDP/defunct/scrollserver/stylesheets/docbook/extensions/doc/saxon6/com/nwalsh/saxon6/Verbatim.html

@@ -268,7 +268,7 @@ <H2>
  <tt>areaset</tt> get the same number.</p>
 
  <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
- supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+ supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
  If only a line is specified, the callout decoration appears in
  the defaultColumn. Lines will be padded with blanks to reach the
  necessary column, but callouts that are located beyond the last

LDP/defunct/scrollserver/stylesheets/docbook/extensions/doc/saxon6/com/nwalsh/saxon6/package-summary.html

@@ -130,7 +130,7 @@ <H2>
 in this Software without prior written authorization from the
 individuals in question.</p>
 
-<p>Anything derived from this Software that is publically
+<p>Anything derived from this Software that is publicly
 distributed will be identified with a different name and the
 version strings in any derived Software will be changed so that no
 possibility of confusion between the derived package and this

LDP/defunct/scrollserver/stylesheets/docbook/extensions/saxon642/com/nwalsh/saxon/CalloutEmitter.java

@@ -277,7 +277,7 @@ protected void formatPad(int numBlanks) {
    * the global callout array if it can be interpreted.</p>
    *
    * <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
-   * supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+   * supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
    * If only a line is specified, the callout decoration appears in
    * the <tt>defaultColumn</tt>.</p>
    *

LDP/defunct/scrollserver/stylesheets/docbook/extensions/saxon642/com/nwalsh/saxon/Verbatim.java

@@ -271,7 +271,7 @@ public static NodeSetValue numberLines (Context context,
    * <dt><code>callout.graphics</code></dt>
    * <dd>Are we using callout graphics? A value of 0 or "" is false,
    * any other value is true. If callout graphics are not used, the
-   * parameters related to graphis are not queried.</dd>
+   * parameters related to graphics are not queried.</dd>
    * <dt><code>callout.graphics.path</code></dt>
    * <dd>Specifies the path to callout graphics.</dd>
    * <dt><code>callout.graphics.extension</code></dt>
@@ -409,7 +409,7 @@ private static void setupCallouts(Context context) {
    * <tt>areaset</tt> get the same number.</p>
    *
    * <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
-   * supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+   * supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
    * If only a line is specified, the callout decoration appears in
    * the defaultColumn. Lines will be padded with blanks to reach the
    * necessary column, but callouts that are located beyond the last

LDP/defunct/scrollserver/stylesheets/docbook/extensions/saxon642/com/nwalsh/saxon/package.html

@@ -25,7 +25,7 @@
 in this Software without prior written authorization from the
 individuals in question.</p>
 
-<p>Anything derived from this Software that is publically
+<p>Anything derived from this Software that is publicly
 distributed will be identified with a different name and the
 version strings in any derived Software will be changed so that no
 possibility of confusion between the derived package and this

LDP/defunct/scrollserver/stylesheets/docbook/extensions/saxon643/com/nwalsh/saxon/CalloutEmitter.java

@@ -279,7 +279,7 @@ protected void formatPad(int numBlanks) {
    * the global callout array if it can be interpreted.</p>
    *
    * <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
-   * supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+   * supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
    * If only a line is specified, the callout decoration appears in
    * the <tt>defaultColumn</tt>.</p>
    *

LDP/defunct/scrollserver/stylesheets/docbook/extensions/saxon643/com/nwalsh/saxon/Verbatim.java

@@ -274,7 +274,7 @@ public static NodeSetValue numberLines (Context context,
    * <dt><code>callout.graphics</code></dt>
    * <dd>Are we using callout graphics? A value of 0 or "" is false,
    * any other value is true. If callout graphics are not used, the
-   * parameters related to graphis are not queried.</dd>
+   * parameters related to graphics are not queried.</dd>
    * <dt><code>callout.graphics.path</code></dt>
    * <dd>Specifies the path to callout graphics.</dd>
    * <dt><code>callout.graphics.extension</code></dt>
@@ -412,7 +412,7 @@ private static void setupCallouts(Context context) {
    * <tt>areaset</tt> get the same number.</p>
    *
    * <p>Only the <tt>linecolumn</tt> and <tt>linerange</tt> units are
-   * supported. If no unit is specifed, <tt>linecolumn</tt> is assumed.
+   * supported. If no unit is specified, <tt>linecolumn</tt> is assumed.
    * If only a line is specified, the callout decoration appears in
    * the defaultColumn. Lines will be padded with blanks to reach the
    * necessary column, but callouts that are located beyond the last