My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions

Issue 385 attachment: typos.patch (3.1 KB)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
208044e9364f8dcd72fcc5bfacf85e8d60e9fbac
diff --git a/redis.conf b/redis.conf
index 5ec2d02..c9b0c16 100644
--- a/redis.conf
+++ b/redis.conf
@@ -184,15 +184,15 @@ slave-serve-stale-data yes
# maxmemory <bytes>

# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
-# is reached? You can select among five behavior:
-#
+# is reached? You can select among five behaviours
+#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys->random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
-#
+#
# Note: with all the kind of policies, Redis will return an error on write
# operations, when there are not suitable keys for eviction.
#
@@ -238,7 +238,7 @@ appendonly no
# appendfilename appendonly.aof

# The fsync() call tells the Operating System to actually write data on disk
-# instead to wait for more data in the output buffer. Some OS will really flush
+# instead of waiting for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
@@ -276,7 +276,7 @@ appendfsync everysec
# the same as "appendfsync none", that in pratical terms means that it is
# possible to lost up to 30 seconds of log in the worst scenario (with the
# default Linux settings).
-#
+#
# If you have latency problems turn this to "yes". Otherwise leave it as
# "no" that is the safest pick from the point of view of durability.
no-appendfsync-on-rewrite no
@@ -300,7 +300,7 @@ vm-enabled no
# file for every redis process you are running. Redis will complain if the
# swap file is already in use.
#
-# The best kind of storage for the Redis swap file (that's accessed at random)
+# The best kind of storage for the Redis swap file (that's accessed at random)
# is a Solid State Disk (SSD).
#
# *** WARNING *** if you are using a shared hosting the default of putting
@@ -309,7 +309,7 @@ vm-enabled no
vm-swap-file /tmp/redis.swap

# vm-max-memory configures the VM to use at max the specified amount of
-# RAM. Everything that deos not fit will be swapped on disk *if* possible, that
+# RAM. Everything that does not fit will be swapped on disk *if* possible, that
# is, if there is still enough contiguous space in the swap file.
#
# With vm-max-memory 0 the system will swap everything it can. Not a good
diff --git a/src/redis.c b/src/redis.c
index cf5673a..b0f99fc 100644
--- a/src/redis.c
+++ b/src/redis.c
@@ -387,7 +387,7 @@ dictType commandTableDictType = {
NULL /* val destructor */
};

-/* Hash type hash table (note that small hashes are represented with zimpaps) */
+/* Hash type hash table (note that small hashes are represented with zipmaps) */
dictType hashDictType = {
dictEncObjHash, /* hash function */
NULL, /* key dup */
Powered by Google Project Hosting