DOC-3967 moved pub/sub and keyspace notification pages

Author: andy-stark-redis

content/commands/cluster-info.md

@@ -66,13 +66,13 @@ Here are the explanation of these fields:
 * `cluster_stats_messages_pong_sent` and `cluster_stats_messages_pong_received`: PONG (reply to PING).
 * `cluster_stats_messages_meet_sent` and `cluster_stats_messages_meet_received`: Handshake message sent to a new node, either through gossip or [`CLUSTER MEET`]({{< relref "/commands/cluster-meet" >}}).
 * `cluster_stats_messages_fail_sent` and `cluster_stats_messages_fail_received`: Mark node xxx as failing.
-* `cluster_stats_messages_publish_sent` and `cluster_stats_messages_publish_received`: Pub/Sub Publish propagation, see [Pubsub]({{< relref "/develop/interact/pubsub#pubsub" >}}).
+* `cluster_stats_messages_publish_sent` and `cluster_stats_messages_publish_received`: Pub/Sub Publish propagation, see [Pubsub]({{< relref "/develop/pubsub#pubsub" >}}).
 * `cluster_stats_messages_auth-req_sent` and `cluster_stats_messages_auth-req_received`: Replica initiated leader election to replace its master.
 * `cluster_stats_messages_auth-ack_sent` and `cluster_stats_messages_auth-ack_received`: Message indicating a vote during leader election.
 * `cluster_stats_messages_update_sent` and `cluster_stats_messages_update_received`: Another node slots configuration.
 * `cluster_stats_messages_mfstart_sent` and `cluster_stats_messages_mfstart_received`: Pause clients for manual failover.
 * `cluster_stats_messages_module_sent` and `cluster_stats_messages_module_received`: Module cluster API message.
-* `cluster_stats_messages_publishshard_sent` and `cluster_stats_messages_publishshard_received`: Pub/Sub Publish shard propagation, see [Sharded Pubsub]({{< relref "/develop/interact/pubsub#sharded-pubsub" >}}).
+* `cluster_stats_messages_publishshard_sent` and `cluster_stats_messages_publishshard_received`: Pub/Sub Publish shard propagation, see [Sharded Pubsub]({{< relref "/develop/pubsub#sharded-pubsub" >}}).
 
 More information about the Current Epoch and Config Epoch variables are available in the [Redis Cluster specification document]({{< relref "/operate/oss_and_stack/reference/cluster-spec#cluster-current-epoch" >}}).
 

content/commands/command.md

@@ -103,7 +103,7 @@ Command flags are an array. It can contain the following simple strings (status
 * **no_mandatory_keys:** the command may accept key name arguments, but these aren't mandatory.
 * **no_multi:** the command isn't allowed inside the context of a [transaction]({{< relref "/develop/reference/transactions" >}}).
 * **noscript:** the command can't be called from [scripts]({{< relref "/develop/programmability/eval-intro" >}}) or [functions]({{< relref "/develop/programmability/functions-intro" >}}).
-* **pubsub:** the command is related to [Redis Pub/Sub]({{< relref "/develop/interact/pubsub" >}}).
+* **pubsub:** the command is related to [Redis Pub/Sub]({{< relref "/develop/pubsub" >}}).
 * **random**: the command returns random results, which is a concern with verbatim script replication.
   As of Redis 7.0, this flag is a [command tip][tb].
 * **readonly:** the command doesn't modify data.

content/commands/psubscribe.md

@@ -47,7 +47,7 @@ Use `\` to escape special characters if you want to match them verbatim.
 Once the client enters the subscribed state it is not supposed to issue any other commands, except for additional [`SUBSCRIBE`]({{< relref "/commands/subscribe" >}}), [`SSUBSCRIBE`]({{< relref "/commands/ssubscribe" >}}), `PSUBSCRIBE`, [`UNSUBSCRIBE`]({{< relref "/commands/unsubscribe" >}}), [`SUNSUBSCRIBE`]({{< relref "/commands/sunsubscribe" >}}), [`PUNSUBSCRIBE`]({{< relref "/commands/punsubscribe" >}}), [`PING`]({{< relref "/commands/ping" >}}), [`RESET`]({{< relref "/commands/reset" >}}) and [`QUIT`]({{< relref "/commands/quit" >}}) commands.
 However, if RESP3 is used (see [`HELLO`]({{< relref "/commands/hello" >}})) it is possible for a client to issue any commands while in subscribed state.
 
-For more information, see [Pub/sub]({{< relref "/develop/interact/pubsub" >}}).
+For more information, see [Pub/sub]({{< relref "/develop/pubsub" >}}).
 
 ## Behavior change history
 

content/commands/spublish.md

@@ -55,7 +55,7 @@ In Redis Cluster, shard channels are assigned to slots by the same algorithm use
 A shard message must be sent to a node that owns the slot the shard channel is hashed to. 
 The cluster makes sure that published shard messages are forwarded to all the nodes in the shard, so clients can subscribe to a shard channel by connecting to any one of the nodes in the shard.
 
-For more information about sharded pubsub, see [Sharded Pubsub]({{< relref "/develop/interact/pubsub#sharded-pubsub" >}}).
+For more information about sharded pubsub, see [Sharded Pubsub]({{< relref "/develop/pubsub#sharded-pubsub" >}}).
 
 ## Examples
 

content/commands/ssubscribe.md

@@ -53,7 +53,7 @@ Client(s) can subscribe to a node covering a slot (primary/replica) to receive t
 All the specified shard channels needs to belong to a single slot to subscribe in a given `SSUBSCRIBE` call,
 A client can subscribe to channels across different slots over separate `SSUBSCRIBE` call.
 
-For more information about sharded Pub/Sub, see [Sharded Pub/Sub]({{< relref "/develop/interact/pubsub#sharded-pubsub" >}}).
+For more information about sharded Pub/Sub, see [Sharded Pub/Sub]({{< relref "/develop/pubsub#sharded-pubsub" >}}).
 
 ## Examples
 

content/commands/subscribe.md

@@ -41,7 +41,7 @@ other commands, except for additional `SUBSCRIBE`, [`SSUBSCRIBE`]({{< relref "/c
 [`PUNSUBSCRIBE`]({{< relref "/commands/punsubscribe" >}}), [`PING`]({{< relref "/commands/ping" >}}), [`RESET`]({{< relref "/commands/reset" >}}) and [`QUIT`]({{< relref "/commands/quit" >}}) commands.
 However, if RESP3 is used (see [`HELLO`]({{< relref "/commands/hello" >}})) it is possible for a client to issue any commands while in subscribed state.
 
-For more information, see [Pub/sub]({{< relref "/develop/interact/pubsub" >}}).
+For more information, see [Pub/sub]({{< relref "/develop/pubsub" >}}).
 
 ## Behavior change history
 

content/commands/sunsubscribe.md

@@ -54,7 +54,7 @@ In this case a message for every unsubscribed shard channel will be sent to the
 
 Note: The global channels and shard channels needs to be unsubscribed from separately.
 
-For more information about sharded Pub/Sub, see [Sharded Pub/Sub]({{< relref "/develop/interact/pubsub#sharded-pubsub" >}}).
+For more information about sharded Pub/Sub, see [Sharded Pub/Sub]({{< relref "/develop/pubsub#sharded-pubsub" >}}).
 
 ## Return information
 

content/develop/clients/nodejs/amr.md

@@ -340,7 +340,7 @@ console.log(`Database size is ${size}`);
 If you are using the
 [RESP2]({{< relref "/develop/reference/protocol-spec#resp-versions" >}})
 protocol, you should
-be aware that [pub/sub]({{< relref "/develop/interact/pubsub" >}}) can
+be aware that [pub/sub]({{< relref "/develop/pubsub" >}}) can
 cause complications with reauthentication.
 
 After a connection enters PUB/SUB mode, the socket is blocked and can't process

content/develop/clients/nodejs/connect.md

@@ -344,7 +344,7 @@ related to connection:
 -   `reconnecting`: (No parameters) The client is about to try reconnecting after the
     connection was lost due to an error.
 -   `sharded-channel-moved`: The cluster slot of a subscribed
-    [sharded pub/sub channel]({{< relref "/develop/interact/pubsub#sharded-pubsub" >}})
+    [sharded pub/sub channel]({{< relref "/develop/pubsub#sharded-pubsub" >}})
     has been moved to another shard. Note that when you use a
     [`RedisCluster`](#connect-to-a-redis-cluster) connection, this event is automatically
     handled for you. See

content/develop/clients/nodejs/migration.md

@@ -321,7 +321,7 @@ for await (const keys of client.scanIterator()) {
 
 `ioredis` reports incoming pub/sub messages with a `message`
 event on the client object (see
-[Publish/subscribe]({{< relref "/develop/interact/pubsub" >}}) for more
+[Publish/subscribe]({{< relref "/develop/pubsub" >}}) for more
 information about messages):
 
 ```js