diff -r 5072524fcc79 -r 80ef3a206772 Symbian3/PDK/Source/GUID-2E8929E6-9555-51D2-B41D-6F1D05A4DB87.dita
--- a/Symbian3/PDK/Source/GUID-2E8929E6-9555-51D2-B41D-6F1D05A4DB87.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-2E8929E6-9555-51D2-B41D-6F1D05A4DB87.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -29,7 +29,7 @@
 following diagram shows where render stages fit into the Window Server architecture. </p> <fig id="GUID-B1321BD9-2EF4-5BB3-8226-880C460526C1">
 <title>              Window Server architecture showing render stages    
        </title>
-<image href="GUID-25A63716-D637-589D-BAB7-B962455F2DC6_d0e243458_href.png" placement="inline"/>
+<image href="GUID-25A63716-D637-589D-BAB7-B962455F2DC6_d0e249469_href.png" placement="inline"/>
 </fig> <p>Symbian provides default render stage plug-ins, which are of production
 quality and reproduce the rendering behavior in Symbian OS v9.4. In ScreenPlay,
 device creators can replace the render stage plug-ins with their own bespoke
@@ -48,7 +48,7 @@
 a sequence of frames, in order to create the desired effect. </p> <fig id="GUID-75F4A91E-D764-5BF4-8B21-74689EB43E7A">
 <title>              A typical render stage configuration, showing some of
 the key              interfaces            </title>
-<image href="GUID-0F2AE495-F6D8-5351-BD83-76D579564C2E_d0e243480_href.png" placement="inline"/>
+<image href="GUID-0F2AE495-F6D8-5351-BD83-76D579564C2E_d0e249491_href.png" placement="inline"/>
 </fig> <p>The render stages are stacked on top of each other—effectively they
 are chained into a pipeline, in which the Window Server "talks" only to the
 first render stage. This render stage in turn talks only to the second render
@@ -98,7 +98,7 @@
 to helper classes. </p> <fig id="GUID-84104CD3-C78C-50C7-9155-50596B3EE3EF">
 <title>              A concrete render stage class implementing key render
 stage              interfaces            </title>
-<image href="GUID-973CF8E7-18C8-5E24-BC7A-97148FAEF3E4_d0e243549_href.png" placement="inline"/>
+<image href="GUID-973CF8E7-18C8-5E24-BC7A-97148FAEF3E4_d0e249560_href.png" placement="inline"/>
 </fig> </section>
 <section id="GUID-5D81D1A7-26A0-5461-9AC5-3EF359D283CB"><title>Advanced use
 case</title> <p>Render stages can optionally create their own <b>visuals tree</b> to
@@ -117,7 +117,7 @@
 drawing operations relates to. </p> <fig id="GUID-97D46D41-589A-504D-B7C0-9092E6E5DF17">
 <title>              Render stage that has a visuals tree and visual stores
            </title>
-<image href="GUID-3248A2B1-54D0-56E3-B770-DC595B01EA04_d0e243585_href.png" placement="inline"/>
+<image href="GUID-3248A2B1-54D0-56E3-B770-DC595B01EA04_d0e249596_href.png" placement="inline"/>
 </fig> <p>Render stages that implement their own visuals stores typically
 use the Window Server's <b>change-tracking</b> rendering mode. This is an
 optimization of the <xref href="GUID-22093E74-EFE7-5642-93DE-1573E18F7C08.dita">Window