Symbian3/PDK/Source/GUID-EBF025DB-1552-5E99-8C07-09932DB60552.dita
changeset 5 f345bda72bc4
parent 1 25a17d01db0c
child 9 59758314f811
--- a/Symbian3/PDK/Source/GUID-EBF025DB-1552-5E99-8C07-09932DB60552.dita	Tue Mar 30 11:42:04 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-EBF025DB-1552-5E99-8C07-09932DB60552.dita	Tue Mar 30 11:56:28 2010 +0100
@@ -11,7 +11,7 @@
   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
 <concept id="GUID-EBF025DB-1552-5E99-8C07-09932DB60552" xml:lang="en"><title>Physical
 Channel Implementation</title><shortdesc>A media driver must implement a physical channel class derived
-from the <apiname>DMediaDriver</apiname> base class. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+from the <codeph>DMediaDriver</codeph> base class. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
 <p/>
 <p>This includes those drivers associated with fixed media, such as the internal
 drive, or removable media, such as a PC Card or MultiMediaCard. </p>
@@ -503,7 +503,7 @@
 true. </p> <p>Consider the following case. A request has been made to read
 1024 bytes from a media device that has a block size of 512 bytes. The 1024
 bytes start at offset +256 on the media device. </p> <fig id="GUID-30EA5683-9B12-59D6-88EF-21F4E84988B3">
-<image href="GUID-12CD8E91-4102-5253-A7DE-E5436028764F_d0e396579_href.png" placement="inline"/>
+<image href="GUID-12CD8E91-4102-5253-A7DE-E5436028764F_d0e418369_href.png" placement="inline"/>
 </fig> <p>To get the first 256 bytes, you must read the first block of 512
 bytes from the media device. This can corrupt the physical memory passed in
 the I/O request. The solution is to read the first block from the media device