diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-859CAA08-59C9-5FD3-98DE-6BDD0D6ED50B.dita
--- a/Symbian3/SDK/Source/GUID-859CAA08-59C9-5FD3-98DE-6BDD0D6ED50B.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-859CAA08-59C9-5FD3-98DE-6BDD0D6ED50B.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -29,7 +29,7 @@
 <fig id="GUID-19D41F69-1264-5726-9CDD-C4DD0F231BE3">
 <title>           The display is an orthogonal view of a series of layers.
          </title>
-<image href="GUID-7F3F89C0-999A-552E-90BB-17D720C53DE6_d0e184682_href.png" placement="inline"/>
+<image href="GUID-7F3F89C0-999A-552E-90BB-17D720C53DE6_d0e189679_href.png" placement="inline"/>
 </fig>
 <p>Composition requires: </p>
 <ul>
@@ -68,7 +68,7 @@
 output which is rendered, composited and displayed. </p>
 <fig id="GUID-9DF4C86A-C06D-5C5A-9AB6-E9991CC1937A">
 <title>           Graphics Composition          </title>
-<image href="GUID-F31EC49A-FE01-58B2-9CB5-4A3BBCCB7DA7_d0e184746_href.png" placement="inline"/>
+<image href="GUID-F31EC49A-FE01-58B2-9CB5-4A3BBCCB7DA7_d0e189743_href.png" placement="inline"/>
 </fig>
 <p>In a device with graphics acceleration hardware (a Graphics Processing
 Unit or GPU) there might, in addition to the memory managed by the CPU, be
@@ -79,7 +79,7 @@
 in software and hardware. </p>
 <fig id="GUID-2717F861-0045-5598-A3EC-7CF678BEFA70">
 <title>           Hardware rendered graphics - the wrong way!          </title>
-<image href="GUID-EADC4EA6-4492-5A00-A29E-6F7747FCAAC9_d0e184763_href.png" placement="inline"/>
+<image href="GUID-EADC4EA6-4492-5A00-A29E-6F7747FCAAC9_d0e189760_href.png" placement="inline"/>
 </fig>
 <p>The diagram, however, represents a system with several problem areas that
 would render it unsuitable for any practical implementation </p>
@@ -116,7 +116,7 @@
 display. The diagram below illustrates how Window Server-rendered UI content
 and external surfaces are composited using the UI surface. </p> <fig id="GUID-3448FD6B-9A39-58CD-8819-39B0B6CC4E13">
 <title>              Hardware composition and the Flattened UI            </title>
-<image href="GUID-B0797210-4EE3-557B-A5A6-D215D030BA0E_d0e184810_href.png" placement="inline"/>
+<image href="GUID-B0797210-4EE3-557B-A5A6-D215D030BA0E_d0e189807_href.png" placement="inline"/>
 </fig> <p>Although this method of composition is flexible and powerful, it
 does have some limitations, particularly with respect to semi-transparent
 hardware-accelerated surfaces. </p> <p>It is not possible, for example, to
@@ -128,18 +128,18 @@
 green layer displays a hardware rendered surface so it is actually behind
 the layer on which it appears. </p> <fig id="GUID-1FB1194D-FCAE-534C-94DC-AF4CF00E3A1C">
 <title>              The UI surface            </title>
-<image href="GUID-79009102-0490-5C61-9722-C5EE49A1AF2B_d0e184827_href.png" placement="inline"/>
+<image href="GUID-79009102-0490-5C61-9722-C5EE49A1AF2B_d0e189824_href.png" placement="inline"/>
 </fig> </section>
 <section id="GUID-41E9CA54-759F-5651-95F8-9F39808BE740"><title>Composition
 Examples</title> <p>This illustrations below illustrate the use of hardware
 accelerated surfaces and the UI surface </p> <fig id="GUID-8178DBA8-E10C-56F3-A828-80746CE6A993">
 <title>              Video rendered to a hardware accelerated surface mapped
 to a layer              behind the UI surface            </title>
-<image href="GUID-FE3C8D39-CE17-5AC7-AB6A-4D6664D52196_d0e184843_href.png" placement="inline"/>
+<image href="GUID-FE3C8D39-CE17-5AC7-AB6A-4D6664D52196_d0e189840_href.png" placement="inline"/>
 </fig> <fig id="GUID-51411B10-6DC3-5B74-BCEF-11EC1D0FBCA8">
 <title>              As above with a semi-transparent dialog on the UI surface
            </title>
-<image href="GUID-4616CCC9-7BD3-5D91-873A-6027167329ED_d0e184851_href.png" placement="inline"/>
+<image href="GUID-4616CCC9-7BD3-5D91-873A-6027167329ED_d0e189848_href.png" placement="inline"/>
 </fig> </section>
 </conbody><related-links>
 <link href="GUID-D93978BE-11A3-5CE3-B110-1DEAA5AD566C.dita"><linktext>The ScreenPlay