--- a/Symbian3/PDK/Source/GUID-22E46647-D677-5A47-A7E0-E1E0AE736B27.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-22E46647-D677-5A47-A7E0-E1E0AE736B27.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -43,7 +43,7 @@
 A configuration at ROM build time decides which implementation is used. </p>
 <fig id="GUID-E4CD5B76-03E0-5F4C-8C65-C2F2B52969F5">
 <title>           DirectGDI architecture          </title>
-<image href="GUID-912643B5-0B8D-5836-B864-9A2DBAC86B00_d0e265062_href.png" placement="inline"/>
+<image href="GUID-912643B5-0B8D-5836-B864-9A2DBAC86B00_d0e271062_href.png" placement="inline"/>
 </fig>
 <p>Notice that all three of the implementations implement the common <xref href="GUID-97E3E8DD-A2DA-3961-96E3-41AEAFFDD275.dita"><apiname>MDirectGdiEngine</apiname></xref> interface.
 Also notice that the hardware implementation uses asynchronous calls to the
@@ -58,7 +58,7 @@
 red. Classes that cross the generic layer boundary have some parts that cannot
 be modified (such as a fixed API), but have other parts that can be modified. </p> <fig id="GUID-1A830274-D596-586A-B469-0CB7619FB391">
 <title>              The DirectGDI generic layer classes            </title>
-<image href="GUID-26B3BB7B-53CC-518F-85DA-CBAAD52DCE1C_d0e265087_href.png" placement="inline"/>
+<image href="GUID-26B3BB7B-53CC-518F-85DA-CBAAD52DCE1C_d0e271087_href.png" placement="inline"/>
 </fig> </section>
 </conbody><related-links>
 <link href="GUID-A2E07A3C-B3A8-50B9-BD60-F1F01795FA24.dita"><linktext>DirectGDI