summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Baumann <abaumann@yahoo.com>2012-08-10 21:55:01 +0200
committerAndreas Baumann <abaumann@yahoo.com>2012-08-10 21:55:01 +0200
commit24138633222cac676d02c2e40b52569c32ec52d7 (patch)
treedda7af5eaa3c4699914a91007094d252b5e9eff6
parentab50a978f99ae94e54c3bcfa0d17c03123153c52 (diff)
downloadpgfuse-24138633222cac676d02c2e40b52569c32ec52d7.tar.gz
pgfuse-24138633222cac676d02c2e40b52569c32ec52d7.tar.bz2
speeling typo
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 3bcc1b2..b2c5be1 100644
--- a/README
+++ b/README
@@ -17,7 +17,7 @@ Yes, I know what happens if you store files in a database (in respect to
drop of efficiency and incremental backups for instance). :-)
Nevertheless, there are special situations, where a filesystem in a database
-is usefull. With FUSE this is also rather simple to write.
+is useful. With FUSE this is also rather simple to write.
The reason I wrote one was a project with lots of data on a ReiserFS (at
least in 2001, this was), which was more or less immutable and should be