diff --git a/msvs/setups/documentation/redis.windows-service.conf b/msvs/setups/documentation/redis.windows-service.conf index aa041067e34e44ea7b306839914ecbf0982db9c0..16f41ee5a7520d970cacd787ba39780fdbf3fef5 100644 --- a/msvs/setups/documentation/redis.windows-service.conf +++ b/msvs/setups/documentation/redis.windows-service.conf @@ -267,7 +267,7 @@ slave-read-only yes repl-diskless-sync no # When diskless replication is enabled, it is possible to configure the delay -# the server waits in order to spawn the child that trnasfers the RDB via socket +# the server waits in order to spawn the child that transfers the RDB via socket # to the slaves. # # This is important since once the transfer starts, it is not possible to serve @@ -488,7 +488,7 @@ slave-priority 100 # # The default is: # -# maxmemory-policy volatile-lru +# maxmemory-policy noeviction # LRU and minimal TTL algorithms are not precise algorithms but approximated # algorithms (in order to save memory), so you can select as well the sample @@ -781,7 +781,7 @@ slowlog-max-len 128 # By default latency monitoring is disabled since it is mostly not needed # if you don't have latency issues, and collecting data has a performance # impact, that while very small, can be measured under big load. Latency -# monitoring can easily be enalbed at runtime using the command +# monitoring can easily be enabled at runtime using the command # "CONFIG SET latency-monitor-threshold " if needed. latency-monitor-threshold 0 diff --git a/msvs/setups/documentation/redis.windows.conf b/msvs/setups/documentation/redis.windows.conf index 6e5880eb657554df08c5e37bba6d510f605206b9..21915cce12e81f0c050fa7b3de406f50bdc45786 100644 --- a/msvs/setups/documentation/redis.windows.conf +++ b/msvs/setups/documentation/redis.windows.conf @@ -267,7 +267,7 @@ slave-read-only yes repl-diskless-sync no # When diskless replication is enabled, it is possible to configure the delay -# the server waits in order to spawn the child that trnasfers the RDB via socket +# the server waits in order to spawn the child that transfers the RDB via socket # to the slaves. # # This is important since once the transfer starts, it is not possible to serve @@ -488,7 +488,7 @@ slave-priority 100 # # The default is: # -# maxmemory-policy volatile-lru +# maxmemory-policy noeviction # LRU and minimal TTL algorithms are not precise algorithms but approximated # algorithms (in order to save memory), so you can select as well the sample @@ -781,7 +781,7 @@ slowlog-max-len 128 # By default latency monitoring is disabled since it is mostly not needed # if you don't have latency issues, and collecting data has a performance # impact, that while very small, can be measured under big load. Latency -# monitoring can easily be enalbed at runtime using the command +# monitoring can easily be enabled at runtime using the command # "CONFIG SET latency-monitor-threshold " if needed. latency-monitor-threshold 0