diff --git a/ANNOUNCE b/ANNOUNCE
index 7b2a32ff1..e5f0a0a6f 100644
--- a/ANNOUNCE
+++ b/ANNOUNCE
@@ -21,7 +21,8 @@ portion of the OpenStep standard (the Foundation library).
 1.2 Noteworthy changes in version `1.24.7'
 ==========================================
 
-   * TLS and other security improvements
+   * TLS and other security improvements (note, SSLv3.0 is disabled by
+     default in order to prevent the 'POODLE' attack).
 
    * Latest timezone data included
 
diff --git a/Documentation/GNUmakefile b/Documentation/GNUmakefile
index c99e9358b..d83d11d31 100644
--- a/Documentation/GNUmakefile
+++ b/Documentation/GNUmakefile
@@ -58,7 +58,7 @@ SUBPROJECTS = manual General
 DOCUMENT_TEXT_NAME = \
 INSTALL NEWS README ANNOUNCE
 
-TOP_DOC_FILES = INSTALL NEWS README ANNOUNCE README.initialize
+TOP_DOC_FILES = INSTALL NEWS README ANNOUNCE
 
 gnustep-base_TEXI_FILES = \
 version.texi \
diff --git a/Documentation/README.initialize b/Documentation/README.initialize
deleted file mode 100644
index a15de89e3..000000000
--- a/Documentation/README.initialize
+++ /dev/null
@@ -1,7 +0,0 @@
-The libobjc included with gcc does not have a thread-safe implementation of the initialize method. This means that any classes not already used may be incorrectly initialised, potentially causing strange behaviors and crashes.
-
-To put this into context, the runtime bug has been knoown for several years and only rarely causes problems ... the easy workaround being to ensure that any classes used by a new thread have already been used in the main thread before the new thread starts.
-
-If you are worried, please build/run GNUstep with a runtime which supports the +initialize method. The GNUstep stable runtime (libobjc) and experimental runtime (libobjc2), available from the GNUstep website and subversion repository, should both work.
-
-To disable this warning (eg. for an application which does not suffer any problems caused by this runtime bug), please set the GSSilenceInitializeWarning user default to YES.");
\ No newline at end of file
diff --git a/Documentation/news.texi b/Documentation/news.texi
index 98c65939f..3eaeb0868 100644
--- a/Documentation/news.texi
+++ b/Documentation/news.texi
@@ -14,7 +14,8 @@ See the @url{ReleaseNotes.html} document for more information.
 @section Noteworthy changes in version @samp{1.24.7}
 
 @itemize @bullet
-@item TLS and other security improvements
+@item TLS and other security improvements (note, SSLv3.0 is disabled by default
+in order to prevent the 'POODLE' attack).
 @item Latest timezone data included
 @item Various other bugfixes
 @end itemize
diff --git a/NEWS b/NEWS
index 832a9c18d..a487453a2 100644
--- a/NEWS
+++ b/NEWS
@@ -8,7 +8,8 @@ See the `ReleaseNotes.html' document for more information.
 1.1 Noteworthy changes in version `1.24.7'
 ==========================================
 
-   * TLS and other security improvements
+   * TLS and other security improvements (note, SSLv3.0 is disabled by
+     default in order to prevent the 'POODLE' attack).
 
    * Latest timezone data included
 
diff --git a/README.initialize b/README.initialize
new file mode 100644
index 000000000..fdbfc98cf
--- /dev/null
+++ b/README.initialize
@@ -0,0 +1,18 @@
+The libobjc included with older versions of gcc does not have a thread-safe
+implementation of the initialize method. This means that any classes not
+already used may be incorrectly initialised, potentially causing strange
+behaviors and crashes.
+
+To put this into context, the runtime bug has been known for several years
+and only rarely causes problems ... the easy workaround being to ensure that
+any classes used by a new thread have already been used in the main thread
+before the new thread starts.
+
+If you are worried, please build/run GNUstep with a runtime which supports
+the +initialize method. The GNUstep stable runtime (libobjc) and experimental
+runtime (libobjc2), available from the GNUstep website and subversion
+repository, should both work.
+
+To disable this warning (eg. for an application which does not suffer any
+problems caused by this runtime bug), please set the GSSilenceInitializeWarning
+user default to YES.");