diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-39A995DC-F047-4B41-A60D-27063CE329BE.dita
--- a/Symbian3/SDK/Source/GUID-39A995DC-F047-4B41-A60D-27063CE329BE.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-39A995DC-F047-4B41-A60D-27063CE329BE.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -38,7 +38,7 @@
 steps until the necessary level of protection is achieved.</p></li>
 </ol>
 <p/>
-<fig id="GUID-A41ADA16-6D0B-4EA4-BBF2-67C2CFED68F3"><title>Security development process</title><image href="GUID-316D7B85-F827-4479-B5EE-81F210614236_d0e11518_href.png"/></fig>
+<fig id="GUID-A41ADA16-6D0B-4EA4-BBF2-67C2CFED68F3"><title>Security development process</title><image href="GUID-316D7B85-F827-4479-B5EE-81F210614236_d0e11621_href.png"/></fig>
 <p>The security development process is guided by <i>cost</i>, <i>efficiency,</i> and <i>usability</i>.
 If security is too tight, this may be expensive and affect both performance
 and the user's experience of the system or software. On the other hand, if