DEV: clean up old PRs from previous sites (part 5)

content/commands/client-list/index.md

@@ -100,7 +100,7 @@ Here is the meaning of the fields:
 * `psub`: number of pattern matching subscriptions
 * `ssub`: number of shard channel subscriptions. Added in Redis 7.0.3
 * `multi`: number of commands in a MULTI/EXEC context
-* `watch`: number of keys this client is currently watching. Added in Redis 8.0
+* `watch`: number of keys this client is currently watching. Added in Redis 7.4 RC1
 * `qbuf`: query buffer length (0 means no query pending)
 * `qbuf-free`: free space of the query buffer (0 means the buffer is full)
 * `argv-mem`: incomplete arguments for the next command (already extracted from query buffer)

content/commands/eval/index.md

@@ -80,7 +80,7 @@ Scripts **should never** access keys with programmatically-generated names or ba
 **Note:**
 in some cases, users will abuse Lua EVAL by embedding values in the script instead of providing them as argument, and thus generating a different script on each call to EVAL.
 These are added to the Lua interpreter and cached to redis-server, consuming a large amount of memory over time.
-Starting from Redis 8.0, scripts loaded with `EVAL` or [`EVAL_RO`]({{< relref "/commands/eval_ro" >}}) will be deleted from redis after a certain number (least recently used order).
+Starting from Redis 7.4 RC1, scripts loaded with `EVAL` or [`EVAL_RO`]({{< relref "/commands/eval_ro" >}}) will be deleted from redis after a certain number (least recently used order).
 The number of evicted scripts can be viewed through [`INFO`]({{< relref "/commands/info" >}})'s `evicted_scripts`.
 
 Please refer to the [Redis Programmability]({{< relref "/develop/interact/programmability/" >}}) and [Introduction to Eval Scripts]({{< relref "/develop/interact/programmability/eval-intro" >}}) for more information about Lua scripts.

content/commands/ft.sugget/index.md

@@ -53,14 +53,6 @@ title: FT.SUGGET
 
 Get completion suggestions for a prefix
 
-## Syntax
-
-{{< highlight bash >}}
-
-{{< / highlight >}}
-
-[Examples](#examples)
-
 ## Required arguments
 
 <details open>
@@ -105,7 +97,7 @@ returns optional payloads saved along with the suggestions. If no payload is pre
 
 FT.SUGGET returns an array reply, which is a list of the top suggestions matching the prefix, optionally with score after each entry.
 
-## Examples
+## Example
 
 <details open>
 <summary><b>Get completion suggestions for a prefix</b></summary>

content/commands/info/index.md

@@ -126,10 +126,10 @@ Here is the meaning of all fields in the **clients** section:
 *   `blocked_clients`: Number of clients pending on a blocking call ([`BLPOP`]({{< relref "/commands/blpop" >}}),
      [`BRPOP`]({{< relref "/commands/brpop" >}}), [`BRPOPLPUSH`]({{< relref "/commands/brpoplpush" >}}), [`BLMOVE`]({{< relref "/commands/blmove" >}}), [`BZPOPMIN`]({{< relref "/commands/bzpopmin" >}}), [`BZPOPMAX`]({{< relref "/commands/bzpopmax" >}}))
 *   `tracking_clients`: Number of clients being tracked ([`CLIENT TRACKING`]({{< relref "/commands/client-tracking" >}}))
-*   `pubsub_clients`: Number of clients in pubsub mode ([`SUBSCRIBE`]({{< relref "/commands/subscribe" >}}), [`PSUBSCRIBE`]({{< relref "/commands/psubscribe" >}}), [`SSUBSCRIBE`]({{< relref "/commands/ssubscribe" >}})). Added in Redis 8.0
-*   `watching_clients`: Number of clients in watching mode ([`WATCH`]({{< relref "/commands/watch" >}})). Added in Redis 8.0
+*   `pubsub_clients`: Number of clients in pubsub mode ([`SUBSCRIBE`]({{< relref "/commands/subscribe" >}}), [`PSUBSCRIBE`]({{< relref "/commands/psubscribe" >}}), [`SSUBSCRIBE`]({{< relref "/commands/ssubscribe" >}})). Added in Redis 7.4 RC1
+*   `watching_clients`: Number of clients in watching mode ([`WATCH`]({{< relref "/commands/watch" >}})). Added in Redis 7.4 RC1
 *   `clients_in_timeout_table`: Number of clients in the clients timeout table
-*   `total_watched_keys`: Number of watched keys. Added in Redis 8.0.
+*   `total_watched_keys`: Number of watched keys. Added in Redis 7.4 RC1.
 *   `total_blocking_keys`: Number of blocking keys. Added in Redis 7.2.
 *   `total_blocking_keys_on_nokey`: Number of blocking keys that one or more clients that would like to be unblocked when the key is deleted. Added in Redis 7.2.
 
@@ -196,7 +196,7 @@ Here is the meaning of all fields in the **memory** section:
 *   `mem_replication_backlog`: Memory used by replication backlog
 *   `mem_total_replication_buffers`: Total memory consumed for replication buffers - Added in Redis 7.0.
 *   `mem_allocator`: Memory allocator, chosen at compile time.
-*   `mem_overhead_db_hashtable_rehashing`: Temporary memory overhead of database dictionaries currently being rehashed - Added in 8.0.
+*   `mem_overhead_db_hashtable_rehashing`: Temporary memory overhead of database dictionaries currently being rehashed - Added in 7.4 RC1.
 *   `active_defrag_running`: When `activedefrag` is enabled, this indicates whether defragmentation is currently active, and the CPU percentage it intends to utilize.
 *   `lazyfree_pending_objects`: The number of objects waiting to be freed (as a
      result of calling [`UNLINK`]({{< relref "/commands/unlink" >}}), or [`FLUSHDB`]({{< relref "/commands/flushdb" >}}) and [`FLUSHALL`]({{< relref "/commands/flushall" >}}) with the **ASYNC**
@@ -319,7 +319,7 @@ Here is the meaning of all fields in the **stats** section:
 *   `expire_cycle_cpu_milliseconds`: The cumulative amount of time spent on active expiry cycles
 *   `evicted_keys`: Number of evicted keys due to `maxmemory` limit
 *   `evicted_clients`: Number of evicted clients due to `maxmemory-clients` limit. Added in Redis 7.0.
-*   `evicted_scripts`: Number of evicted EVAL scripts due to LRU policy, see [`EVAL`]({{< relref "/commands/eval" >}}) for more details. Added in Redis 8.0.
+*   `evicted_scripts`: Number of evicted EVAL scripts due to LRU policy, see [`EVAL`]({{< relref "/commands/eval" >}}) for more details. Added in Redis 7.4 RC1.
 *   `total_eviction_exceeded_time`:  Total time `used_memory` was greater than `maxmemory` since server startup, in milliseconds
 *   `current_eviction_exceeded_time`: The time passed since `used_memory` last rose above `maxmemory`, in milliseconds
 *   `keyspace_hits`: Number of successful lookup of keys in the main dictionary

content/commands/memory-stats/index.md

@@ -54,13 +54,13 @@ values. The following metrics are reported:
 *   `dbXXX`: For each of the server's databases, the overheads of the main and
      expiry dictionaries (`overhead.hashtable.main` and
     `overhead.hashtable.expires`, respectively) are reported in bytes
-*   `overhead.db.hashtable.lut`: Total overhead of dictionary buckets in databases (Added in Redis 8.0)
-*   `overhead.db.hashtable.rehashing`: Temporary memory overhead of database dictionaries currently being rehashed (Added in Redis 8.0) 
+*   `overhead.db.hashtable.lut`: Total overhead of dictionary buckets in databases (Added in Redis 7.4 RC1)
+*   `overhead.db.hashtable.rehashing`: Temporary memory overhead of database dictionaries currently being rehashed (Added in Redis 7.4 RC1) 
 *   `overhead.total`: The sum of all overheads, i.e. `startup.allocated`,
      `replication.backlog`, `clients.slaves`, `clients.normal`, `aof.buffer` and
      those of the internal data structures that are used in managing the
      Redis keyspace (see [`INFO`]({{< relref "/commands/info" >}})'s `used_memory_overhead`)
-*   `db.dict.rehashing.count`: Number of DB dictionaries currently being rehashed (Added in Redis 8.0)
+*   `db.dict.rehashing.count`: Number of DB dictionaries currently being rehashed (Added in Redis 7.4 RC1)
 *   `keys.count`: The total number of keys stored across all databases in the
      server
 *   `keys.bytes-per-key`: The ratio between `dataset.bytes` and `keys.count` 

content/commands/sort/index.md

@@ -231,9 +231,9 @@ SORT mylist BY weight_* GET object_* GET #
 
 ## Restrictions for using external keys
 
-Before 8.0, when enabling `Redis cluster-mode` there is no way to guarantee the existence of the external keys on the node which the command is processed on. In this case, any use of [`GET`]({{< relref "/commands/get" >}}) or `BY` which reference external key pattern will cause the command to fail with an error.
+Before 7.4 RC1, when enabling `Redis cluster-mode` there is no way to guarantee the existence of the external keys on the node which the command is processed on. In this case, any use of [`GET`]({{< relref "/commands/get" >}}) or `BY` which reference external key pattern will cause the command to fail with an error.
 
-Starting from 8.0, pattern with hash tag can be mapped to a slot, and so in `Redis cluster-mode`, the use of `BY` or [`GET`]({{< relref "/commands/get" >}}) is allowed when pattern contains hash tag and implies a specific slot which the key is also in, which means any key matching this pattern must be in the same slot as the key, and therefore in the same node. For example, in cluster mode, `{mylist}weight_*` is acceptable as a pattern when sorting `mylist`, while pattern `{abc}weight_*` will be denied, causing the command to fail with an error.
+Starting from 7.4 RC1, pattern with hash tag can be mapped to a slot, and so in `Redis cluster-mode`, the use of `BY` or [`GET`]({{< relref "/commands/get" >}}) is allowed when pattern contains hash tag and implies a specific slot which the key is also in, which means any key matching this pattern must be in the same slot as the key, and therefore in the same node. For example, in cluster mode, `{mylist}weight_*` is acceptable as a pattern when sorting `mylist`, while pattern `{abc}weight_*` will be denied, causing the command to fail with an error.
 
 To use pattern with hash tag, see [Hash tags]({{< baseurl >}}/operate/oss_and_stack/reference/cluster-spec#hash-tags) for more information.
 

content/commands/xread/index.md

@@ -262,9 +262,16 @@ You can read the last entry in a single stream easily using the `XREVRANGE` comm
 ```
 > XREVRANGE stream + - COUNT 1
 ```
+<<<<<<< Updated upstream
 But this approach becomes slow as you add more streams because you must issue a separate command for each stream.
 Instead, starting from Redis 7.4 RC1, you can use the `+` sign as a special ID.
 This requests the last available entry in a stream. For example:
+=======
+But if there are many streams involved, this approach is quickly becoming
+too slow, having to issue a command per stream.
+Instead, starting from Redis 7.4 RC1, the `+` sign can be used as a special ID,
+requesting the last available entry in a stream. For example:
+>>>>>>> Stashed changes
 
 ```
 > XREAD STREAM streamA streamB streamC streamD + + + +

content/develop/interact/programmability/lua-api.md

@@ -689,7 +689,7 @@ In addition, the following external libraries are loaded and accessible to scrip
 
 ### <a name="os-library"></a> _os_ library
 
-* Since version: 8.0.0
+* Since version: 7.4 RC1
 * Available in scripts: yes
 * Available in functions: yes