diff --git a/internals2/memory/management.xml b/internals2/memory/management.xml
index 7b8fcf286f..70732cdec3 100644
--- a/internals2/memory/management.xml
+++ b/internals2/memory/management.xml
@@ -116,11 +116,11 @@
 
   <para>
    As said above it is an essential part of the memory management to avoid
-   having memory leaks and therefore free all memory you've allocated. As a
-   safety net the Zend Engine will free all memory, which had been allocated
-   using above mentioned APIs at the end of a request. If PHP was built using
-   the <code>--enable-debug</code> configuration option this will lead to a
-   warning.
+   having memory leaks and therefore free all memory you've allocated as soon
+   as possible. As a safety net the Zend Engine will free all memory, which had
+   been allocated using above mentioned APIs at the end of a request. If PHP 
+   was built using the <code>--enable-debug</code> configuration option this 
+   will lead to a warning.
   </para>
 
   <example xml:id="internals2.memory.management.example.leak">
@@ -143,7 +143,7 @@ ZEND_FUNCTION(leak)
    <screen>
 <![CDATA[
 [Thu Oct 22 02:14:57 2009]  Script:  '-'
-/home/hohannes/src/PHP_5_3/Zend/zend_builtin_functions.c(1377) :  Freeing 0x088888D4 (3 bytes), script=-
+/home/johannes/src/PHP_5_3/Zend/zend_builtin_functions.c(1377) :  Freeing 0x088888D4 (3 bytes), script=-
 === Total 1 memory leaks detected ===
 ]]>
    </screen>
@@ -151,9 +151,9 @@ ZEND_FUNCTION(leak)
 
   <note>
    <simpara>
-    When dealing with PHP variables you have to make sure the variable is
-    allocated using emalloc and take care of the reference count. Details can
-    be found in <xref linkend="internals2.variables"/>.
+    When dealing with PHP variables you have to make sure the variable's
+    memory is allocated using emalloc and take care of the reference count.
+    Details can be found in <xref linkend="internals2.variables"/>.
    </simpara>
   </note>