--- a/Symbian3/PDK/Source/GUID-EAA6A9FB-A470-550C-B7B4-FF68A733A2D5.dita	Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-EAA6A9FB-A470-550C-B7B4-FF68A733A2D5.dita	Fri Aug 13 16:47:46 2010 +0100
@@ -88,7 +88,7 @@
 already have the kernel lock, or in the case of IDFCs, you do not need to
 acquire it as no preemption can occur. In these cases, you just call <xref href="GUID-D5B555DA-3D17-3ED2-A931-CB35BD93A953.dita#GUID-D5B555DA-3D17-3ED2-A931-CB35BD93A953/GUID-76E5AE32-9A70-344A-9E6B-5B439622715A"><apiname>NFastMutex::Wait()</apiname></xref> and <xref href="GUID-D5B555DA-3D17-3ED2-A931-CB35BD93A953.dita#GUID-D5B555DA-3D17-3ED2-A931-CB35BD93A953/GUID-CA8C65D8-E59A-385A-92B8-2B22A4A2F1CB"><apiname>NFastMutex::Signal()</apiname></xref>. </p> <p>The following diagram illustrates the general principle: </p> <fig id="GUID-30A0EA62-83CF-5AB9-A07E-525D0972E55B">
 <title>Fast mutex</title>
-<image href="GUID-3AFE0D8B-FB9B-5355-A63B-FB71DD13E7D0_d0e306985_href.png" placement="inline"/>
+<image href="GUID-3AFE0D8B-FB9B-5355-A63B-FB71DD13E7D0_d0e304822_href.png" placement="inline"/>
 </fig> <p>There are a number of assumptions here, one of which is that the
 priorities are such that thread T1 does not run until a reschedule occurs,
 after T2 has been interrupted. </p> <p id="GUID-111E74A3-8442-5598-8BB9-F78E2A77610A"><b>Example
@@ -489,7 +489,7 @@
 somewhat artificial, and not based on real code, the following diagram nevertheless
 shows the basic idea behind Symbian platform semaphores. </p> <fig id="GUID-505BC4A5-BBCB-5A63-9795-C751719661BB">
 <title>Symbian platform semaphore</title>
-<image href="GUID-0FE0B646-A62F-55A8-A6E6-587D0909CE19_d0e307852_href.png" placement="inline"/>
+<image href="GUID-0FE0B646-A62F-55A8-A6E6-587D0909CE19_d0e305689_href.png" placement="inline"/>
 </fig> <p id="GUID-6131CDB0-6249-5B9A-A969-9B25F8BCECF5"><b>Rules</b> </p> <p>There
 are a few rules about the use of Symbian platform semaphores: </p> <ul>
 <li id="GUID-B850F00A-D7E6-5542-9D9D-F07F2625E29B"><p>Only Symbian platform