From 9da65aa26b37b96fddc0649a5f5edf45d1e316c0 Mon Sep 17 00:00:00 2001
From: Matthias Andree <matthias.andree@gmx.de>
Date: Wed, 29 Apr 2009 12:34:54 +0000
Subject: Make document valid XHTML again.

svn path=/branches/BRANCH_6-3/; revision=5272
---
 fetchmail-FAQ.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index effae468..026c4a03 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -386,7 +386,7 @@ introduced in the upper half of the sequence; if it doesn't, the
 failure was introduced in the lower half. Now bisect that half in
 the same way. In a very few tries, you should be able to identify
 the exact adjacent pair of versions between which your bug was
-introduced. <STRONG>Please</STRONG> include session transcripts (as 
+introduced. <strong>Please</strong> include session transcripts (as
 described in the last bullet point above) of <strong>both
 the working and failing versions.</strong> Often, the source of the problem
 can instantly identified by looking at the differences in protocol
@@ -485,8 +485,8 @@ fetchmail. It's a Mailman list, see <a
 &lt;fetchmail-devel@lists.berlios.de&gt; for people who want to discuss
 fixes and improvements in fetchmail and help co-develop it. It's a
 Mailman list, which you can sign up for at <a
-href="http://lists.berlios.de/mailman/listinfo/fetchmail-devel">http://lists.berlios.de/mailman/listinfo/fetchmail-devel</a>.
-There is also an announcements-only list,
+href="http://lists.berlios.de/mailman/listinfo/fetchmail-devel">http://lists.berlios.de/mailman/listinfo/fetchmail-devel</a>.</p>
+<p>There is also an announcements-only list,
 &lt;fetchmail-announce@lists.berlios.de&gt;, which you can sign up for at <a
 href="http://lists.berlios.de/mailman/listinfo/fetchmail-announce">http://lists.berlios.de/mailman/listinfo/fetchmail-announce</a>.</p>
 
-- 
cgit v1.2.3