--- a/Symbian3/PDK/Source/GUID-D53A00E4-CF37-5F11-8D15-C5ECCCE64597.dita	Tue Mar 30 11:42:04 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-D53A00E4-CF37-5F11-8D15-C5ECCCE64597.dita	Tue Mar 30 11:56:28 2010 +0100
@@ -11,9 +11,9 @@
   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
 <concept id="GUID-D53A00E4-CF37-5F11-8D15-C5ECCCE64597" xml:lang="en"><title>Vibra
 API</title><abstract><shortdesc>Vibra API provides the functionality to control the device
-vibra, which is accessed using the <apiname>CHWRMVibra</apiname> instance.
-It also provides methods to retrieve the current settings of the vibration
-feature in the user profile and the current status of the vibra. It uses synchronous
+vibra, which is accessed using the <codeph>CHWRMVibra</codeph> instance. It
+also provides methods to retrieve the current settings of the vibration feature
+in the user profile and the current status of the vibra. It uses synchronous
 method calls which block the client application until a response is received
 from the plug-in. </shortdesc> <p>Vibra API also allows the client to request
 for tactile vibration feedback. </p> </abstract><prolog><metadata><keywords/></metadata></prolog><conbody>
@@ -59,19 +59,20 @@
 </tbody>
 </tgroup>
 </table>
-<section><title> Observer</title> <p>A separate callback interface <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>MHWRMVibraObserver</apiname></xref> for status reporting is also
+<section id="GUID-60F7705E-24A1-4A36-8842-A53A380957B2"><title> Observer</title> <p>A separate callback interface <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>MHWRMVibraObserver</apiname></xref> for status reporting is also
 used. The client creates an instance of <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>CHWRMVibra</apiname></xref> using <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>NewL()</apiname></xref>. If the client requires the status information,
 it must provide a callback pointer of the <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>MHWRMVibraObserver</apiname></xref> implementing
 class for the <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>NewL()</apiname></xref> method. </p> <fig id="GUID-95D74CC2-CEDD-569B-8B34-A47FDA4F8DE0">
 <title>              Vibra API Interfaces            </title>
-<image href="GUID-DC44DCFC-8549-5CDE-B6DA-F5FD73E2D9FC_d0e135754_href.jpg" placement="inline"/>
+<image href="GUID-DC44DCFC-8549-5CDE-B6DA-F5FD73E2D9FC_d0e160691_href.jpg" placement="inline"/>
 </fig> </section>
-<section><title>Tactile vibration feedback</title> <p>Tactile vibration is
+<section id="GUID-B20AA3A6-94BB-4723-90F2-73B5192C7C78"><title>Tactile vibration feedback</title> <p>Tactile vibration is
 used in many touch screen devices to provide vibration feedback to the user
 through display surface. </p> <p>The clients can specify the intensity and
 duration of the feedback pulse, and receive notifications when the tactile
 feedback settings changes in the user profile through <xref href="GUID-68D63D0A-4CC6-34A6-AF5B-BB59AC96625E.dita"><apiname>MHWRMVibraFeedbackObserver</apiname></xref> class. </p> <p> <b> Note</b>: The tactile feedback functionality is only available to the clients configured
-at the firmware build time (Symbian platform licensees). </p> <table id="GUID-D75949EB-BC44-4120-825B-8B905562777D"><title>Definitions</title>
+at the firmware build time (Symbian platform licensees). </p> <table id="GUID-D75949EB-BC44-4120-825B-8B905562777D">
+<title>Definitions</title>
 <tgroup cols="2"><colspec colname="COLSPEC0" colwidth="0.42*"/><colspec colname="COLSPEC1" colwidth="1.58*"/>
 <tbody>
 <row>