DOC-4543 fix links to client section pages

Author: andy-stark-redis

content/commands/client-caching/index.md

@@ -43,7 +43,7 @@ title: CLIENT CACHING
 This command controls the tracking of the keys in the next command executed
 by the connection, when tracking is enabled in `OPTIN` or `OPTOUT` mode.
 Please check the
-[client side caching documentation]({{< relref "/develop/connect/clients/client-side-caching" >}}) for
+[client side caching documentation]({{< relref "/develop/clients/client-side-caching" >}}) for
 background information.
 
 When tracking is enabled Redis, using the [`CLIENT TRACKING`]({{< relref "/commands/client-tracking" >}}) command, it is

content/commands/client-trackinginfo/index.md

@@ -29,7 +29,7 @@ syntax_fmt: CLIENT TRACKINGINFO
 syntax_str: ''
 title: CLIENT TRACKINGINFO
 ---
-The command returns information about the current client connection's use of the [server assisted client side caching]({{< relref "/develop/connect/clients/client-side-caching" >}}) feature.
+The command returns information about the current client connection's use of the [server assisted client side caching]({{< relref "/develop/clients/client-side-caching" >}}) feature.
 
 Here's the list of tracking information sections and their respective values:
 

content/develop/clients/_index.md

@@ -23,14 +23,14 @@ for six main languages:
 
 | Language | Client name | Docs | Supported |
 | :-- | :-- | :-- | :-- |
-| [Python](https://www.python.org/) | [`redis-py`](https://github.com/redis/redis-py) |[Redis Python library guide]({{< relref "/develop/connect/clients/python/redis-py" >}}) | Yes |
+| [Python](https://www.python.org/) | [`redis-py`](https://github.com/redis/redis-py) |[Redis Python library guide]({{< relref "/develop/clients/redis-py" >}}) | Yes |
 | [Python](https://www.python.org/) | [`RedisVL`](https://github.com/redis/redis-vl-python) |[RedisVL guide]({{< relref "/integrate/redisvl" >}}) | Yes 
-| [C#/.NET](https://learn.microsoft.com/en-us/dotnet/csharp/) | [`NRedisStack`](https://github.com/redis/NRedisStack) |[C#/.NET guide]({{< relref "/develop/connect/clients/dotnet" >}}) | Yes |
-| [Node.js](https://nodejs.org/en) | [`node-redis`](https://github.com/redis/node-redis) | [Node.js guide]({{< relref "/develop/connect/clients/nodejs" >}}) | Yes |
-| [Java](https://www.java.com/en/) | [`Jedis`](https://github.com/redis/jedis) | [Jedis guide]({{< relref "/develop/connect/clients/java/jedis" >}}) |  Yes |
-| [Java](https://www.java.com/en/) | [`Lettuce`](https://github.com/redis/lettuce) | [Lettuce guide]({{< relref "/develop/connect/clients/java/lettuce" >}}) | Yes |
-| [Go](https://go.dev/) | [`go-redis`](https://github.com/redis/go-redis) | [Go guide]({{< relref "/develop/connect/clients/go" >}}) | Yes |
-| [PHP](https://www.php.net/)| [`Predis`](https://github.com/predis/predis) | [PHP guide]({{< relref "/develop/connect/clients/php" >}}) | No |
+| [C#/.NET](https://learn.microsoft.com/en-us/dotnet/csharp/) | [`NRedisStack`](https://github.com/redis/NRedisStack) |[C#/.NET guide]({{< relref "/develop/clients/dotnet" >}}) | Yes |
+| [Node.js](https://nodejs.org/en) | [`node-redis`](https://github.com/redis/node-redis) | [Node.js guide]({{< relref "/develop/clients/nodejs" >}}) | Yes |
+| [Java](https://www.java.com/en/) | [`Jedis`](https://github.com/redis/jedis) | [Jedis guide]({{< relref "/develop/clients/jedis" >}}) |  Yes |
+| [Java](https://www.java.com/en/) | [`Lettuce`](https://github.com/redis/lettuce) | [Lettuce guide]({{< relref "/develop/clients/lettuce" >}}) | Yes |
+| [Go](https://go.dev/) | [`go-redis`](https://github.com/redis/go-redis) | [Go guide]({{< relref "/develop/clients/go" >}}) | Yes |
+| [PHP](https://www.php.net/)| [`Predis`](https://github.com/predis/predis) | [PHP guide]({{< relref "/develop/clients/php" >}}) | No |
 
 We also provide several higher-level
 [object mapping (OM)]({{< relref "/develop/connect/clients/om-clients" >}})

content/develop/clients/jedis/_index.md

@@ -17,7 +17,7 @@ weight: 5
 ---
 
 [Jedis](https://github.com/redis/jedis) is a synchronous Java client for Redis.
-Use [Lettuce]({{< relref "/develop/connect/clients/java/lettuce" >}}) if you need
+Use [Lettuce]({{< relref "/develop/clients/lettuce" >}}) if you need
 a more advanced Java client that also supports asynchronous and reactive connections.
 The sections below explain how to install `Jedis` and connect your application
 to a Redis database.

content/develop/clients/jedis/connect.md

@@ -151,7 +151,7 @@ public class Main {
 
 Client-side caching is a technique to reduce network traffic between
 the client and server, resulting in better performance. See
-[Client-side caching introduction]({{< relref "/develop/connect/clients/client-side-caching" >}})
+[Client-side caching introduction]({{< relref "/develop/clients/client-side-caching" >}})
 for more information about how client-side caching works and how to use it effectively.
 
 To enable client-side caching, specify the
@@ -274,7 +274,7 @@ one of its open connections. When you subsequently close the same connection,
 it is not actually closed but simply returned to the pool for reuse.
 This avoids the overhead of repeated connecting and disconnecting.
 See
-[Connection pools and multiplexing]({{< relref "/develop/connect/clients/pools-and-muxing" >}})
+[Connection pools and multiplexing]({{< relref "/develop/clients/pools-and-muxing" >}})
 for more information.
 
 Use the following code to connect with a connection pool:

content/develop/clients/lettuce/_index.md

@@ -19,7 +19,7 @@ weight: 6
 [Lettuce](https://github.com/redis/lettuce/tree/main/src/main) is an advanced Java client for Redis
 that supports synchronous, asynchronous, and reactive connections.
 If you only need synchronous connections then you may find the other Java client
-[Jedis]({{< relref "/develop/connect/clients/java/jedis" >}}) easier to use.
+[Jedis]({{< relref "/develop/clients/jedis" >}}) easier to use.
 
 The sections below explain how to install `Lettuce` and connect your application
 to a Redis database.

content/develop/clients/lettuce/connect.md

@@ -176,7 +176,7 @@ For connection pooling, Lettuce leverages `RedisClient` or `RedisClusterClient`,
 A typical approach with Lettuce is to create a single `RedisClient` instance and reuse it to establish connections to your Redis server(s).
 These connections are multiplexed; that is, multiple commands can be run concurrently over a single or a small set of connections, making explicit pooling less practical.
 See
-[Connection pools and multiplexing]({{< relref "/develop/connect/clients/pools-and-muxing" >}})
+[Connection pools and multiplexing]({{< relref "/develop/clients/pools-and-muxing" >}})
 for more information.
 
 Lettuce provides pool config to be used with Lettuce asynchronous connection methods.

content/develop/clients/pools-and-muxing.md

@@ -27,13 +27,13 @@ code by making as few separate connections as possible.
 Managing connections in your own code can be tricky, so the Redis
 client libraries give you some help. The two basic approaches to
 connection management are called *connection pooling* and *multiplexing*.
-The [`redis-py`]({{< relref "/develop/connect/clients/python/redis-py" >}}),
-[`jedis`]({{< relref "/develop/connect/clients/java/jedis" >}}), and
-[`go-redis`]({{< relref "/develop/connect/clients/go" >}}) clients support
+The [`redis-py`]({{< relref "/develop/clients/redis-py" >}}),
+[`jedis`]({{< relref "/develop/clients/jedis" >}}), and
+[`go-redis`]({{< relref "/develop/clients/go" >}}) clients support
 connection pooling, while
-[`NRedisStack`]({{< relref "/develop/connect/clients/dotnet" >}})
+[`NRedisStack`]({{< relref "/develop/clients/dotnet" >}})
 supports multiplexing.
-[`Lettuce`]({{< relref "/develop/connect/clients/java/lettuce" >}})
+[`Lettuce`]({{< relref "/develop/clients/lettuce" >}})
 supports both approaches.
 
 ## Connection pooling

content/develop/clients/redis-py/connect.md

@@ -95,7 +95,7 @@ For more information, see [redis-py TLS examples](https://redis-py.readthedocs.i
 
 Client-side caching is a technique to reduce network traffic between
 the client and server, resulting in better performance. See
-[Client-side caching introduction]({{< relref "/develop/connect/clients/client-side-caching" >}})
+[Client-side caching introduction]({{< relref "/develop/clients/client-side-caching" >}})
 for more information about how client-side caching works and how to use it effectively.
 
 To enable client-side caching, add some extra parameters when you connect
@@ -214,7 +214,7 @@ one of its open connections. When you subsequently close the same connection,
 it is not actually closed but simply returned to the pool for reuse.
 This avoids the overhead of repeated connecting and disconnecting.
 See
-[Connection pools and multiplexing]({{< relref "/develop/connect/clients/pools-and-muxing" >}})
+[Connection pools and multiplexing]({{< relref "/develop/clients/pools-and-muxing" >}})
 for more information.
 
 Use the following code to connect with a connection pool:

content/develop/data-types/timeseries/clients.md

@@ -22,7 +22,7 @@ The table below shows the client libraries that support Redis time series:
 | Language | Client |
 | :-- | :-- |
 | Python | [redis-py]({{< relref "/develop/connect/clients/python" >}}) |
-| JavaScript | [node-redis]({{< relref "/develop/connect/clients/nodejs" >}}) |
-| Java | [Jedis]({{< relref "/develop/connect/clients/java/jedis" >}}) |
-| C#/.NET | [NRedisStack]({{< relref "/develop/connect/clients/dotnet" >}}) |
+| JavaScript | [node-redis]({{< relref "/develop/clients/nodejs" >}}) |
+| Java | [Jedis]({{< relref "/develop/clients/jedis" >}}) |
+| C#/.NET | [NRedisStack]({{< relref "/develop/clients/dotnet" >}}) |
 | Go | [redistimeseries-go](https://github.com/RedisTimeSeries/redistimeseries-go/)