summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan-Erik Rediger <janerik@fnordig.de>2015-04-28 11:07:21 +0200
committerJan-Erik Rediger <janerik@fnordig.de>2015-04-28 11:07:21 +0200
commit3ff49afff1bf9b0d84d8ad53fb2d6b9b5d4b039c (patch)
tree724b0f553b965119029587cb0bf4e55238f8324f
parent1b25757f415d6e6da0cdf1769f94f8e318e5be25 (diff)
downloadredis-3ff49afff1bf9b0d84d8ad53fb2d6b9b5d4b039c.tar.gz
Fix spelling and grammatical errors in readme
Closes #2549
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index 0565418f6..8efc7faca 100644
--- a/README.md
+++ b/README.md
@@ -3,15 +3,15 @@ This README is just a fast *quick start* document. You can find more detailed do
What is Redis?
--------------
-Redis is often referred as a *data structures* server. What this means is that Redis provides access to mutable data structures via a set of commands, which are send using a *server-client* model with TCP sockets and a simple protocol. So different processes can query and modify the same data structures in a shared way.
+Redis is often referred as a *data structures* server. What this means is that Redis provides access to mutable data structures via a set of commands, which are sent using a *server-client* model with TCP sockets and a simple protocol. So different processes can query and modify the same data structures in a shared way.
Data structures implemented into Redis have a few special properties:
* Redis cares to store them on disk, even if they are always served and modified into the server memory. This means that Redis is fast, but that is also non-volatile.
* Implementation of data structures stress on memory efficiency, so data structures inside Redis will likely use less memory compared to the same data structure modeled using an high level programming language.
-* Redis offers a number of features that are natural to find into a database, like replication, tunable levels of durability, cluster, high availability.
+* Redis offers a number of features that are natural to find in a database, like replication, tunable levels of durability, cluster, high availability.
-Another good example is to think at Redis as a more complex version of memcached, where the opeations are not just SETs and GETs, but operations to work with complex data types like Lists, Sets, ordered data structures, and so forth.
+Another good example is to think at Redis as a more complex version of memcached, where the operations are not just SETs and GETs, but operations to work with complex data types like Lists, Sets, ordered data structures, and so forth.
If you want to know more, this is a list of selected starting points: