X-Git-Url: http://cloudbase.mooo.com/gitweb/z180-stamp.git/blobdiff_plain/289f6a146c0b2087607d8d8659531ea90142779a..976db69ffa80c4d499e53f6f22c26d784fdac0a1:/fatfs/documents/doc/dstat.html

diff --git a/fatfs/documents/doc/dstat.html b/fatfs/documents/doc/dstat.html
index e9926bb..a891489 100644
--- a/fatfs/documents/doc/dstat.html
+++ b/fatfs/documents/doc/dstat.html
@@ -25,7 +25,7 @@ DSTATUS disk_status (
 <h4>Parameter</h4>
 <dl class="par">
 <dt>pdrv</dt>
-<dd>Physical drive number to identify the target device. Always zero at single drive system.</dd>
+<dd>Physical drive number to identify the target device. Always zero in single drive system.</dd>
 </dl>
 </div>
 
@@ -37,9 +37,9 @@ DSTATUS disk_status (
 <dt>STA_NOINIT</dt>
 <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>
 <dt>STA_NODISK</dt>
-<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>
+<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>
 <dt>STA_PROTECT</dt>
-<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>
+<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>
 </dl>
 </div>