anchor.diff:  # still in execution after the maximum allowed time and will start to
   # reply to queries with an error.
   #
  -# When a long running script exceed the maximum execution time only the
  +# When a long running script exceeds the maximum execution time only the
   # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
   # used to stop a script that did not yet called write commands. The second
  -# is the only way to shut down the server in the case a write commands was
  -# already issue by the script but the user don't want to wait for the natural
  +# is the only way to shut down the server in the case a write command was
  +# already issued by the script but the user doesn't want to wait for the natural
   # termination of the script.
   #
   # Set it to 0 or a negative value for unlimited execution without warnings.
  
positive.code: 
  # Don't use more memory than the specified amount of bytes.
  # When the memory limit is reached Redis will try to remove keys
  # accordingly to the eviction policy selected (see maxmemmory-policy).
  #
  # If Redis can't remove keys according to the policy, or if the policy is
  # set to 'noeviction', Redis will start to reply with errors to commands
  
negative.code: # that will prevent fsync() from being called in the main process while a
  # BGSAVE or BGREWRITEAOF is in progress.
  #
  # This means that while another child is saving, the durability of Redis is
  # the same as "appendfsync none". In practical terms, this means that it is
  # possible to lose 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
  