diff --git a/LDP/ldpwn/20030527.xml b/LDP/ldpwn/20030527.xml
index 523c9bc3..3e705f73 100644
--- a/LDP/ldpwn/20030527.xml
+++ b/LDP/ldpwn/20030527.xml
@@ -95,7 +95,7 @@ Robinson subjected the default LDP license to a Debian Free Software
Guidelines analysis
and proposed several changes to it. People further discussed the license
-and the changes on the the debian-legal mailing
list.
diff --git a/LDP/ldpwn/20030722.xml b/LDP/ldpwn/20030722.xml
index f0a9b4ce..6be61dff 100644
--- a/LDP/ldpwn/20030722.xml
+++ b/LDP/ldpwn/20030722.xml
@@ -70,7 +70,7 @@ default in the standard XFree86 package, Eric Steven Raymond's LOST (Linux One Stanza Tips) project is a series of small Linux related hints and tips and a set of of scripts/programs for interfacing the snippets with existing mailers and web pages. The LOST project was born in the Linux-India-Help mailing list in Aug 2001 because the developers of the project felt that as newbies join the list, the same queries are floated time and again.
+The LOST (Linux One Stanza Tips) project is a series of small Linux related hints and tips and a set of scripts/programs for interfacing the snippets with existing mailers and web pages. The LOST project was born in the Linux-India-Help mailing list in Aug 2001 because the developers of the project felt that as newbies join the list, the same queries are floated time and again.
diff --git a/LDP/ldpwn/20031125.xml b/LDP/ldpwn/20031125.xml
index 81514f9d..9daef02c 100644
--- a/LDP/ldpwn/20031125.xml
+++ b/LDP/ldpwn/20031125.xml
@@ -167,7 +167,7 @@ url="http://www.opencontent.org/opl.shtml">http://www.opencontent.org/opl.shtml<
any issues and what people think in general about documentation
licenses. David Lawyer said
-that that LDP needs to create it's own license and prevent documentation
+that the LDP needs to create it's own license and prevent documentation
abuse. Andy Oram suggested that the LDP should contact the Creative
Commons for help. Somewhere in the discussion, Colin Watson Saqib Ali created a website that can
convert the XML Documents stored in the CVS to HTML/PDF on-the-fly. The
-idea is to to let the HOWTO authors to view the HTML/PDF output of their
+idea is to let the HOWTO authors to view the HTML/PDF output of their
XML source once they commit the source to the CVS. Using the converter
is as simple as going to something like http://www.xml-dev.com:8080/tldp/http://cvsview.tldp.org/index.cgi/*checkout*/LDP/howto/docbook/DocBook-OpenJade-SGML-XML-HOWTO.xml.
diff --git a/LDP/ldpwn/20050330.xml b/LDP/ldpwn/20050330.xml
index 86a499b6..0ffa8b5e 100644
--- a/LDP/ldpwn/20050330.xml
+++ b/LDP/ldpwn/20050330.xml
@@ -118,7 +118,7 @@ first review all the docs on this subject. If docs were not being adequately
maintained, she would try to find new authors. She would also try to find
authors for areas covered by the subject but not adequately by any LDP docs.
She would suggest mergers or splits in exiting documents. New doc proposals
-would go the the appropriate subject specialist. He said that there
+would go to the appropriate subject specialist. He said that there
should be a subject specialist coordinator and the subject specialist
coordinator would need to have good knowledge of all aspects of Linux and have
time to check out the facts when disputes arose. The subject specialist
diff --git a/LDP/ldpwn/20060404.xml b/LDP/ldpwn/20060404.xml
index 939686e2..c9476652 100644
--- a/LDP/ldpwn/20060404.xml
+++ b/LDP/ldpwn/20060404.xml
@@ -42,7 +42,7 @@
There is a discussion
- going on on what the best manner is to convert your docbook xml
+ going on what the best manner is to convert your docbook xml
document into pdf. A few different manners are mentioned. But there is
still no winner! That is normal, because it is also a matter of
taste.