--- a/Symbian3/SDK/Source/GUID-DEF3B8B3-5BD7-505B-93F9-A20CE00FFAE6.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-DEF3B8B3-5BD7-505B-93F9-A20CE00FFAE6.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -62,7 +62,7 @@
 <li id="GUID-F06D0F56-40AA-5631-9686-BA955E8E263B"><p> <xref href="GUID-DEF3B8B3-5BD7-505B-93F9-A20CE00FFAE6.dita#GUID-DEF3B8B3-5BD7-505B-93F9-A20CE00FFAE6/GUID-AA3990F3-52AB-5B14-8ED4-50CCA824AF84">Preventing deadlock</xref>. </p> </li>
 </ul> <p>The diagram below shows how plugins fit into the File Server software
 stack. </p> <fig id="GUID-EF5AECEC-9CB0-54B0-B6D2-46266B5FF49E">
-<image href="GUID-9A4543B3-2A79-5604-AE11-5087507C6755_d0e262222_href.png" placement="inline"/>
+<image href="GUID-9A4543B3-2A79-5604-AE11-5087507C6755_d0e267086_href.png" placement="inline"/>
 </fig> <p> <b>Note</b>: more than one plugin can be loaded into the file server
 at the same time. A plugin is not aware of other plugins. </p> <p id="GUID-3D91570E-8939-557B-8E1E-3A3C5BD27A26"><b> Threads and execution context</b> </p> <p>The
 Symbian platform File Server has multiple threads. There is a thread for each
@@ -94,7 +94,7 @@
 the plugins are not re-entrant safe this can lead to deadlock in the file
 server. </p> <fig id="GUID-01A69E82-BF01-520A-A8C5-927F1ED85E04">
 <title>                 File server deadlock               </title>
-<image href="GUID-9CC5E096-74FB-59AB-BAB9-A5486B961B7D_d0e262298_href.png" placement="inline"/>
+<image href="GUID-9CC5E096-74FB-59AB-BAB9-A5486B961B7D_d0e267162_href.png" placement="inline"/>
 </fig> <p>The framework introduced in v9.5 prevents deadlock by allowing plugins
 to issue internal file server requests after intercepting a request by using
 the newly introduced <xref href="GUID-3C50CF63-9AF4-3F36-8B8F-3FBB613E1CAC.dita"><apiname>RFilePlugin</apiname></xref>, <xref href="GUID-2E871434-D08F-3275-AC55-260A9A78661A.dita"><apiname>RDirPlugin</apiname></xref> and <xref href="GUID-DE8D8017-6E9C-38CE-A023-98A53CDF7152.dita"><apiname>RFsPlugin</apiname></xref> APIs
@@ -104,7 +104,7 @@
 for a typical plugin intercepting a file read request is illustrated below: </p> <fig id="GUID-E366027F-3112-520F-A118-4C048102749E">
 <title>                 Read request intercepted by a plugin             
  </title>
-<image href="GUID-2ABCF233-7DCC-59E2-B075-81E148A1D2AB_d0e262336_href.png" placement="inline"/>
+<image href="GUID-2ABCF233-7DCC-59E2-B075-81E148A1D2AB_d0e267200_href.png" placement="inline"/>
 </fig> <p>The classes <xref href="GUID-3C50CF63-9AF4-3F36-8B8F-3FBB613E1CAC.dita"><apiname>RFilePlugin</apiname></xref>, <xref href="GUID-2E871434-D08F-3275-AC55-260A9A78661A.dita"><apiname>RDirPlugin</apiname></xref> and <xref href="GUID-DE8D8017-6E9C-38CE-A023-98A53CDF7152.dita"><apiname>RFsPlugin</apiname></xref> have
 been introduced to facilitate plugins with direct access behaviour on file
 and directory requests. These classes are analogous to the client-side <xref href="GUID-BE0804F6-4375-3C8A-8C83-968F510466E0.dita"><apiname>RFile</apiname></xref>, <xref href="GUID-12AE154F-7741-38C0-ADFE-9784FCF5E516.dita"><apiname>RDir</apiname></xref> and <xref href="GUID-E263C747-946F-35AA-9F1D-41833BD350FC.dita"><apiname>RFs</apiname></xref> classes and have functions with similar or identical signitures. </p> <p>In
@@ -184,7 +184,7 @@
 first plugin to be able to intercept requests. </p> <fig id="GUID-41EB2F58-407F-52C7-A40C-0E3858CF718B">
 <title>                 Plugin stack showing absolute positions          
     </title>
-<image href="GUID-64BDD1DA-6B93-5F45-8CBD-7DBAF92CC4C7_d0e262462_href.png" placement="inline"/>
+<image href="GUID-64BDD1DA-6B93-5F45-8CBD-7DBAF92CC4C7_d0e267326_href.png" placement="inline"/>
 </fig> <p>The absolute position method is more appropriate for mounting plugins
 that operate regardless of their position in the plugin stack or when all
 of the plugins for a device are known and installed when manufactured. This