--- a/Symbian3/SDK/Source/GUID-57A909F3-EAEA-5FE2-B620-E21204794497.dita	Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-57A909F3-EAEA-5FE2-B620-E21204794497.dita	Thu Mar 11 15:24:26 2010 +0000
@@ -13,22 +13,20 @@
 to Load the Physical Device Driver and Logical Device Driver: Tutorial</title><shortdesc>When testing using the console, all drivers need to be loaded directly.
 This tutorial describes how to load the drivers required for the Serial Communications
 Server. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
-<context><p>Testing of communications software can be done using the Symbian
-OS console shell interface rather than a GUI interface. The console shell
-interface has advantages when testing since the console allows software to
-be tested in isolation. When testing with a GUI interface the testing can
-be difficult if other software in the GUI is attempting to access resources.
-If the device or the emulator is started with just the console, then only
-the kernel and file system are running. The tester can then load the software
-required for the test and ensure that no other software is using any resources.
-This avoids problems of other software interrupting the CPU or using and releasing
-memory or other hardware while a test is running. </p><p>Any test applications
-that have not been launched by the GUI should
- explicitly load the correct physical and logical device drivers. In most
-cases the bootloader will load the physical device driver. It is safe to load
-a
-device driver which has already been loaded, since the API will return
-<xref href="GUID-D1D25122-F2B8-3C78-8599-84905BFD47B8.dita"><apiname>KErrAlreadyExists</apiname></xref></p> </context>
+<context id="GUID-3FD29C37-082A-4B68-A955-E4B0D625BA92"><p>Testing of communications software can be done using the Symbian platform
+console shell interface rather than a GUI interface. The console shell interface
+has advantages when testing since the console allows software to be tested
+in isolation. When testing with a GUI interface the testing can be difficult
+if other software in the GUI is attempting to access resources. If the device
+or the emulator is started with just the console, then only the kernel and
+file system are running. The tester can then load the software required for
+the test and ensure that no other software is using any resources. This avoids
+problems of other software interrupting the CPU or using and releasing memory
+or other hardware while a test is running. </p><p>Any test applications that
+have not been launched by the GUI should  explicitly load the correct physical
+and logical device drivers. In most cases the bootloader will load the physical
+device driver. It is safe to load a device driver which has already been loaded,
+since the API will return <xref href="GUID-D1D25122-F2B8-3C78-8599-84905BFD47B8.dita"><apiname>KErrAlreadyExists</apiname></xref></p> </context>
 <steps id="GUID-8D0D239F-51F9-512A-8405-ADD01AE1660B">
 <step id="GUID-21876E62-D2A9-510A-BAD2-CB3E4271A02B"><cmd>Identify the names
 of the physical and logical device drivers required.</cmd>