diff -r 5072524fcc79 -r 80ef3a206772 Symbian3/PDK/Source/GUID-91F95D0C-E4CF-510E-B280-E27F89274ACE.dita
--- a/Symbian3/PDK/Source/GUID-91F95D0C-E4CF-510E-B280-E27F89274ACE.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-91F95D0C-E4CF-510E-B280-E27F89274ACE.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -658,7 +658,7 @@
 In figure 1 both Client 1 and Client 2 receive status <codeph>KErrServerBusy</codeph>. </p> <fig id="GUID-DCD0CDE1-EA45-53D3-A2DE-F38786408881">
 <title>                      Figure 1. Processing of two SET initiated requests
 from                      different clients.                    </title>
-<image href="GUID-09EFBBDE-780D-5A16-8E3B-78DEFF1F8938_d0e453895_href.png" placement="inline"/>
+<image href="GUID-09EFBBDE-780D-5A16-8E3B-78DEFF1F8938_d0e459740_href.png" placement="inline"/>
 </fig> <p> <i>Making a location request after receiving KErrServerBusy</i>  </p> <p>A
 client that receives the error <codeph>KErrServerBusy</codeph> will usually
 want to make the request again to obtain a position update. </p> <p>In many