diff --git a/content/commands/client-caching/index.md b/content/commands/client-caching/index.md
index 5b8f3c1247..44b70c349f 100644
--- a/content/commands/client-caching/index.md
+++ b/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/use/client-side-caching" >}}) for
+[client side caching documentation]({{< relref "/develop/connect/clients/client-side-caching" >}}) for
 background information.
 
 When tracking is enabled Redis, using the [`CLIENT TRACKING`]({{< relref "/commands/client-tracking" >}}) command, it is
diff --git a/content/commands/client-getredir/index.md b/content/commands/client-getredir/index.md
index 3f102aadd6..f596eb21b9 100644
--- a/content/commands/client-getredir/index.md
+++ b/content/commands/client-getredir/index.md
@@ -31,7 +31,7 @@ syntax_str: ''
 title: CLIENT GETREDIR
 ---
 This command returns the client ID we are redirecting our
-[tracking]({{< relref "/develop/use/client-side-caching" >}}) notifications to. We set a client
+[tracking]({{< relref "/develop/connect/clients/client-side-caching#tracking" >}}) notifications to. We set a client
 to redirect to when using [`CLIENT TRACKING`]({{< relref "/commands/client-tracking" >}}) to enable tracking. However in
 order to avoid forcing client libraries implementations to remember the
 ID notifications are redirected to, this command exists in order to improve
diff --git a/content/commands/client-tracking/index.md b/content/commands/client-tracking/index.md
index 74c401eaf9..9c91fc8653 100644
--- a/content/commands/client-tracking/index.md
+++ b/content/commands/client-tracking/index.md
@@ -75,7 +75,7 @@ syntax_str: "[REDIRECT\_client-id] [PREFIX\_prefix [PREFIX prefix ...]] [BCAST]
 title: CLIENT TRACKING
 ---
 This command enables the tracking feature of the Redis server, that is used
-for [server assisted client side caching]({{< relref "/develop/use/client-side-caching" >}}).
+for [server assisted client side caching]({{< relref "/develop/connect/clients/client-side-caching#tracking" >}}).
 
 When tracking is enabled Redis remembers the keys that the connection
 requested, in order to send later invalidation messages when such keys are
@@ -85,7 +85,7 @@ when the RESP3 protocol is used) or redirected in a different connection
 available where clients participating in this protocol receive every
 notification just subscribing to given key prefixes, regardless of the
 keys that they requested. Given the complexity of the argument please
-refer to [the main client side caching documentation]({{< relref "/develop/use/client-side-caching" >}}) for the details. This manual page is only a reference for the options of this subcommand.
+refer to [the main client side caching documentation]({{< relref "/develop/reference/client-side-caching" >}}) for the details. This manual page is only a reference for the options of this subcommand.
 
 In order to enable tracking, use:
 
diff --git a/content/commands/client-trackinginfo/index.md b/content/commands/client-trackinginfo/index.md
index 9f96497d86..cb194690f7 100644
--- a/content/commands/client-trackinginfo/index.md
+++ b/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/use/client-side-caching" >}}) feature.
+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.
 
 Here's the list of tracking information sections and their respective values:
 
diff --git a/content/develop/connect/clients/client-side-caching.md b/content/develop/connect/clients/client-side-caching.md
index 8c9a7a9297..91b83559dd 100644
--- a/content/develop/connect/clients/client-side-caching.md
+++ b/content/develop/connect/clients/client-side-caching.md
@@ -43,7 +43,7 @@ client-side caching works well in the very common use case where a small subset
 is accessed much more frequently than the rest of the data (according
 to the [Pareto principle](https://en.wikipedia.org/wiki/Pareto_principle)).
 
-## Updating the cache when the data changes
+## Updating the cache when the data changes {#tracking}
 
 All caching systems must implement a scheme to update data in the cache
 when the corresponding data changes in the main database. Redis uses an
diff --git a/content/develop/data-types/_index.md b/content/develop/data-types/_index.md
index 77414ef4bd..58f279fe55 100644
--- a/content/develop/data-types/_index.md
+++ b/content/develop/data-types/_index.md
@@ -17,7 +17,7 @@ weight: 35
 ---
 
 Redis is a data structure server.
-At its core, Redis provides a collection of native data types that help you solve a wide variety of problems, from [caching]({{< relref "/develop/use/client-side-caching" >}}) to
+At its core, Redis provides a collection of native data types that help you solve a wide variety of problems, from [caching]({{< relref "/develop/data-types/strings" >}}) to
 [queuing]({{< relref "/develop/data-types/lists" >}}) to
 [event processing]({{< relref "/develop/data-types/streams" >}}).
 Below is a short description of each data type, with links to broader overviews and command references.