Clarify wording a little.

diff --git a/FAQ b/FAQ
index e00651e9c55d6d780277e7954b08a4bb325c903b..e2e1c2f92ef6c6fccb4b8d6e64a8dcfd54704271 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -897,16 +897,14 @@ thread-safe):
 
 * Why does Valgrind complain about the use of uninitialized data?
 
-OpenSSL does internally call its own PRNG routines to retrieve random
-numbers. It so does with uninitialed buffer contents. The buffer
-contents is mixed into the entropy pool so that it technically does
-not matter whether the buffer is initialized at this point or not.
-Valgrind (and other test tools) will complain whatsoever. When
-using Valgrind, make sure to use an OpenSSL library that has been
-compiled with the PEDANTIC macro being defined (-DPEDANTIC) to
-get rid of these warnings. Compling with -DPURIFY will help as well.
-
-The PEDANTIC macro was added in OpenSSL 0.9.8f.
+When OpenSSL's PRNG routines are called to generate random numbers the supplied
+buffer contents are mixed into the entropy pool: so it technically does not
+matter whether the buffer is initialized at this point or not.  Valgrind (and
+other test tools) will complain about this. When using Valgrind, make sure the
+OpenSSL library has been compiled with the PEDANTIC macro defined (-DPEDANTIC)
+to get rid of these warnings.  Compling with -DPURIFY will help as well.
+
+The use of PEDANTIC with the PRNG was added in OpenSSL 0.9.8f.
 
 
 ===============================================================================