1 files changed, 4 insertions, 4 deletions
diff --git a/fatfs/documents/doc/dwrite.html b/fatfs/documents/doc/dwrite.html
index 51174f9..fef5106 100644
--- a/fatfs/documents/doc/dwrite.html
+++ b/fatfs/documents/doc/dwrite.html
@@ -13,12 +13,12 @@
 
 <div class="para func">
 <h2>disk_write</h2>
-<p>The disk_write function is called to write data to the sector(s) of storage device.</p>
+<p>The disk_write function is called to write data to the storage device.</p>
 <pre>
 DRESULT disk_write (
   BYTE <span class="arg">pdrv</span>,        <span class="c">/* [IN] Physical drive number */</span>
   const BYTE* <span class="arg">buff</span>, <span class="c">/* [IN] Pointer to the data to be written */</span>
-  DWORD <span class="arg">sector</span>,     <span class="c">/* [IN] Sector number to write from */</span>
+  LBA_t <span class="arg">sector</span>,     <span class="c">/* [IN] Sector number to write from */</span>
   UINT <span class="arg">count</span>        <span class="c">/* [IN] Number of sectors to write */</span>
 );
 </pre>
@@ -32,7 +32,7 @@ DRESULT disk_write (
 <dt>buff</dt>
 <dd>Pointer to the first item of the <em>byte array</em> to be written. The size of data to be written is sector size * <tt class="arg">count</tt> bytes.</dd>
 <dt>sector</dt>
-<dd>Start sector number in 32-bit LBA.</dd>
+<dd>Start sector number in LBA. The data type <tt>LBA_t</tt> is an alias of <tt>DWORD</tt> or <tt>QWORD</tt> depends on the configuration option.</dd>
 <dt>count</dt>
 <dd>Number of sectors to write.</dd>
 </dl>
@@ -60,7 +60,7 @@ DRESULT disk_write (
 <h4>Description</h4>
 <p>The specified memory address is not that always aligned to word boundary because the argument is defined as <tt>BYTE*</tt>. For more information, refer to the description of <a href="dread.html"><tt>disk_read</tt></a> function.</p>
 <p>Generally, a multiple sector write request (<tt class="arg">count</tt><tt> &gt; 1</tt>) must not be split into single sector transactions to the storage device, or the file write throughput will be drastically decreased.</p>
-<p>FatFs expects delayed write function of the disk control layer. The write operation to the media does not need to be completed at return from this function by what write operation is in progress or data is only stored into the write-back cache. But write data on the <tt class="arg">buff</tt> is invalid after return from this function. The write completion request is done by <tt>CTRL_SYNC</tt> command of <tt><a href="dioctl.html">disk_ioctl</a></tt> function. Therefore, if a delayed write function is implemented, the write throughput of the filesystem will be improved.</p>
+<p>FatFs expects delayed write function of the disk control layer. The write operation to the media does not need to be completed when return from this function by what write operation is in progress or data is only stored into the write-back cache. But write data on the <tt class="arg">buff</tt> is invalid after return from this function. The write completion request is done by <tt>CTRL_SYNC</tt> command of <tt><a href="dioctl.html">disk_ioctl</a></tt> function. Therefore, if a delayed write function is implemented, the write throughput of the filesystem will be improved.</p>
 <p><em>Remarks: Application program MUST NOT call this function, or FAT structure on the volume can be collapsed.</em></p>
 </div>