--- a/Symbian3/SDK/Source/GUID-0A13A931-016C-5325-97AF-2DE0B210DF2F.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-0A13A931-016C-5325-97AF-2DE0B210DF2F.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -53,7 +53,7 @@
 <title>              Window Server            </title>
 <desc><p>The Window Server controls access by many client applications,
 to the machine’s screen, keyboard and pointer. </p> </desc>
-<image href="GUID-FE4BBEB4-4E5A-5BF2-A72F-AF53BAD83518_d0e187538_href.png" placement="inline"/>
+<image href="GUID-FE4BBEB4-4E5A-5BF2-A72F-AF53BAD83518_d0e192526_href.png" placement="inline"/>
 </fig> <p>The Window Server thread runs at a higher priority than
 any application; only the kernel runs at a higher priority. Therefore,
 all applications' requests for screen updates, and all handling of
@@ -79,7 +79,7 @@
 we provide a summary of the key concepts. </p> <fig id="GUID-A84A2706-1AF0-598B-976E-0980AD69E6E7">
 <title>             Window Server client-side API classes        
    </title>
-<image href="GUID-FEFF353E-DE8A-5FBA-B696-CD01D06BE813_d0e187563_href.png" placement="inline"/>
+<image href="GUID-FEFF353E-DE8A-5FBA-B696-CD01D06BE813_d0e192551_href.png" placement="inline"/>
 </fig> <table id="GUID-37EDAB58-6F7B-526A-8E46-891598924120">
 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
 <thead>
@@ -178,18 +178,12 @@
 the Window Server and write to the screen directly. This avoids client-server
 communication and as a result is faster. However, some interaction
 with the Window Server is needed to prevent the application from drawing
-over other application's data. </p> <p>In ScreenPlay, Symbian recommends
-the use of <xref href="GUID-1C025957-258C-54C0-94A5-AD60C14E6D76.dita">external surfaces</xref> in preference to DSA. However, support for
-DSA is maintained for backward compatibility reasons, although there
-are some subtle changes in the support offered.</p><p>ScreenPlay does
-not support the mixing of <xref href="GUID-0AEE5955-C530-35F1-A904-69183331B294.dita"><apiname>CWindowGc</apiname></xref> and DSA rendering
-to the same window. When DSA rendering is present, any <codeph>CWindowGc</codeph> rendering to the same window is ignored. For example, an application
-that uses <codeph>CWindowGC</codeph> rendering in one part of a window
-and DSA rendering in another part will not work as expected in a ScreenPlay
-environment. Similarly, <codeph>CWindowGc</codeph> rendering can no
-longer be used to seed the DSA content as it could previously. However, <codeph>CWindowGc</codeph> rendering can be provided but it is not rendered
-until the DSA rendering finishes. It is therefore best to avoid mixing
-the rendering types in the same window.</p> </entry>
+over other application's data. </p> <p>On ScreenPlay, support for
+direct screen access (DSA) is maintained for backward compatibility
+reasons, although Symbian recommends the use of <xref href="GUID-1C025957-258C-54C0-94A5-AD60C14E6D76.dita">external surfaces</xref> in preference to DSA. However, whereas on some earlier devices,
+applications might work without fully conforming to the rules of DSA,
+these rules are now necessarily enforced. See <xref href="GUID-3F0FCBB5-98D2-4355-96E3-2DA938DE1C16.dita">DSA Migration Guide</xref> for information about the guidelines applications must follow in
+order to be able to run correctly on a ScreenPlay device.</p> </entry>
 </row>
 </tbody>
 </tgroup>