Some small grammatical changes (by @ShawnMilo)

Reapplied to the reformatted tree.

Fixes #119.

commands/bgsave.md

@@ -1,7 +1,7 @@
 Save the DB in background.
 The OK code is immediately returned.
-Redis forks, the parent continues to server the clients, the child saves the DB
-on disk then exit.
+Redis forks, the parent continues to serve the clients, the child saves the DB
+on disk then exits.
 A client my be able to check if the operation succeeded using the `LASTSAVE`
 command.
 

commands/blpop.md

@@ -6,7 +6,7 @@ given keys being checked in the order that they are given.
 
 ## Non-blocking behavior
 
-When `BLPOP` is called, if at least one of the specified keys contain a
+When `BLPOP` is called, if at least one of the specified keys contains a
 non-empty list, an element is popped from the head of the list and returned to
 the caller together with the `key` it was popped from.
 

commands/config get.md

@@ -6,7 +6,7 @@ can read the whole configuration of a server using this command.
 The symmetric command used to alter the configuration at run time is `CONFIG
 SET`.
 
-`CONFIG GET` takes a single argument, that is glob style pattern.
+`CONFIG GET` takes a single argument, which is a glob-style pattern.
 All the configuration parameters matching this parameter are reported as a list
 of key-value pairs.
 Example:
@@ -19,7 +19,7 @@ Example:
     5) "set-max-intset-entries"
     6) "512"
 
-You can obtain a list of all the supported configuration parameters typing
+You can obtain a list of all the supported configuration parameters by typing
 `CONFIG GET *` in an open `redis-cli` prompt.
 
 All the supported parameters have the same meaning of the equivalent
@@ -30,9 +30,9 @@ following important differences:
 
 * Where bytes or other quantities are specified, it is not possible to use
   the `redis.conf` abbreviated form (10k 2gb ... and so forth), everything
-  should be specified as a well formed 64 bit integer, in the base unit of the
+  should be specified as a well-formed 64-bit integer, in the base unit of the
   configuration directive.
-* The save parameter is a single string of space separated integers.
+* The save parameter is a single string of space-separated integers.
   Every pair of integers represent a seconds/modifications threshold.
 
 For instance what in `redis.conf` looks like:

commands/config set.md

@@ -8,8 +8,7 @@ issuing a `CONFIG GET *` command, that is the symmetrical command used to obtain
 information about the configuration of a running Redis instance.
 
 All the configuration parameters set using `CONFIG SET` are immediately loaded
-by Redis that will start acting as specified starting from the next command
-executed.
+by Redis and will take effect starting with the next command executed.
 
 All the supported parameters have the same meaning of the equivalent
 configuration parameter used in the [redis.conf][hgcarr22rc] file, with the
@@ -19,9 +18,9 @@ following important differences:
 
 * Where bytes or other quantities are specified, it is not possible to use
   the `redis.conf` abbreviated form (10k 2gb ... and so forth), everything
-  should be specified as a well formed 64 bit integer, in the base unit of the
+  should be specified as a well-formed 64-bit integer, in the base unit of the
   configuration directive.
-* The save parameter is a single string of space separated integers.
+* The save parameter is a single string of space-separated integers.
   Every pair of integers represent a seconds/modifications threshold.
 
 For instance what in `redis.conf` looks like:
@@ -33,16 +32,17 @@ that means, save after 900 seconds if there is at least 1 change to the dataset,
 and after 300 seconds if there are at least 10 changes to the datasets, should
 be set using `CONFIG SET` as "900 1 300 10".
 
-It is possible to switch persistence from RDB snapshotting to append only file
+It is possible to switch persistence from RDB snapshotting to append-only file
 (and the other way around) using the `CONFIG SET` command.
-For more information about how to do that please check [persistence page][tp].
+For more information about how to do that please check the [persistence
+page][tp].
 
 [tp]: /topics/persistence
 
 In general what you should know is that setting the `appendonly` parameter to
-`yes` will start a background process to save the initial append only file
+`yes` will start a background process to save the initial append-only file
 (obtained from the in memory data set), and will append all the subsequent
-commands on the append only file, thus obtaining exactly the same effect of a
+commands on the append-only file, thus obtaining exactly the same effect of a
 Redis server that started with AOF turned on since the start.
 
 You can have both the AOF enabled with RDB snapshotting if you want, the two

commands/dbsize.md

@@ -1,4 +1,4 @@
-Return the number of keys in the currently selected database.
+Return the number of keys in the currently-selected database.
 
 @return
 

commands/dump.md

@@ -6,7 +6,7 @@ command.
 The serialization format is opaque and non-standard, however it has a few
 semantical characteristics:
 
-* It contains a 64bit checksum that is used to make sure errors will be
+* It contains a 64-bit checksum that is used to make sure errors will be
   detected.
   The `RESTORE` command makes sure to check the checksum before synthesizing a
   key using the serialized value.