Index: ossp-pkg/shiela/ChangeLog
RCS File: /v/ossp/cvs/ossp-pkg/shiela/ChangeLog,v
rcsdiff -q -kk '-r1.24' '-r1.25' -u '/v/ossp/cvs/ossp-pkg/shiela/ChangeLog,v' 2>/dev/null
--- ChangeLog	2002/12/23 08:52:22	1.24
+++ ChangeLog	2002/12/23 09:05:47	1.25
@@ -11,6 +11,9 @@
 
   Changes between 1.0.1 and 1.0.2 (22-Dec-2002 to xx-Dec-2002):
 
+   *) Fixed typos in manual pages.
+      [Ralf S. Engelschall]
+
    *) Avoid over-sized lines in xdelta based patch scripts.
       [Ralf S. Engelschall]
 
Index: ossp-pkg/shiela/shiela-install.pod
RCS File: /v/ossp/cvs/ossp-pkg/shiela/shiela-install.pod,v
rcsdiff -q -kk '-r1.13' '-r1.14' -u '/v/ossp/cvs/ossp-pkg/shiela/shiela-install.pod,v' 2>/dev/null
--- shiela-install.pod	2002/12/23 08:50:34	1.13
+++ shiela-install.pod	2002/12/23 09:05:47	1.14
@@ -93,7 +93,7 @@
 
 =item B<7.>
 
-add to C<$CVSROOT/CVSROOT/commitinfo> (the hool for checking commit
+add to C<$CVSROOT/CVSROOT/commitinfo> (the hook for checking commit
 operations): ``C<ALL $CVSROOT/CVSROOT/shiela --hook=commitinfo>''.
 
 =item B<8.>
@@ -126,12 +126,12 @@
 
 =head1 INSTALLATION: AUTOMATICALLY
 
-For convinience reasons one can alternatively use the interactive
+For convenience reasons one can alternatively use the interactive
 B<shiela-install> utility, which perform the above steps automatically
 and especially creates initial C<shiela.cfg> and C<shiela.msg> files.
 Just run C<shiela-install> and answer the questions.
 
-For convinience reasons (while testing) one can also override the
+For convenience reasons (while testing) one can also override the
 default value of a question by using C<variable=value> on the
 B<shiela-install> command line. For instance, ``C<shiela-install
 repos_path=/tmp/cvs>'' sets the default path for the question about the
Index: ossp-pkg/shiela/shiela.pod
RCS File: /v/ossp/cvs/ossp-pkg/shiela/shiela.pod,v
rcsdiff -q -kk '-r1.14' '-r1.15' -u '/v/ossp/cvs/ossp-pkg/shiela/shiela.pod,v' 2>/dev/null
--- shiela.pod	2002/12/23 08:50:34	1.14
+++ shiela.pod	2002/12/23 09:05:47	1.15
@@ -313,7 +313,7 @@
 (see B<User> and B<Group> directives) or can be given as "C<*>" (which means
 "any").  So, a specification of "C<foo>" means the user C<foo>, "C<*:bar>"
 means any user of group C<bar> and "C<*:*>" means any user of any group.
-Similarily, nobody can be expressed as C<!*:*>.
+Similarly, nobody can be expressed as C<!*:*>.
 
 Example: C<Acl foo-src/*:FOO_1_0 *:core !badboy;>
 
@@ -325,7 +325,7 @@
 reports (see B<Report> directive). To disable logging one can use "C<none>" as
 the E<lt>reportidE<gt> (and leave out the ":E<lt>targetE<gt>" part).
 
-The occurance of the logging message depends how the specified report is
+The occurrence of the logging message depends how the specified report is
 defined (by C<Report>). After it is produced it is send to E<lt>targetE<gt>
 which can be either an Email address of the form I<user>C<@>I<domain> or a
 filesystem path.
@@ -505,7 +505,7 @@
 rewrite the functionality of C<log_accum.pl>, C<commit_prep.pl> and
 C<cvs_acls.pl> from scratch. The result is B<OSSP shiela>.
 
-The name B<OSSP shiela> was choosen just by coincidence and has no
+The name B<OSSP shiela> was chosen just by coincidence and has no
 related meaning. It was just that while the program was written,
 a code-name was needed. And because Engelschall's first baby was
 forthcoming and Ralf and Daniela Engelschall reviewed lots of names, one