diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-E7DD9CFD-F477-5D25-BC10-BEBFB1022F7E.dita
--- a/Symbian3/PDK/Source/GUID-E7DD9CFD-F477-5D25-BC10-BEBFB1022F7E.dita	Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-E7DD9CFD-F477-5D25-BC10-BEBFB1022F7E.dita	Fri Aug 13 16:47:46 2010 +0100
@@ -63,7 +63,7 @@
 a network initiated location request. </p> <fig id="GUID-BEDFACD2-D262-500C-ACF5-37679F7FA091">
 <title>              Figure 1: SUPL Push API and Symbian plug-ins        
    </title>
-<image href="GUID-398483AD-C341-5777-AD23-381A067F9180_d0e460040_href.png" placement="inline"/>
+<image href="GUID-398483AD-C341-5777-AD23-381A067F9180_d0e457872_href.png" placement="inline"/>
 </fig> <p><b>SUPL
 WAP Push plug-in</b> </p> <p>The Symbian platform includes the WAP Push Framework
 to process WAP Push messages. If the Symbian SUPL WAP Push plug-in is installed,
@@ -104,7 +104,7 @@
 (if required). </p> <fig id="GUID-47957CAE-DC5F-55C9-B157-6274D00B0990">
 <title>                 Figure 2: Class diagram of SUPL Push API sender classes
               </title>
-<image href="GUID-0A24FF35-5A61-5305-812B-632F20F0395D_d0e460144_href.png" placement="inline"/>
+<image href="GUID-0A24FF35-5A61-5305-812B-632F20F0395D_d0e457976_href.png" placement="inline"/>
 </fig> <table id="GUID-01E93B41-A2AB-5251-947D-E4839A0AC71D">
 <tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/>
 <thead>
@@ -178,7 +178,7 @@
 are used by the Symbian reference SUPL Protocol Module. </p> <fig id="GUID-62800587-837F-5EC0-872C-AA505491E3E0">
 <title>                 Figure 3: Class diagram of SUPL Push API receiver
 classes               </title>
-<image href="GUID-120CA508-9984-54D0-B366-6D10D646FD49_d0e460374_href.png" placement="inline"/>
+<image href="GUID-120CA508-9984-54D0-B366-6D10D646FD49_d0e458206_href.png" placement="inline"/>
 </fig> <table id="GUID-1D1A1ED6-1BEC-575C-98B4-1B93F6F5D1DD">
 <tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/>
 <thead>
@@ -224,7 +224,7 @@
 the <codeph>SUPL           INIT</codeph> message is received, but this does
 not guarantee that the network initiated location request will complete successfully. </p> <fig id="GUID-AF4F52FA-F4CC-58E0-BD6F-5C74BC6B6ECD">
 <title>              Figure 4: SUPL Push API sequence diagram            </title>
-<image href="GUID-84623607-ACCA-5E57-9001-DA56E16C1652_d0e460570_href.png" placement="inline"/>
+<image href="GUID-84623607-ACCA-5E57-9001-DA56E16C1652_d0e458402_href.png" placement="inline"/>
 </fig> </section>
 <section id="GUID-202D83AC-6C99-5481-8074-ACFEBD426AE3"><title>References</title> <p>[1] <xref href="http://www.openmobilealliance.org" scope="external">Open Mobile Alliance</xref> Secure
 User Plane Location (SUPL) Architecture OMA-AD-SUPL-V1_0-20070615-A </p> </section>