X-Git-Url: http://cloudbase.mooo.com/gitweb/z180-stamp.git/blobdiff_plain/7b78a5a287827db9e9b16286f3604aef69b37c5c..refs/tags/fatfs-0.12b:/fatfs/doc/en/dstat.html?ds=sidebyside
diff --git a/fatfs/doc/en/dstat.html b/fatfs/doc/en/dstat.html
index c8204cc..0751460 100644
--- a/fatfs/doc/en/dstat.html
+++ b/fatfs/doc/en/dstat.html
@@ -35,11 +35,11 @@ DSTATUS disk_status (
The current drive status is returned in combination of status flags described below. FatFs refers only STA_NOINIT and STA_PROTECT.
- STA_NOINIT
-- Indicates that the device is not initialized. This flag is set on system reset, media removal or failure of disk_initialize() function. It is cleared on disk_initialize() function succeeded. Media change that occurs asynchronously must be captured and reflect it to the status flags, or auto-mount feature will not work correctly. If the system does not support media change detect feature, application program needs to force de-initialize the file system object with f_mount() function after the media change.
+- Indicates that the device is not initialized and not ready to work. This flag is set on system reset, media removal or failure of disk_initialize function. It is cleared on disk_initialize 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 force de-initialize the file system object and re-mount the volume with f_mount function after each media change.
- STA_NODISK
-- Indicates that no medium in the drive. This is always cleared on fixed disk drive. Note that FatFs does not refer this flag.
+- Indicates that no medium in the drive. This is always cleared at fixed disk drive. Note that FatFs does not refer this flag.
- STA_PROTECT
-- Indicates that the medium is write protected. This is always cleared on the drives without write protect feature. Not valid if no medium in the drive.
+- Indicates that the medium is write protected. This is always cleared at the drives without write protect function. Not valid if no medium in the drive.