Import fatfs R0.15

[z180-stamp.git] / fatfs / documents / doc / dstat.html

diff --git a/fatfs/documents/doc/dstat.html b/fatfs/documents/doc/dstat.html
index e9926bb8ef8c74d7b061761c3719d9b2b1a1f662..a891489d020104bc6577084664e829c2a8ed759c 100644 (file)
--- a/fatfs/documents/doc/dstat.html
+++ b/fatfs/documents/doc/dstat.html
@@ -25,7 +25,7 @@ DSTATUS disk_status (
 <h4>Parameter</h4>\r
 <dl class="par">\r
 <dt>pdrv</dt>\r
-<dd>Physical drive number to identify the target device. Always zero at single drive system.</dd>\r
+<dd>Physical drive number to identify the target device. Always zero in single drive system.</dd>\r
 </dl>\r
 </div>\r
 \r
@@ -37,9 +37,9 @@ DSTATUS disk_status (
 <dt>STA_NOINIT</dt>\r
 <dd>Indicates that the device has not been initialized and not ready to work. This flag is set on system reset, media removal or failure of <a href="dinit.html"><tt>disk_initialize</tt></a> function. It is cleared on <tt>disk_initialize</tt> function succeeded. Any media change that occurs asynchronously must be captured and reflect it to the status flags, or auto-mount function will not work correctly. If the system does not support media change detection, application program needs to explicitly re-mount the volume with <tt>f_mount</tt> function after each media change.</dd>\r
 <dt>STA_NODISK</dt>\r
-<dd>Indicates that no medium in the drive. This is always cleared at fixed disk drive. Note that FatFs does not refer this flag.</dd>\r
+<dd>Indicates that no medium in the drive. This is always cleared when the drive is non-removable class. Note that FatFs does not refer this flag.</dd>\r
 <dt>STA_PROTECT</dt>\r
-<dd>Indicates that the medium is write protected. This is always cleared at the drives without write protect function. Not valid if <tt>STA_NODISK</tt> is set.</dd>\r
+<dd>Indicates that the medium is write protected. This is always cleared when the drive has no write protect function. Not valid if <tt>STA_NODISK</tt> is set.</dd>\r
 </dl>\r
 </div>\r
 \r