--- a/Symbian3/SDK/Source/GUID-000ACB11-EDD0-5160-BC5E-4593F1BAF293.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-000ACB11-EDD0-5160-BC5E-4593F1BAF293.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -39,7 +39,7 @@
 to it is closed. The queue itself is simply a block of memory divided into
 slots, managed by the <codeph>DMsgQueue</codeph> object. </p>
 <fig id="GUID-BDA4A786-57B2-529D-BDFB-72D2B2B30670">
-<image href="GUID-7C061090-83A8-5E0F-B42B-2D722BE054EE_d0e243007_href.png" placement="inline"/>
+<image href="GUID-7C061090-83A8-5E0F-B42B-2D722BE054EE_d0e247966_href.png" placement="inline"/>
 </fig>
 <section id="GUID-1D2EF848-8068-56B9-850B-56AE88E192DE"><title>Handle to a
 message queue</title> <p>A message queue is created, opened, written to and
@@ -50,7 +50,7 @@
 the implementation, while <codeph>RMsgQueue</codeph> provides type safety.
 An <codeph>RMsgQueueBase</codeph> object is a valid message queue handle,
 but does not offer the type safety that <codeph>RMsgQueue</codeph> does. </p> <fig id="GUID-B9685695-0E07-5CC1-AFED-0ABF4DC93ACB">
-<image href="GUID-2F6EF388-CA87-5AAD-A4C5-37FC3CE15331_d0e243046_href.png" placement="inline"/>
+<image href="GUID-2F6EF388-CA87-5AAD-A4C5-37FC3CE15331_d0e248005_href.png" placement="inline"/>
 </fig> <p>Message queues are used for one-way, one to one communications only.
 The message queue is therefore unicast. If there are multiple readers of the
 message queue only one will receive the message. </p> </section>