Some fixes to wording and spelling

CVS version numbers

english/devel/debian-volatile/index.wml: 1.1 -> 1.2

1 files changed, 12 insertions, 12 deletions

diff --git a/english/devel/debian-volatile/index.wml b/english/devel/debian-volatile/index.wml
index e289e819d09..46629372237 100644
--- a/english/devel/debian-volatile/index.wml
+++ b/english/devel/debian-volatile/index.wml
@@ -41,9 +41,9 @@ guaranteed, as well as the upgrade to the next stable release
 (etch).</p>
 
 <p><strong>Contact</strong><br />
-The generic contact address (new packages, mirror requests, ...) is
+The generic contact address (new packages, mirror requests, ...) is the mailing list
 <a href="mailto:debian-volatile@lists.debian.org">debian-volatile@lists.debian.org</a>.</p>
-<p>If you want to subscribe to that address, please see
+<p>If you want to subscribe to that list, please see
 <a href="http://lists.debian.org/debian-volatile">http://lists.debian.org/debian-volatile</a>
 for details.</p>
 
@@ -68,7 +68,7 @@ following criteria:</p>
    use" security.d.o, and they should be confident that nothing is broken by
    that.</li>
 
- <li>For bugs, the normal debian bug tracking system should be used.</li>
+ <li>For bugs, the normal Debian bug tracking system should be used.</li>
 
  <li>Packages in main cannot require any software outside of main for
    execution or compilation. Packages need to be autobuildable within the
@@ -80,8 +80,8 @@ http://release.debian.org/sarge_rc_policy.txt</a>
    as a hint what's not ok.</li>
 
  <li>The upgrade path from volatile to the next stable release needs to be at
-  least as easy as from the current stable release; means e.g.
-  that the version in volatile must not be higher than in testing.</li>
+  least as easy as from the current stable release; meaning e.g.
+  that the version number in volatile must not be higher than in testing.</li>
 </ul>
 
 <p><strong>Procedure for a package to be included</strong><br />
@@ -89,12 +89,12 @@ We experienced that the following procedure works quite well for new
 packages to be included to debian-volatile:</p>
 <ol>
 <li>Send a mail to debian-volatile@lists.debian.org<br />
-   This is for discussing your changes in public. It is also a good idea to
+   This list is for discussing your changes in public. It is also a good idea to
    include a link to a unified diff. Please remember the debian-volatile
-   guidelines, i.e. make only necessary changes.<br />
+   guidelines, i.e. only make necessary changes.<br />
    I hereby encourage fellow developers to activly participate in this
    discussion as the debian-volatile team wants to know which changes
-   the users want, and which not ... Everybody on the list is encouraged
+   the users want, and which not ... Everybody on the list are encouraged
    to review the proposed changes.</li>
 
 <li>Upload to debian-volatile<br />
@@ -108,17 +108,17 @@ packages to be included to debian-volatile:</p>
    previous version are security fixes, please tell us in advance. If
    you already have, please put CAN numbers in the changelog. If you
    do not have them, please tell us, we can obtain them for you. If you
-   want to contact the volatile-team private, then please speak with one
+   want to contact the volatile-team in private, then please speak with one
    of its team members. Sometimes there are embargo dates on
    publication of security bugs / fixes. We respect them.</li>
 
 <li>Packages are built automatically<br />
-   Now packages are built by the autobuilder network. No interaction is
+   Packages are now built by the autobuilder network. No interaction is
    needed here.</li>
 
 <li>volatile-announce-mail is being prepared<br />
-   While the package is autobuilt the debian-volatile team will contact
-   you about the content of the announce mail which is send via
+   While the package is autobuilt, the debian-volatile team will contact
+   you about the content of the announcement mail which is sent via
    debian-volatile-announce@lists.debian.org</li>
 
 <li>Package is released.<br />