--- a/Symbian3/SDK/Source/GUID-4ADD8234-4AFD-4E80-94A4-AC018FE83276.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-4ADD8234-4AFD-4E80-94A4-AC018FE83276.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -18,7 +18,7 @@
 <li><p>Spawn APIs</p></li>
 <li><p>Libgmodule APIs </p></li>
 </ul>
-<section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-11-1-1-7-1-6-1-4-1-3-3">       <title>Memory
+<section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-13-1-1-7-1-6-1-4-1-3-3">       <title>Memory
 allocation</title>       <p>The Symbian GLib implementation does not follow
 the default OSS behavior. The default OSS behavior is such that in the event
 of a memory allocation failure the application, using <codeph>g_malloc()</codeph> and
@@ -30,7 +30,7 @@
 all the application code written using GLib does not perform memory allocation
 failure checks. Hence, for Symbian GLib it is the application programmer's
 responsibility to check for memory allocation failures.  </p>     </section>
-<section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-11-1-1-7-1-6-1-4-1-3-4">       <title>Spawn
+<section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-13-1-1-7-1-6-1-4-1-3-4">       <title>Spawn
 APIs</title>       <p>GLib has a set of APIs for process spawning. Since Symbian
 platform does not support the <codeph>fork()</codeph> and <codeph>exec()</codeph> APIs,
 the <codeph>g_spawn*</codeph> APIs have limitations in their functionality.