diff --git a/content/develop/interact/search-and-query/advanced-concepts/query_syntax.md b/content/develop/interact/search-and-query/advanced-concepts/query_syntax.md
index 3a537e83c6..4c1154966b 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/query_syntax.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/query_syntax.md
@@ -182,7 +182,7 @@ Finally, there's new [`FT.SEARCH`]({{< relref "commands/ft.search/" >}}) syntax
 
 Here's an example using two stacked polygons that represent a box contained within a house.
 
-![two stacked polygons]({{< relref "develop/interact/search-and-query/img/polygons.png" >}})
+{{< image filename="develop/interact/search-and-query/img/polygons.png" >}}
 
 First, create an index using a `FLAT` `GEOSHAPE`, representing a 2D X Y coordinate system.
 
diff --git a/content/develop/interact/search-and-query/advanced-concepts/stemming.md b/content/develop/interact/search-and-query/advanced-concepts/stemming.md
index 7cdf9b58b1..8db542e513 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/stemming.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/stemming.md
@@ -27,7 +27,7 @@ For further details see the [Snowball Stemmer website](https://snowballstem.org/
 Stemming maps different forms of the same word to a common root - "stem" - for example, the English stemmer maps *studied* ,*studies* and *study* to *studi* . So a searching for *studied* would also find documents which only have the other forms.
 
 
-In order to define which language the Stemmer should apply when building the index, you need to specify the `LANGUAGE` parameter for the entire index or for the specific field. For more details check the [FT.CREATE]({{< relref "develop/commands/ft.create" >}}) syntax.
+In order to define which language the Stemmer should apply when building the index, you need to specify the `LANGUAGE` parameter for the entire index or for the specific field. For more details check the [FT.CREATE]({{< relref "commands/ft.create" >}}) syntax.
 
 **Create a index with language definition**
 
diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md
index 9af8dca8e6..dd0283673a 100644
--- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md
+++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/graph-quickstart.md
@@ -217,7 +217,7 @@ Alex's updated friend count: [[1]]
 
 You can use the [Redis Insight]({{< relref "/develop/tools/insight" >}}) workbench to visualize the relationships between the nodes of your graph.
 
-1. Connect to your database with Redis Insight. You can [connect manually]({{< relref "develop/connect/insight/#add-a-standalone-redis-database" >}}) or use the [auto-discovery]({{< relref "develop/connect/insight/#auto-discovery-for-redis-cloud-databases" >}}) feature.
+1. Connect to your database with Redis Insight. You can [connect manually]({{< relref "develop/tools/insight#add-a-standalone-redis-database" >}}) or use the [auto-discovery]({{< relref "develop/tools/insight#auto-discovery-for-redis-cloud-databases" >}}) feature.
 
 1. Select the **Workbench** button:
 
diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Debugging.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Debugging.md
index 048d89527f..0387902c00 100644
--- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Debugging.md
+++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Debugging.md
@@ -46,7 +46,7 @@ After loading the library and executing the function with `TFCALL`, you'll see s
 
 ### Use Redis pub/sub
 
-If you don't have access to your Redis database log files, you can use pub/sub. The following example demonstrates how to use the [client.call]({{< relref "develop/interact/programmability/triggers-and-functions/concepts/javascript_api/#clientcall" >}}) API to publish to a pub/sub channel.
+If you don't have access to your Redis database log files, you can use pub/sub. The following example demonstrates how to use the [client.call]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/concepts/JavaScript_API#clientcall" >}}) API to publish to a pub/sub channel.
 
 ```javascript
 #!js api_version=1.0 name=lib
diff --git a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/concepts/Cluster_Support.md b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/concepts/Cluster_Support.md
index 9729f89bb2..c295dae99a 100644
--- a/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/concepts/Cluster_Support.md
+++ b/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/concepts/Cluster_Support.md
@@ -109,7 +109,7 @@ The remote function arguments and results are serialized in the following way:
 
 ## Execution timeout
 
-Remote functions will not be permitted to run forever and will timeout. The timeout period can be configured using [remote-task-default-timeout]({{< relref "develop/interact/programmability/triggers-and-functions/configuration/#remote-task-default-timeout" >}}).
+Remote functions will not be permitted to run forever and will timeout. The timeout period can be configured using [remote-task-default-timeout]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions/Configuration#remote-task-default-timeout" >}}).
 When using `async_client.runOnShards` API, the timeout will be added as error to the error array. When using `async_client.runOnKey`, a timeout will cause an exception to be raised.
 
 ## Remote function limitations