[gentoo-doc-cvs] cvs commit: sudo-guide.xml

["swift" <swift@lark.gentoo.org>]

swift       05/08/04 08:05:21

  Modified:    xml/htdocs/doc/en sudo-guide.xml
  Log:
  Spelling mistakes, no content change. Fixed #101189

Revision  Changes    Path
1.5       +8 -8      xml/htdocs/doc/en/sudo-guide.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/sudo-guide.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/sudo-guide.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/sudo-guide.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo

Index: sudo-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/sudo-guide.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- sudo-guide.xml	3 Aug 2005 08:13:40 -0000	1.4
+++ sudo-guide.xml	4 Aug 2005 08:05:21 -0000	1.5
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/sudo-guide.xml,v 1.4 2005/08/03 08:13:40 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/sudo-guide.xml,v 1.5 2005/08/04 08:05:21 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -23,7 +23,7 @@
 <license/>
 
 <version>1.2</version>
-<date>2005-08-03</date>
+<date>2005-08-04</date>
 
 <chapter>
 <title>About Sudo</title>
@@ -45,8 +45,8 @@
 application (or any user of a certain group, depending on the permissions used).
 You can (and probably even should) require the user to provide a password when
 he wants to execute the application and you can even fine-tune the permissions
-based on the location where the user is at: if he is logged on from the system
-itself or through SSH from a remote site.
+based on the user's location: logged on from the system itself or through SSH 
+from a remote site.
 </p>
 
 </body>
@@ -130,7 +130,7 @@
 application that can allow people to elevate privileges. For instance, allowing
 users to execute <c>emerge</c> as root can indeed grant them full root access 
 to the system because <c>emerge</c> can be manipulated to change the live file 
-system in the user his advantage. If you do not trust your <c>sudo</c> users,
+system to the user's advantage. If you do not trust your <c>sudo</c> users,
 don't grant them any rights.
 </p>
 
@@ -182,7 +182,7 @@
 </pre>
 
 <p>
-The password that <c>sudo</c> requires is the user his own password. This is to
+The password that <c>sudo</c> requires is the user's own password. This is to
 make sure that no terminal that you accidentally left open to others is abused
 for malicious purposes.
 </p>
@@ -245,7 +245,7 @@
 <p>
 More interesting is to define a set of users who can run software administrative
 applications (such as <c>emerge</c> and <c>ebuild</c>) on the system and a group
-of administrators who can change users their password - but not roots!
+of administrators who can change the password of any user, except root!
 </p>
 
 <pre caption="Using aliases for users and commands">
@@ -346,7 +346,7 @@
 before <c>sudo</c> fails) to <c>2</c> instead of the default 3:
 </p>
 
-<pre caption="Requiring the root password instead of the user his password">
+<pre caption="Requiring the root password instead of the user's password">
 Defaults:john   runaspw, passwd_tries=2
 </pre>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list