redis · andy-stark-redis · Jul 30, 2026 · Jul 30, 2026 · Jul 30, 2026 · Jul 30, 2026
diff --git a/HUGO_DEPENDENCY_ASSESSMENT.md b/HUGO_DEPENDENCY_ASSESSMENT.md
diff --git a/content/commands/discard.md b/content/commands/discard.md
@@ -33,7 +33,7 @@ title: DISCARD
 Flushes all previously queued commands in a [transaction][tt] and restores the
 connection state to normal.
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 If [`WATCH`]({{< relref "/commands/watch" >}}) was used, `DISCARD` unwatches all keys watched by the connection.
 

diff --git a/content/commands/exec.md b/content/commands/exec.md
@@ -37,12 +37,12 @@ This command's behavior varies in clustered Redis environments. See the [multi-k
 Executes all previously queued commands in a [transaction][tt] and restores the
 connection state to normal.
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 When using [`WATCH`]({{< relref "/commands/watch" >}}), `EXEC` will execute commands only if the watched keys were
 not modified, allowing for a [check-and-set mechanism][ttc].
 
-[ttc]: /develop/interact/transactions#cas
+[ttc]: /develop/using-commands/transactions#cas
 
 ## Redis Software and Redis Cloud compatibility
 

diff --git a/content/commands/expire.md b/content/commands/expire.md
@@ -104,7 +104,7 @@ Note that calling `EXPIRE`/[`PEXPIRE`]({{< relref "/commands/pexpire" >}}) with
 will be `del`, not `expired`).
 
 [del]: /commands/del
-[ntf]: /develop/use/keyspace-notifications
+[ntf]: /develop/pubsub/keyspace-notifications
 
 ## Required arguments
 

diff --git a/content/commands/multi.md b/content/commands/multi.md
@@ -38,7 +38,7 @@ This command's behavior varies in clustered Redis environments. See the [multi-k
 Marks the start of a [transaction][tt] block.
 Subsequent commands will be queued for atomic execution using [`EXEC`]({{< relref "/commands/exec" >}}).
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 ## Redis Software and Redis Cloud compatibility
 

diff --git a/content/commands/setbit.md b/content/commands/setbit.md
@@ -147,7 +147,7 @@ native programming language. Symmetrically, it is also possible to set an entire
 bitmap by performing the bits-to-bytes encoding in the client and calling [`SET`]({{< relref "/commands/set" >}})
 with the resultant string.
 
-[ti]: /develop/data-types-intro#bitmaps
+[ti]: /develop/data-types#bitmaps
 
 ### Pattern: setting multiple bits
 

diff --git a/content/commands/unwatch.md b/content/commands/unwatch.md
@@ -32,7 +32,7 @@ title: UNWATCH
 ---
 Flushes all the previously watched keys for a [transaction][tt].
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 If you call [`EXEC`]({{< relref "/commands/exec" >}}) or [`DISCARD`]({{< relref "/commands/discard" >}}), there's no need to manually call `UNWATCH`.
 

diff --git a/content/commands/watch.md b/content/commands/watch.md
@@ -56,7 +56,7 @@ This command's behavior varies in clustered Redis environments. See the [multi-k
 Marks the given keys to be watched for conditional execution of a
 [transaction][tt].
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 ## Redis Software and Redis Cloud compatibility
 

diff --git a/content/develop/ai/redisvl/0.14.0/user_guide/sql_to_redis_queries.md b/content/develop/ai/redisvl/0.14.0/user_guide/sql_to_redis_queries.md
@@ -500,7 +500,7 @@ results
 
 ### Aggregations
 
-See docs for redis supported reducer functions: [https://redis.io/docs/latest/develop/ai/search-and-query/advanced-concepts/aggregations/#supported-groupby-reducers](docs).
+See docs for redis supported reducer functions: [docs](https://redis.io/docs/latest/develop/ai/search-and-query/advanced-concepts/aggregations/#supported-groupby-reducers).
 
 
 ```python

diff --git a/content/develop/ai/redisvl/0.23.0/user_guide/how_to_guides/mcp_authentication.md b/content/develop/ai/redisvl/0.23.0/user_guide/how_to_guides/mcp_authentication.md
@@ -19,7 +19,7 @@ authenticated.
 Authentication is a separate concern from **transport security** (Host/Origin
 validation), which is always on for the HTTP transports and defends against DNS
 rebinding independently of auth. See
-[Transport Security](mcp.md#transport-security-host-origin-validation). Both
+[Transport Security]({{< relref "mcp#transport-security-host-origin-validation" >}}). Both
 layers apply together: auth decides *who* may call; the Host/Origin guard
 rejects requests whose claimed authority is not allowlisted.
 {{< /note >}}

diff --git a/content/develop/ai/redisvl/0.6.0/user_guide/_index.md b/content/develop/ai/redisvl/0.6.0/user_guide/_index.md
@@ -84,13 +84,3 @@ User guides provide helpful resources for using RedisVL and its different compon
   * [Optimize](threshold_optimization/#optimize)
   * [Test it out](threshold_optimization/#test-it-out)
   * [Cleanup](threshold_optimization/#cleanup)
-* [Release Guides](release_guide/)
-  * [0.5.1 Feature Overview](release_guide/0_5_0_release/)
-  * [HybridQuery class](release_guide/0_5_0_release/#hybridquery-class)
-  * [TextQueries](release_guide/0_5_0_release/#textqueries)
-  * [Threshold optimization](release_guide/0_5_0_release/#threshold-optimization)
-  * [Schema validation](release_guide/0_5_0_release/#schema-validation)
-  * [Timestamp filters](release_guide/0_5_0_release/#timestamp-filters)
-  * [Batch search](release_guide/0_5_0_release/#batch-search)
-  * [Vector normalization](release_guide/0_5_0_release/#vector-normalization)
-  * [Hybrid policy on knn with filters](release_guide/0_5_0_release/#hybrid-policy-on-knn-with-filters)
diff --git a/content/develop/ai/redisvl/0.7.0/user_guide/_index.md b/content/develop/ai/redisvl/0.7.0/user_guide/_index.md
@@ -84,13 +84,3 @@ User guides provide helpful resources for using RedisVL and its different compon
   * [Optimize](threshold_optimization/#optimize)
   * [Test it out](threshold_optimization/#test-it-out)
   * [Cleanup](threshold_optimization/#cleanup)
-* [Release Guides](release_guide/)
-  * [0.5.1 Feature Overview](release_guide/0_5_0_release/)
-  * [HybridQuery class](release_guide/0_5_0_release/#hybridquery-class)
-  * [TextQueries](release_guide/0_5_0_release/#textqueries)
-  * [Threshold optimization](release_guide/0_5_0_release/#threshold-optimization)
-  * [Schema validation](release_guide/0_5_0_release/#schema-validation)
-  * [Timestamp filters](release_guide/0_5_0_release/#timestamp-filters)
-  * [Batch search](release_guide/0_5_0_release/#batch-search)
-  * [Vector normalization](release_guide/0_5_0_release/#vector-normalization)
-  * [Hybrid policy on knn with filters](release_guide/0_5_0_release/#hybrid-policy-on-knn-with-filters)
diff --git a/content/develop/ai/redisvl/user_guide/how_to_guides/mcp_authentication.md b/content/develop/ai/redisvl/user_guide/how_to_guides/mcp_authentication.md
@@ -20,7 +20,7 @@ authenticated.
 Authentication is a separate concern from **transport security** (Host/Origin
 validation), which is always on for the HTTP transports and defends against DNS
 rebinding independently of auth. See
-[Transport Security](mcp.md#transport-security-host-origin-validation). Both
+[Transport Security]({{< relref "mcp#transport-security-host-origin-validation" >}}). Both
 layers apply together: auth decides *who* may call; the Host/Origin guard
 rejects requests whose claimed authority is not allowlisted.
 {{< /note >}}

diff --git a/content/develop/ai/search-and-query/advanced-concepts/aggregations-syntax.md b/content/develop/ai/search-and-query/advanced-concepts/aggregations-syntax.md
@@ -23,10 +23,6 @@ The [main aggregations page]({{< relref "/develop/ai/search-and-query/advanced-c
 
 `GROUPBY` ... `REDUCE` ... `APPLY` ... `GROUPBY` ... `REDUCE`
 
-{{< note >}}
-The examples on this page are based on a hypothetical "products" data set, which you can [download here](./data/products.txt).
-{{< /note >}}
-
 ## Syntax and expression ordering
 
 The `FT.AGGREGATE` command processes multiple expressions in a pipeline. Below is the recommended order:

diff --git a/content/develop/clients/nodejs/amr.md b/content/develop/clients/nodejs/amr.md
@@ -155,7 +155,7 @@ authorityConfig: {
   },
 // ...
 ```
-See Microsoft's [Authority]([Authority](https://learn.microsoft.com/en-us/entra/identity-platform/msal-client-application-configuration#authority))
+See Microsoft's [Authority](https://learn.microsoft.com/en-us/entra/identity-platform/msal-client-application-configuration#authority)
 docs for more information.
 
 ### Authenticate with a service principal

diff --git a/content/develop/clients/redis-py/_index.md b/content/develop/clients/redis-py/_index.md
@@ -26,10 +26,10 @@ weight: 1
 The sections below explain how to install `redis-py` and connect your application
 to a Redis database.
 
-`redis-py` requires a running Redis server. See [here]({{< relref "/operate/oss_and_stack/install/" >}}) for Redis Open Source installation instructions.
+`redis-py` requires a running Redis server. See [here](../../../operate/oss_and_stack/install/_index.md) for Redis Open Source installation instructions.
 
 You can also access Redis with an object-mapping client interface. See
-[RedisOM for Python]({{< relref "/integrate/redisom-for-python" >}})
+[RedisOM for Python](../../../integrate/redisom-for-python/_index.md)
 for more information.
 
 ## Install

diff --git a/content/develop/clients/redis-py/amr.md b/content/develop/clients/redis-py/amr.md
@@ -26,7 +26,7 @@ letting `redis-entra-id` fetch and renew the authentication tokens for you autom
 
 ## Install
 
-Install [`redis-py`]({{< relref "/develop/clients/redis-py#install" >}}) first,
+Install [`redis-py`](_index.md#install) first,
 if you have not already done so. Then, install `redis-entra-id` with the
 following command:
 
@@ -134,11 +134,11 @@ When you have created your `CredentialProvider` instance, you are ready to
 connect to AMR.
 The example below shows how to pass the instance as a parameter to the standard
 `RedisCluster()` connection method.
-{{< note >}} Azure requires you to use
-[Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security)
-when you connect (see
-[Connect with TLS]({{< relref "/develop/clients/redis-py/connect#connect-to-your-production-redis-with-tls" >}}) for more information).
-{{< /note >}}
+> [!NOTE]
+> Azure requires you to use
+> [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security)
+> when you connect (see
+> [Connect with TLS](connect.md#connect-to-your-production-redis-with-tls) for more information).
 
 ```python
 from redis import RedisCluster

diff --git a/content/develop/clients/redis-py/async.md b/content/develop/clients/redis-py/async.md
@@ -21,7 +21,7 @@ namespace. It mirrors the synchronous client API, so most code patterns
 translate directly — you `await` commands instead of calling them.
 
 Use the async client for I/O-bound workloads, for integration with async web
-frameworks (such as [FastAPI]({{< relref "/integrate/fastapi" >}}), [Starlette](https://www.starlette.io/), [aiohttp](https://docs.aiohttp.org/en/stable/), or [Sanic](https://sanic.dev/en/), or when you need
+frameworks (such as [FastAPI](../../../integrate/fastapi/_index.md), [Starlette](https://www.starlette.io/), [aiohttp](https://docs.aiohttp.org/en/stable/), or [Sanic](https://sanic.dev/en/), or when you need
 to run many concurrent Redis operations from a single process. For simple
 scripts, CPU-bound work, or codebases without an existing event loop, the
 synchronous client is usually a better choice.
@@ -50,7 +50,7 @@ which ensures `aclose()` runs even if an exception is raised:
 
 For production usage, you should manage connections with a connection pool
 rather than opening and closing them individually.
-See [Connection pools and multiplexing]({{< relref "/develop/clients/pools-and-muxing" >}})
+See [Connection pools and multiplexing](../pools-and-muxing.md)
 for more information about how this works.
 
 A `Redis` client instance already creates and manages its own connection
@@ -93,7 +93,7 @@ through a single connection instead.)
 ## Pipelines and transactions
 
 Pipelines and transactions work the same way as in the synchronous client
-(see [Pipelines and transactions]({{< relref "/develop/clients/redis-py/transpipe" >}})
+(see [Pipelines and transactions](transpipe.md)
 for the conceptual background). The only difference is that you create the
 pipeline inside an `async with` block and `await pipe.execute()`.
 
@@ -125,7 +125,7 @@ consuming task its own subscription.
 
 To connect to a Redis cluster asynchronously, import `RedisCluster` from
 `redis.asyncio.cluster`. The API matches the synchronous cluster client
-(see [Connect to a Redis cluster]({{< relref "/develop/clients/redis-py/connect#connect-to-a-redis-cluster" >}})),
+(see [Connect to a Redis cluster](connect.md#connect-to-a-redis-cluster)),
 with `await` in front of each command.
 
 {{< clients-example set="async_intro" step="cluster" lang_filter="Python" description="Foundational: Connect to a Redis cluster with the async client" difficulty="beginner" >}}
@@ -139,7 +139,7 @@ Always close clients and pools when you're done:
   single scope.
 - For longer-lived clients, call `await r.aclose()` explicitly. (The older
   `close()` method is deprecated.)
-- For frameworks with startup/shutdown hooks — for example [FastAPI]({{< relref "/integrate/fastapi" >}})'s
+- For frameworks with startup/shutdown hooks — for example [FastAPI](../../../integrate/fastapi/_index.md)'s
   `lifespan` — create the client or pool at startup and close it at
   shutdown so connections aren't leaked between process restarts.
 
@@ -178,6 +178,6 @@ client, apply these rules:
 
 - The [`redis-py` asyncio examples](https://redis.readthedocs.io/en/stable/examples/asyncio_examples.html)
   on Read the Docs cover further patterns.
-- See [Error handling]({{< relref "/develop/clients/redis-py/error-handling" >}}) and
-  [Client-side geographic failover]({{< relref "/develop/clients/redis-py/failover" >}}) for
+- See [Error handling](error-handling.md) and
+  [Client-side geographic failover](failover.md) for
   resiliency patterns that apply to both sync and async clients.