fix warnings

Author: kaitlynmichael

content/operate/kubernetes/7.4.6/re-databases/db-controller.md

@@ -27,11 +27,11 @@ the custom resource with default values to create a full specification. It then
 database on the specified Redis Enterprise cluster (REC).
 
 Once the database is created, it is exposed with the same service mechanisms by the service rigger for the Redis Enterprise cluster.
-If the database [custom resource is deleted]({{< relref "/operate/kubernetes/re-clusters/delete-custom-resources/" >}}), the database and its services are deleted from the cluster.
+If the database [custom resource is deleted]({{< relref "/operate/kubernetes/7.4.6/delete-custom-resources" >}}), the database and its services are deleted from the cluster.
 
 ### Flexible deployment options
 
-Databases in multiple namespaces can be managed by the same operator. To learn more, see [Manage databases in multiple namespaces]({{<relref "/operate/kubernetes/re-clusters/multi-namespace/">}}).
+Databases in multiple namespaces can be managed by the same operator. To learn more, see [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/re-clusters/multi-namespace" >}}).
 
 To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/deployment/deployment-options.md" >}}).
 

content/operate/kubernetes/re-databases/db-controller.md

@@ -26,11 +26,11 @@ the custom resource with default values to create a full specification. It then
 database on the specified Redis Enterprise cluster (REC).
 
 Once the database is created, it is exposed with the same service mechanisms by the service rigger for the Redis Enterprise cluster.
-If the database [custom resource is deleted]({{< relref "/operate/kubernetes/re-clusters/delete-custom-resources/" >}}), the database and its services are deleted from the cluster.
+If the database [custom resource is deleted]({{< relref "/operate/kubernetes/7.4.6/delete-custom-resources" >}}), the database and its services are deleted from the cluster.
 
 ### Flexible deployment options
 
-Databases in multiple namespaces can be managed by the same operator. To learn more, see [Manage databases in multiple namespaces]({{<relref "/operate/kubernetes/re-clusters/multi-namespace/">}}).
+Databases in multiple namespaces can be managed by the same operator. To learn more, see [Manage databases in multiple namespaces]({{<relref "/operate/kubernetes/re-clusters/multi-namespace">}}).
 
 To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/deployment/deployment-options.md" >}}).
 

content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-34-2022-05.md

@@ -20,7 +20,7 @@ The Redis Enterprise K8s 6.2.10-34 supports the Redis Enterprise Software releas
 The key new features, bug fixes, and known limitations are described below.
 
 {{<warning>}}
-  **Do not** upgrade to this 6.2.10-34 release if you are an **OpenShift** customer and **also use modules**. Instead, **use the [6.2.10-45]({{< relref "/operate/kubernetes/release-notes/k8s-6-2-10-45-2022-07.md" >}})** release.
+  **Do not** upgrade to this 6.2.10-34 release if you are an **OpenShift** customer and **also use modules**. Instead, **use the [6.2.10-45]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-45-2022-07" >}})** release.
 
   There was a change in 6.2.10-34 to a new RHEL 8 base image for the Redis Server image. Due to binary differences in modules between the two operating systems, you cannot directly update RHEL 7 clusters to RHEL 8 when those clusters host databases using modules.