> Could you check out the incubator-site module from cvs
> and send in your fixes in patch format?
Here's the patch.
--------
Tim
? patchfile.txt
Index: src/documentation/content/xdocs/rules-for-revolutionaries.xml
===================================================================
RCS file:
/home/cvspublic/incubator-site/src/documentation/content/xdocs/rules-for-revolutionaries.xml,v
retrieving revision 1.1
diff -u -r1.1 rules-for-revolutionaries.xml
--- src/documentation/content/xdocs/rules-for-revolutionaries.xml 10 Nov 2002
03:04:06 -0000 1.1
+++ src/documentation/content/xdocs/rules-for-revolutionaries.xml 3 Feb 2003
+01:59:56 -0000
@@ -62,8 +62,8 @@
So -- in any software development project there is a
natural tension between revolution and evolution. In a
closed source environment, you make the call at any
- particular time on whether you are in revolutionay mode or
- evolutionare mode. For example, JSDK was in evolutionary
+ particular time on whether you are in revolutionary mode or
+ evolutionary mode. For example, JSDK was in evolutionary
mode for years. Then in Nov 98, We made a decision to go
revolutionary. Of course, at the time the project team was
composed of 1 person -- me, so it was an easy decision.
@@ -106,7 +106,7 @@
the group updated on their progress, and allowing others
who want to help out to do so. The committer, and the
group of people who he/she has a attracted are free to
- take any approaches they want too free of interference.
+ take any approaches they want to free of interference.
2) When a revolution is ready for prime time, the
committer proposes a merge to the -dev list. At that
@@ -141,7 +141,7 @@
wants to bring stuff into the trunk, they propose it here
and we evaluate it on it's merits.
- If somebody disagrees with Craigs approach (for the sake
+ If somebody disagrees with Craig's approach (for the sake
of argument here), they are free to create a BLUE
whiteboard and work out what they think is a good
solution. At that point, the community will have to
Index: src/documentation/content/xdocs/drafts/voting.xml
===================================================================
RCS file:
/home/cvspublic/incubator-site/src/documentation/content/xdocs/drafts/voting.xml,v
retrieving revision 1.7
diff -u -r1.7 voting.xml
--- src/documentation/content/xdocs/drafts/voting.xml 3 Dec 2002 19:48:33 -0000
1.7
+++ src/documentation/content/xdocs/drafts/voting.xml 3 Feb 2003 01:59:56 -0000
@@ -110,7 +110,7 @@
<section>
<title>Expressing Votes: +1, 0, -1, and Fractions</title>
<p>The voting process in Apache may seem more than a little
- weird if you've never enountered it before. Votes are represented
+ weird if you've never encountered it before. Votes are represented
as numbers between -1 and +1, with '-1' meaning 'no' and '+1'
meaning 'yes.'</p>
<p>The in-between values are indicative of how strongly the
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
