--- a/Symbian3/SDK/Source/GUID-B7A40638-BA80-5175-B23D-2F3964C274A0.dita Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-B7A40638-BA80-5175-B23D-2F3964C274A0.dita Tue Jul 20 12:00:49 2010 +0100
@@ -50,7 +50,7 @@
as the <i>Transport</i>. </p> <fig id="GUID-5467DE40-01FB-5D50-BB6D-866D5C425ADA">
<title> Separation of Data Flows and Control in the Comms Architecture
</title>
-<image href="GUID-69847989-624F-5119-8AC0-3D95D72AF076_d0e76088_href.png" placement="inline"/>
+<image href="GUID-69847989-624F-5119-8AC0-3D95D72AF076_d0e76050_href.png" placement="inline"/>
</fig> <p>In fact the Comms Architecture actually divides the area marked
Control above into two areas, <i>Control</i> and <i>Management</i>. This is
the reason that this Comms Architecture is also known as the <i>Three-Plane
@@ -77,7 +77,7 @@
the same protocols. </title>
<desc><p>In this example IP and TCP are used in three different stacks. A
combination of these Stacks could be running concurrently. </p> </desc>
-<image href="GUID-FBBC7F0D-FD4B-58B7-BEAC-B68EEBD19ACF_d0e76136_href.png" placement="inline"/>
+<image href="GUID-FBBC7F0D-FD4B-58B7-BEAC-B68EEBD19ACF_d0e76098_href.png" placement="inline"/>
</fig> <p>Each stack requires a configuration that details how these protocols
find and work with each other; the protocols themselves need to know how to
talk with the other protocols. To allow flexibility, each protocol must avoid
@@ -97,7 +97,7 @@
<title> The Comms Architecture shown in the scope of a complete
protocol stack and the end-to-end path between the applications
on each device. </title>
-<image href="GUID-26399981-1E45-5578-851E-D234295F3B05_d0e76153_href.png" placement="inline"/>
+<image href="GUID-26399981-1E45-5578-851E-D234295F3B05_d0e76115_href.png" placement="inline"/>
</fig> </section>
<section id="GUID-1BAC904D-F705-5416-A0F6-3D5FA3B10A7E"><title>Performance</title> <p>A
key requirement of the Comms Architecture is the performance of data transfer.