--- a/Symbian3/SDK/Source/GUID-66C1493D-5B85-558A-9A39-454E6EBA307B.dita	Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-66C1493D-5B85-558A-9A39-454E6EBA307B.dita	Thu Mar 11 15:24:26 2010 +0000
@@ -10,7 +10,7 @@
 <!DOCTYPE concept
   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
 <concept id="GUID-66C1493D-5B85-558A-9A39-454E6EBA307B" xml:lang="en"><title>Signal
-Emulation on Symbian Platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+Emulation on the Symbian Platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
 <p>The <codeph>libc</codeph> library of P.I.P.S. provides support for POSIX
 signals, thereby facilitating the porting of applications that use signals
 for exception handling and as control IPC. </p>
@@ -29,7 +29,7 @@
 <li id="GUID-177E6544-106B-5E8B-94C6-B0AAD6437C4C"><p>There might be a considerable
 amount of latency when you send or receive signals. </p> </li>
 </ul>
-<section><title>Sending signals</title> <p>Signals can be sent between P.I.P.S.
+<section id="GUID-BD44C679-553C-402B-AF78-8922E15884E4"><title>Sending signals</title> <p>Signals can be sent between P.I.P.S.
 processes using <xref href="GUID-16DC4A9D-44BC-36E2-AB97-5E9E7521937D.dita"><apiname>kill()</apiname></xref>, <xref href="GUID-EB7F74AE-091B-32C3-9D73-18B82F8D3D73.dita"><apiname>raise()</apiname></xref> or <xref href="GUID-3C70BF0B-CD6E-3A30-A9E6-4CCF11D47EEC.dita"><apiname>sigqueue()</apiname></xref>. </p> <p>You
 can use these functions to send any of the supported signals (refer to the
 following table). </p> <p>The P.I.P.S. runtime sends the following signals
@@ -44,13 +44,13 @@
 </ul> <p> <b>Note:</b> Always ensure that you handle <codeph>SIGPIPE</codeph>, <codeph>SIGCHLD</codeph> or <codeph>SIGALRM</codeph> using
 a signal handler to avoid the termination of the process receiving these signals.
 For more information about handling signals, see the following section. </p> </section>
-<section><title>Handling signals</title> <p>A signal can be received by a
+<section id="GUID-E244317F-3B69-4B10-8156-03F4A807E663"><title>Handling signals</title> <p>A signal can be received by a
 process at any time and is handled immediately, unless it is currently blocked.
 You can handle a signal in the following ways: </p> <ol id="GUID-F03B299F-A527-5365-81D3-DDDC607A4094">
 <li id="GUID-DF0E70C8-74C2-5ACC-B556-8D216275C554"><p> <b>Use default handling:</b> The
-default action for each signal supported on Symbian platform is listed in
-the following table. </p> <p> <b>Note:</b> The default action for all of the
-signals sent by the P.I.P.S. runtime (<codeph>SIGPIPE</codeph>, <codeph>SIGCHLD</codeph> or <codeph>SIGALRM</codeph>)
+default action for each signal supported on the Symbian platform
+is listed in the following table. </p> <p> <b>Note:</b> The default action
+for all of the signals sent by the P.I.P.S. runtime (<codeph>SIGPIPE</codeph>, <codeph>SIGCHLD</codeph> or <codeph>SIGALRM</codeph>)
 is process termination. You must provide a custom handler for each of these
 signals. </p> <table id="GUID-7101041B-CC50-5367-A3A2-6D15FB15C3DD">
 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
@@ -230,7 +230,7 @@
     return 0;
     }</codeblock> </li>
 </ol> </section>
-<section><title>Blocking signals</title> <p>A P.I.P.S. process can choose
+<section id="GUID-252E0621-51F1-443A-A4FC-689BD27597E3"><title>Blocking signals</title> <p>A P.I.P.S. process can choose
 to block (and subsequently unblock) signals to itself using <xref href="GUID-02901E24-3615-3018-AF20-F5D5D63FD708.dita"><apiname>sighold()</apiname></xref>, <xref href="GUID-AE4CC3C8-C6D4-3F5C-A28F-C4AAB63E8992.dita"><apiname>sigset()</apiname></xref>, <xref href="GUID-68BD2914-FB73-3D91-9D81-425BF2436473.dita"><apiname>sigrelse()</apiname></xref> and <xref href="GUID-C7279C75-CB98-3F24-ABAA-76CF0009A8ED.dita"><apiname>sigprocmask()</apiname></xref>. Signals that are blocked on a P.I.P.S.
 process are not be delivered for handling. Instead, they are queued to be
 handled when they are unblocked. </p> <p>Non-realtime signals are queued only