We need help updating the documentation to update all references of Redis to Valkey outside of the command references (which was previously completed in #4). When updating the documentation, watch out for the following:

1. Only update independent references to Redis. Links to "redis.io" can usually be updated to "valkey.io" because the pages are organized in the same way (the contents of this doc repo). Don't update parts of other URLs or references to external websites. Feel free to delete references to Redis inc. products like RedisJSON as appropriate.

2. Generally keep the capitalization. "Redis" -> "Valkey" and "redis" -> "valkey". This works for almost all usage, for example redis-cli becomes valkey-cli. Some usages of lowercase "redis" need to be handled specially though:

   • The redis object in Lua scripts is replaced by server. Examples:

     -EVAL_RO "return redis.call('GET', KEYS[1])" 1 mykey
     +EVAL_RO "return server.call('GET', KEYS[1])" 1 mykey

     -FUNCTION LOAD "#!lua name=mylib \n redis.register_function('myfunc', function(keys, args) return args[1] end)"
     +FUNCTION LOAD "#!lua name=mylib \n server.register_function('myfunc', function(keys, args) return args[1] end)"

   • Examples where "redis" is part of the valkey-cli prompt are just wrong. The real prompt is just the host and port.

     -redis 127.0.0.1:6379> scan 0
     +127.0.0.1:6379> scan 0

3. Skip the names of clients and tools. "StackExchange.Redis" is obviously the name of a client. It's best to skip the whole directories clients/, modules/ and tools/ when doing the bulk of this work and we'll handle them separately. (We need to investigate, discuss and decide what to do with them.)

4. Explicit references to old version of Redis are handled in either of these ways, depending on the context and usefulness of the information:

   • If it's references to Redis 1-5 (really old), they are simply deleted, but sometimes the sentences need to be rewritten to make sense. Examples:

     • -Starting with Redis 3.2, it is possible to
       +It is possible to

     • -Firstly, and ever since Redis 2.6.0, the `EVAL` command enables running server-side scripts.
       +Firstly, the `EVAL` command enables running server-side scripts.

     • Delete the whole section or note if it's only valid for the really old versions.

       -**Note for Redis < 2.6.5:** Prior to Redis 2.6.5 clients needed to detect errors occurring prior to `EXEC` by checking
       -the return value of the queued command: if the command replies with QUEUED it was

     • -Redis 2.6 introduces the *Redis Software Watchdog* that is a debugging tool
       +Valkey comes with a *Software Watchdog* that is a debugging tool

     • -In version Redis 2.8, a new feature was introduced that allows
       -getting ranges lexicographically, assuming elements in a sorted set are all
       +It is possible to
       +get ranges lexicographically, assuming elements in a sorted set are all

   • If it's related to the upgrade path or compatibility, include the reference to the old Redis version, but refer to Redis using the term "Redis OSS", like "Redis OSS 6.0". This is according to Redis Trademark Policy.

     • -Note that before Redis 7.2.0, **seen-time** used to denote the last successful interaction.
       +Note that before Redis OSS 7.2.0, **seen-time** used to denote the last successful interaction.

   • When reference to 4.0 and newer are deleted, post them here so we can pull them into a compatibility page for future reference.

5. Don't edit docs/reference/modules/modules-api-ref.md. It's generated from module.c in the code repo. (We can do that in a separate PR.)

6. Don't edit commands.json. It's generated from the main repo. (We can do that in a separate PR.)

7. Some pages are completely irrelevant. Don't waste time to rewrite the text about things which is not relevant to Valkey. Maybe we'll delete some of these pages later (not in the same PR).