diff --git a/LDP/howto/linuxdoc/Shadow-Password-HOWTO.sgml b/LDP/howto/linuxdoc/Shadow-Password-HOWTO.sgml
index 148a4e9e..54b80ac2 100644
--- a/LDP/howto/linuxdoc/Shadow-Password-HOWTO.sgml
+++ b/LDP/howto/linuxdoc/Shadow-Password-HOWTO.sgml
@@ -1210,7 +1210,7 @@ For example, let look again at <tt>fred</tt>
 fred P 03/04/96 0 60 0 0</verb></tscreen>
 This means that <tt>fred</tt>'s password is valid, it was last changed on
 03/04/96, it can be changed at any time, it expires after 60 days, fred will
-not be warned, and and the account won't be disabled when the password
+not be warned, and the account won't be disabled when the password
 expires.
 <p>
 This simply means that if <tt>fred</tt> logs in after the password expires,
@@ -1383,7 +1383,7 @@ information.
 <p>
 Adding shadow support to a program is actually fairly straightforward.  The
 only problem is that the program must be run by root (or SUID root) in order
-for the the program to be able to access the <tt>/etc/shadow</tt> file.
+for the program to be able to access the <tt>/etc/shadow</tt> file.
 <p>
 This presents one big problem: very careful programming practices must be
 followed when creating SUID programs.  For instance, if a program has a shell