From 256cebc964cd8e7a4a9ee86a56a16d0e613e92a6 Mon Sep 17 00:00:00 2001
From: martin <martin@web>
Date: Mon, 5 May 2014 15:31:48 +0000
Subject: [PATCH]

---
 .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn
index 9255749f51..5ede475d2c 100644
--- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn
+++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn
@@ -1,4 +1,4 @@
-The Date resolution for FAT is only 2 seconds for the "last modified time."
+The Date resolution of the FAT filesystem is only 2 seconds for the "last modified time."
 This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of
 the files are modified.  (after remount the times appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem...