[GNU-traductores] gnudist:/home/www/html/server/standards/README.html -- recent changes

[gnudist's file diff daemon]

This is an automated report from gnudist.
Recent changes to /home/www/html/server/standards/README.html:

  14 -rw-rw-r--   1 webcvs   www         12990 Feb 26 13:00 
/home/www/html/server/standards/README.html

diff  -u  
/home/diffmon/old_file_dir/gnudist:!home!www!html!server!standards!README.html.gz
 /home/www/html/server/standards/README.html
--- /tmp/diffmon21783   Tue Feb 27 05:13:44 2001
+++ /home/www/html/server/standards/README.html Mon Feb 26 13:00:03 2001
@@ -55,7 +55,7 @@
 In order to work as a webmaster you need one of the following:
 
 <UL>
-<LI> Become a developper for one of the GNU packages managed by 
+<LI> Become a developer for one of the GNU packages managed by 
     <a HREF="http://savannah.gnu.org/";>Savannah</a>. This will
     allow you to edit the portion of the www.gnu.org web that
     is devoted to this GNU package, as shown in the 
@@ -72,18 +72,20 @@
 The whole www.gnu.org web site is stored under CVS on
 subversions.gnu.org.  Most of the webmaster tasks do not require a
 shell account on gnudist.gnu.org and are a lot simpler to perform by
-checking out the pages on your local machine, modify them and then
-commit the result. For an example of instructions on how to use CVS for this
-purpose, see the <a HREF="http://savannah.gnu.org/cvs/?group_id=2";>CVS
-instructions for the GNU mifluz package</a>.
+checking out the pages on your local machine, modifying them and then
+committing the result. For an example of instructions on how to use
+CVS for this purpose, see the <a
+HREF="http://savannah.gnu.org/cvs/?group_id=2";>CVS instructions for
+the GNU mifluz package</a>.
 
 <P>
-When a commit is done, a synchronization process will update the www.gnu.org
-web site immediately. At the end of the commit operation the changes must
-be visible at www.gnu.org. If it's not the case, complain to <a 
HREF="mailto:address@hidden";>address@hidden</a>.
+When a commit is done, a synchronization process will update the
+www.gnu.org web site immediately. At the end of the commit operation
+the changes should be visible at www.gnu.org. If it's not the case,
+complain to <a HREF="mailto:address@hidden";>address@hidden</a>.
 
 <P>
-In order to be granted edit permissions for a project you must fist
+In order to be granted edit permissions for a project you must first
 <a HREF="https://savannah.gnu.org/account/register.php";>register yourself</a>
 on Savannah. This is a very simple step that anyone can do.
 
@@ -94,35 +96,38 @@
 <P>
 Instead of having a single group of users who have edit permissions
 over the whole www.gnu.org CVS tree, a number of groups have been
-created and only have edit permissions on a specicific directory
+created and only have edit permissions on a specific directory
 tree. For instance, the <a
 HREF="http://savannah.gnu.org/projects/bravegw/";>Brave GNU World</a>
 project members only have edit permissions on the <a
 
HREF="http://www.gnu.org/brave-gnu-world/";>http://www.gnu.org/brave-gnu-world/</a>
-directory. This has a number of advantages such as easily find out
+directory. This has a number of advantages such as easily finding out
 who is in charge of which portion of the www.gnu.org web site. A
 <a HREF="www2savannah.html">www.gnu.org to Savannah projects map</a> is
 updated every day and shows which directories are handled by which projects.
 
 <P>
-Some parts of the www.gnu.org web site do not yet have a matching project
-on Savannah. Don't hesitate to <a 
HREF="http://savannah.gnu.org/register/";>create a project</a> for a given 
subdirectory
-if you plan to work on it with other webmasters. When creating the project,
-select the <i>website only</i> license. The /software/<i>package</i>
-directories have a special status since they must be bound to a project
-that have the same name on Savannah and are associated to a source CVS
-repository. You should try to get in touch with the package maintainer
-before creating a project in /software/<i>package</i>.
+Some parts of the www.gnu.org web site do not yet have a matching
+project on Savannah. Don't hesitate to
+<a HREF="http://savannah.gnu.org/register/";>create a project</a> for a
+given subdirectory if you plan to work on it with other
+webmasters. When creating the project, select the <i>website only</i>
+license. The /software/<i>package</i> directories have a special
+status since they must be bound to a project that have the same name
+on Savannah and are associated to a source CVS repository. You should
+try to get in touch with the package maintainer before creating a
+project in /software/<i>package</i>.
 
 <P>
 Since it would be very complicated for highly involved webmasters to become
 a member of each and every projects when they want to make some global 
-changes, the special project <a HREF="http://savannah.gnu.org/projects/wwww/";>
+changes, the special project <a HREF="http://savannah.gnu.org/projects/www/";>
 www</a> was created. Each member of the <i>www</i> project is granted
 edit persmission over the whole www.gnu.org CVS repository. 
 
 <P>
-If you want more information about Savannah, read the <a 
HREF="README.savannah.html">Administration Guide</a>.
+If you want more information about Savannah, read the
+<a HREF="README.savannah.html">Administration Guide</a>.
 
 <H4><A NAME="SEC1" HREF="README.html#TOC1">Style guidelines</A></H4>
 
@@ -318,7 +323,7 @@
 permitted in any medium, provided this notice is preserved.<P>
 Updated:
 <!-- hhmts start -->
-26 Feb 2001 loic
+26 Feb 2001 mhw
 <!-- hhmts end -->
 <HR>
 </BODY>