You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by pg...@apache.org on 2002/09/26 20:40:09 UTC
cvs commit: jakarta-james/www contribute.html
pgoldstein 2002/09/26 11:40:09
Modified: src/xdocs contribute.xml
www contribute.html
Log:
Spelling/grammar fixes for contribute page. Thanks to Tetsuya Kitahata.
Revision Changes Path
1.4 +6 -6 jakarta-james/src/xdocs/contribute.xml
Index: contribute.xml
===================================================================
RCS file: /home/cvs/jakarta-james/src/xdocs/contribute.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- contribute.xml 30 Jul 2002 13:37:34 -0000 1.3
+++ contribute.xml 26 Sep 2002 18:40:09 -0000 1.4
@@ -7,9 +7,9 @@
<body>
<section name="Introduction">
<p>
- <b>anyone can contribute></b><br/>
- Thats right, we always want to hear from people with contributions to the code,
- the documentation, the website and bug reports.<br/>
+ <b>Anyone can contribute</b><br/>
+ That's right, we always want to hear from people with contributions to the code,
+ the documentation, the website, and bug reports.<br/>
The rest of this document outlines the way to go about these to maximum effect.<br/>
</p>
<p>
@@ -27,7 +27,7 @@
Patches should be submitted to the developers mailing list.<br/>
<b>Always</b> use diff -u to generate patches, make sure you are patching the latest cvs (the HEAD).<br/>
Make your patch from the jakarta-james directory and make sure it conforms
- to the code standards, otherwise it may be ignored. Its is OK to make a single patch covering several
+ to the code standards, otherwise it may be ignored. It is OK to make a single patch covering several
files, but please only one issue at a time.<br/>
Prefix the mail subject with [PATCH]<br/>
Briefly outline the reason for your patch,
@@ -48,7 +48,7 @@
your submission conforms to the code standards. Provide a Brief outline of
your intentions, as above, so that your code can be reviewed easily, and a
note of any relevant bug numbers.<br/>
- New files must contain a refrence to the Apache licence, copy the header from an existing file.<br/>
+ New files must contain a reference to the Apache licence, copy the header from an existing file.<br/>
It also helps if you send your files in an archive (tar, zip) which preserves directories, make it from the jakarta-james directory so we can un-tar your files into the right place.
</p>
</section>
@@ -79,7 +79,7 @@
If this means nothing to you please try to contribute HTML or plain text documents without
any styling, so that we can get at the words and easily convert them into our xml format.<br/>
If all this seems like unnecessary nonsense, send us whatever you like, we'd still be
- happy to recieve good documentation.
+ happy to receive good documentation.
</p>
</section>
1.5 +6 -6 jakarta-james/www/contribute.html
Index: contribute.html
===================================================================
RCS file: /home/cvs/jakarta-james/www/contribute.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- contribute.html 30 Aug 2002 15:04:30 -0000 1.4
+++ contribute.html 26 Sep 2002 18:40:09 -0000 1.5
@@ -163,10 +163,10 @@
<p>
-<b>anyone can contribute></b>
+<b>Anyone can contribute</b>
<br>
- Thats right, we always want to hear from people with contributions to the code,
- the documentation, the website and bug reports.<br>
+ That's right, we always want to hear from people with contributions to the code,
+ the documentation, the website, and bug reports.<br>
The rest of this document outlines the way to go about these to maximum effect.<br>
</p>
@@ -204,7 +204,7 @@
<b>Always</b> use diff -u to generate patches, make sure you are patching the latest cvs (the HEAD).<br>
Make your patch from the jakarta-james directory and make sure it conforms
- to the code standards, otherwise it may be ignored. Its is OK to make a single patch covering several
+ to the code standards, otherwise it may be ignored. It is OK to make a single patch covering several
files, but please only one issue at a time.<br>
Prefix the mail subject with [PATCH]<br>
Briefly outline the reason for your patch,
@@ -237,7 +237,7 @@
your submission conforms to the code standards. Provide a Brief outline of
your intentions, as above, so that your code can be reviewed easily, and a
note of any relevant bug numbers.<br>
- New files must contain a refrence to the Apache licence, copy the header from an existing file.<br>
+ New files must contain a reference to the Apache licence, copy the header from an existing file.<br>
It also helps if you send your files in an archive (tar, zip) which preserves directories, make it from the jakarta-james directory so we can un-tar your files into the right place.
</p>
@@ -288,7 +288,7 @@
If this means nothing to you please try to contribute HTML or plain text documents without
any styling, so that we can get at the words and easily convert them into our xml format.<br>
If all this seems like unnecessary nonsense, send us whatever you like, we'd still be
- happy to recieve good documentation.
+ happy to receive good documentation.
</p>
</blockquote>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>