X-Git-Url: https://git.p6c8.net/dumbdbm.git/blobdiff_plain/9037d1f22ac7e87aa1262728cb257ba14c571462..refs/heads/master:/README.md

diff --git a/README.md b/README.md
index d98fb99..ead5bb3 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# `DumbDBM_File` --- Portable DBM implementation
+# `DumbDBM_File` – Portable DBM implementation
 
 With `dumbdbm` / `dbm.dumb` the Python programming language provides a very simple DBM style database (i.e. a key-value database) written entirely in Python, requiring no external library. Being slow and some kind of *dumb*, it is intended as a last resort fallback if no other (more robust) database modules like GDBM, NDBM or Berkeley DB are available.
 
@@ -93,7 +93,7 @@ The value is inserted into a block. If the value is too big, more than one block
 
 When a value is modified and the new value fits in the old set of blocks, the old ones are used. Otherwise, a new set of blocks is placed at the end of the file.
 
-Currently, when a value is removed from the database, only it's entry in the index file is removed, meaning that it is still in the database. This also means, that it will become unaccessible and rendering the corresponding blocks lost. A similar thing happens when a value is moved to different blocks: The index file points to the value in the new blocks, but the old blocks remain unaccessible in the database file.
+Currently, when a value is removed from the database, only its entry in the index file is removed, meaning that it is still in the database. This also means, that it will become unaccessible and the corresponding blocks will become useless. A similar thing happens when a value is moved to different blocks: The index file points to the value in the new blocks, but the old blocks remain unaccessible in the database file.
 
 ## License