diff options
author | Sébastien Fievet <_@sebastien-fievet.fr> | 2017-07-26 14:11:05 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-07-26 14:11:05 +0200 |
commit | 22bcee5178c68255d1ba7da908405161c4ffbdf5 (patch) | |
tree | 55589888aa879fb39cfee50c0daaf79c6e7c8988 /redis.conf | |
parent | dc997755bf8c2d69899957a8ab6dc41aed0c7ddb (diff) | |
download | redis-22bcee5178c68255d1ba7da908405161c4ffbdf5.tar.gz |
Fix some typos
Diffstat (limited to 'redis.conf')
-rw-r--r-- | redis.conf | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/redis.conf b/redis.conf index c54dba392..7afd35a47 100644 --- a/redis.conf +++ b/redis.conf @@ -606,7 +606,7 @@ slave-priority 100 # deletion of the object. It means that the server stops processing new commands # in order to reclaim all the memory associated with an object in a synchronous # way. If the key deleted is associated with a small object, the time needed -# in order to execute th DEL command is very small and comparable to most other +# in order to execute the DEL command is very small and comparable to most other # O(1) or O(log_N) commands in Redis. However if the key is associated with an # aggregated value containing millions of elements, the server can block for # a long time (even seconds) in order to complete the operation. @@ -621,7 +621,7 @@ slave-priority 100 # It's up to the design of the application to understand when it is a good # idea to use one or the other. However the Redis server sometimes has to # delete keys or flush the whole database as a side effect of other operations. -# Specifically Redis deletes objects independently of an user call in the +# Specifically Redis deletes objects independently of a user call in the # following scenarios: # # 1) On eviction, because of the maxmemory and maxmemory policy configurations, @@ -914,7 +914,7 @@ lua-time-limit 5000 # Docker and other containers). # # In order to make Redis Cluster working in such environments, a static -# configuration where each node known its public address is needed. The +# configuration where each node knows its public address is needed. The # following two options are used for this scope, and are: # # * cluster-announce-ip |