From 621eb630292fd9ee012c0a564c14963f65791827 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Thu, 3 Nov 2016 12:42:28 -0700 Subject: [PATCH] doc: minor fix in winfsp-testing.adoc --- doc/winfsp-testing.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/winfsp-testing.adoc b/doc/winfsp-testing.adoc index 905d4018..1300b544 100644 --- a/doc/winfsp-testing.adoc +++ b/doc/winfsp-testing.adoc @@ -26,7 +26,7 @@ These 3 test suites and a few smaller tests are run through Continuous Integrati === Test File System -WinFsp includes a test user mode file system called *MEMFS*. This is a simple in memory file system written in C/C\++. *MEMFS* attempts to achieve parity with NTFS (barring a few WinFsp limitations -- notably no support for hard links). MEMFS also performs some user mode file system checks during testing, for example, it checks that the buffer received during WRITE calls is read-only. +WinFsp includes a test user mode file system called *MEMFS*. This is a simple in memory file system written in C/C++. *MEMFS* attempts to achieve parity with NTFS (barring a few WinFsp limitations -- notably no support for hard links). MEMFS also performs some user mode file system checks during testing, for example, it checks that the buffer received during WRITE calls is read-only. == Range of Tests