From f5a2f4443a925ab5f76c1616ea8e5c299af1f1af Mon Sep 17 00:00:00 2001
From: Roy Hashimoto <156154+rhashimoto@users.noreply.github.com>
Date: Wed, 5 Jun 2024 07:45:42 -0700
Subject: [PATCH] Update README.md

---
 src/examples/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/examples/README.md b/src/examples/README.md
index 1eeea07..c7e7b99 100644
--- a/src/examples/README.md
+++ b/src/examples/README.md
@@ -5,7 +5,7 @@ production is not prohibited but that isn't their primary purpose.
 
 ## VFS examples
 ### MemoryVFS and MemoryAsyncVFS
-These implementations store database pages in memory. The default SQLite VFS already does that, so their value is mainly to provide minimal working examples for writing a VFS. First-time VFS implementers should probably start by looking at these classes, as well as the [SQLite VFS documentation](https://www.sqlite.org/vfs.html).
+These implementations store database pages in memory. The default SQLite VFS already does that, so their value is mainly to provide minimal working examples for writing a VFS or to help debugging investigations by providing a comparative baseline for behavior and/or performance. First-time VFS implementers should probably start by looking at these classes, as well as the [SQLite VFS documentation](https://www.sqlite.org/vfs.html).
 
 ### IDBBatchAtomicVFS
 This VFS stores database pages in IndexedDB. IndexedDB works on all contexts - Window, Worker, SharedWorker, service worker, extension - which makes IDBBatchAtomicVFS a good general purpose VFS.