Skip to content
Browse files

fix typo

  • Loading branch information...
1 parent 320bbe9 commit d0465017af5139a6345941a86fcc859e6562d6c7 quiver committed
Showing with 4 additions and 4 deletions.
  1. +1 −1 topics/data-types-intro.md
  2. +1 −1 topics/debugging.md
  3. +1 −1 topics/faq.md
  4. +1 −1 topics/persistence.md
View
2 topics/data-types-intro.md
@@ -323,7 +323,7 @@ fortunately, and this is the sane version:
returned 123456).
* Finally associate this new ID to our tag with *SETNX
tag:b840fc02d524045429941cc15f59e41cb7be6c52:id 123456*. By using SETNX if a
- different client was faster than this one the key wil not be setted. Not
+ different client was faster than this one the key will not be setted. Not
only, SETNX returns 1 if the key is set, 0 otherwise. So... let's add a final
step to our computation.
* If SETNX returned 1 (We set the key) return 123456 to the caller, it's our
View
2 topics/debugging.md
@@ -78,7 +78,7 @@ In the above example the process ID is **58414**.
For example: gdb /usr/local/bin/redis-server 58414
-GDB will start and will attach to the running server printing something like the followig:
+GDB will start and will attach to the running server printing something like the following:
Reading symbols for shared libraries + done
0x00007fff8d4797e6 in epoll_wait ()
View
2 topics/faq.md
@@ -20,7 +20,7 @@ To give you an example: 1 Million keys with the key being the natural numbers fr
something like 16MB, this is expected because with small keys and values there
is a lot of overhead. Memcached will perform similarly, but a bit better as
Redis has more overhead (type information, refcount and so forth) to represent
-differnet kinds of objects.
+different kinds of objects.
With large keys/values the ratio is much better of course.
View
2 topics/persistence.md
@@ -228,7 +228,7 @@ from doing heavy disk I/O at the same time.
When snapshotting is in progress and the user explicitly requests a log
rewrite operation using BGREWRITEAOF the server will reply with an OK
-status code telling the user the operation is scheduled, and the rewirte
+status code telling the user the operation is scheduled, and the rewrite
will start once the snapshotting is completed.
In the case both AOF and RDB persistence are enabled and Redis restarts the

0 comments on commit d046501

Please sign in to comment.
Something went wrong with that request. Please try again.