--- a/Symbian3/PDK/Source/GUID-C7F3EDA1-B935-5F5F-AFD4-A3CABA0C031C.dita	Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-C7F3EDA1-B935-5F5F-AFD4-A3CABA0C031C.dita	Fri Aug 13 16:47:46 2010 +0100
@@ -32,14 +32,14 @@
 images below illustrate how the interface extensibility feature works. </p> <p>The
 class diagram shows the implementation of the original interface. </p> <fig id="GUID-C85FB42D-1EE5-508E-B81F-D96B8A8E23E7">
 <title>              Class diagram of the original interface            </title>
-<image href="GUID-7D78DFA8-301C-5A0C-9F83-7C4BBEAE34C2_d0e220721_href.jpg" placement="inline"/>
+<image href="GUID-7D78DFA8-301C-5A0C-9F83-7C4BBEAE34C2_d0e218556_href.jpg" placement="inline"/>
 </fig> <p>The next class diagram shows an example of the original class <b>CImplementationClass</b> supporting
 two extensions . The extensions have been added to the <b>CExampleInterface</b> each
 using a different implementation methodology . </p> <p> <b>CExampleInterfaceExtended</b> requires
 no data and so has been added to the inheritance of the original plug-in <b>CImplementationClass</b> object. <b>MExampleInterfaceExtended2</b> shows
 how extensions can be realized in separate objects with their own data. </p> <fig id="GUID-B2D1AF5C-0789-5D9B-8EB1-13226C864D38">
 <title>              Class diagram of the extended interface            </title>
-<image href="GUID-DAF12BDB-5453-5DDD-ACBA-4C29AE448D87_d0e220750_href.jpg" placement="inline"/>
+<image href="GUID-DAF12BDB-5453-5DDD-ACBA-4C29AE448D87_d0e218585_href.jpg" placement="inline"/>
 </fig> <p>The extended interfaces should maintain the binary compatibility
 by not changing the original interface class definition. The functional compatibility
 should be maintained by incorporating interface extensions as optional. This