From f837179645d3cbe2d480343c8a67d8da66d53c4b Mon Sep 17 00:00:00 2001
From: Michael Jacobsen <im_nott@hotmail.com>
Date: Wed, 7 Apr 2004 19:06:35 +0000
Subject: [PATCH] Cleaned up the text concerning the need for conformance
 tests.

---
 documentation/testing.sgml | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/documentation/testing.sgml b/documentation/testing.sgml
index dae7d4b9eb0..85fc9fbfea8 100644
--- a/documentation/testing.sgml
+++ b/documentation/testing.sgml
@@ -4,12 +4,17 @@
     <sect1 id="testing-intro">
       <title>Introduction</title>
       <para>
-        With more The Windows API follows no standard, it is itself a de facto
-        standard, and deviations from that standard, even small ones, often
-        cause applications to crash or misbehave in some way. Furthermore
-        a conformance test suite is the most accurate (if not necessarily
-        the most complete) form of API documentation and can be used to
-        supplement the Windows API documentation.
+	The Windows API follows no standard, it is itself a de facto standard,
+	and deviations from that standard, even small ones, often cause
+	applications to crash or misbehave in some way.
+      </para>	
+      <para>
+	The question becomes, "How do we ensure compliance with that standard?"
+	The answer is, "By using the API documentation available to us and
+	backing that up with conformance tests." Furthermore, a conformance
+	test suite is the most accurate (if not necessarily the most complete)
+	form of API documentation and can be used to supplement the Windows
+	API documentation.
       </para>
       <para>
         Writing a conformance test suite for more than 10000 APIs is no small