aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorRuss Ferriday <russf@topia.com>2014-12-04 22:23:20 +0000
committerRuss Ferriday <russf@topia.com>2014-12-04 22:23:20 +0000
commit2a13d5ca834c3632cf305cd8a45ba8e21e8688a8 (patch)
treef8b68036dfaf637b37988a527cf1fbe920fdb96f /README.md
parentREADME (diff)
downloaddedo-2a13d5ca834c3632cf305cd8a45ba8e21e8688a8.tar.gz
dedo-2a13d5ca834c3632cf305cd8a45ba8e21e8688a8.tar.xz
grammar & typo
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 9bb08f7..ff5e5e3 100644
--- a/README.md
+++ b/README.md
@@ -395,7 +395,7 @@ application but limits multi-process access to the data.
### LevelDB, RocksDB
-LevelDB and it's derivatives (RocksDB, HyperLevelDB) are similar to Bolt in that
+LevelDB and its derivatives (RocksDB, HyperLevelDB) are similar to Bolt in that
they are libraries bundled into the application, however, their underlying
structure is a log-structured merge-tree (LSM tree). An LSM tree optimizes
random writes by using a write ahead log and multi-tiered, sorted files called
@@ -415,7 +415,7 @@ Bolt supports fully serializable ACID transactions.
### LMDB
Bolt was originally a port of LMDB so it is architecturally similar. Both use
-a B+tree, have ACID semanetics with fully serializable transactions, and support
+a B+tree, have ACID semantics with fully serializable transactions, and support
lock-free MVCC using a single writer and multiple readers.
The two projects have somewhat diverged. LMDB heavily focuses on raw performance