fix relrefs (#1684)

Author: kaitlynmichael

content/operate/kubernetes/deployment/openshift/openshift-cli.md

@@ -21,7 +21,7 @@ Use these steps to set up a Redis Enterprise Software cluster with OpenShift.
 To see which version of Redis Enterprise for Kubernetes supports your OpenShift version, see [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}).
 
 {{<note>}}
-If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/enable-privileged-mode" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.
+If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.
 {{</note>}}
 
 ## Deploy the operator
@@ -75,7 +75,7 @@ DO NOT modify or delete the StatefulSet created during the deployment process. D
 
 ## Security context constraints
 
-Versions 7.22.0-6 and later run in without permissions to [allow automatic resource adjustment]({{<relref "content/operate/kubernetes/security/allow-resource-adjustment">}}). If you use the recommended default security constraints, remove the existing `redis-enterprise-scc-v2` SCC and unbind it from the REC service account after upgrading.
+Versions 7.22.0-6 and later run in without permissions to [allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}). If you use the recommended default security constraints, remove the existing `redis-enterprise-scc-v2` SCC and unbind it from the REC service account after upgrading.
 
 ## Create a Redis Enterprise cluster custom resource
 
@@ -84,7 +84,7 @@ Versions 7.22.0-6 and later run in without permissions to [allow automatic resou
     You can rename the file to `<your_cluster_name>.yaml`, but it is not required. Examples below use `<rec_rhel>.yaml`. [Options for Redis Enterprise clusters]({{< relref "/operate/kubernetes/reference/redis_enterprise_cluster_api" >}}) has more info about the Redis Enterprise cluster (REC) custom resource, or see the [Redis Enterprise cluster API]({{<relref "/operate/kubernetes/reference/redis_enterprise_cluster_api">}}) for a full list of options.
 
     {{<note>}}
-If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/enable-privileged-mode" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.
+If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.
     {{</note>}}
 
     The REC name cannot be changed after cluster creation.

content/operate/kubernetes/deployment/openshift/openshift-operatorhub.md

@@ -12,7 +12,7 @@ weight: 70
 ---
 You can deploy Redis Enterprise for Kubernetes from the Red Hat OpenShift CLI. You can also use a UI, [OperatorHub](https://docs.openshift.com/container-platform/4.11/operators/index.html) (Red Hat) to install operators and create custom resources.
 
-{{<note>}}If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/enable-privileged-mode" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.{{</note>}}
+{{<note>}}If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.{{</note>}}
 
 To see which version of Redis Enterprise for Kubernetes supports your OpenShift version, see [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}).
 
@@ -46,7 +46,7 @@ To see which version of Redis Enterprise for Kubernetes supports your OpenShift
 
 ## Security context constraints
 
-Versions 7.22.0-6 and later run in without permissions to [allow automatic resource adjustment]({{<relref "content/operate/kubernetes/security/allow-resource-adjustment">}}). If you use the recommended default security constraints, remove the existing `redis-enterprise-scc-v2` SCC and unbind it from the REC service account after upgrading.
+Versions 7.22.0-6 and later run in without permissions to [allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}). If you use the recommended default security constraints, remove the existing `redis-enterprise-scc-v2` SCC and unbind it from the REC service account after upgrading.
 
 ## Create Redis Enterprise custom resources
 
@@ -56,7 +56,7 @@ The **Installed Operators**->**Operator details** page shows the provided APIs:
 Use the YAML view to create a custom resource file or let OperatorHub generate the YAML file for you by specifying your configuration options in the form view.
 
 {{<note>}}
-If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/enable-privileged-mode" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.
+If you suspect your file descriptor limits are below 100,000, you must either manually increase limits or [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}). Most major cloud providers and standard container runtime configurations set default file descriptor limits well above the minimum required by Redis Enterprise. In these environments, you can safely run without enabling automatic resource adjustment.
 {{</note>}}
 
 <note> The REC name cannot be changed after cluster creation.</note>

content/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-11-june2025.md

@@ -13,7 +13,7 @@ weight: 1
 
 ## Highlights
 
-This is a maintenance release to support [Redis Enterprise Software version 7.22.0-95]({{<relref "/operate/rs/release-notes/rs-7-22-0-releases/">}}). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-7 (April 2025)]({{<relref "/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-7-april2025">}}).
+This is a maintenance release to support [Redis Enterprise Software version 7.22.0-95]({{< relref "/operate/rs/release-notes/rs-7-22-releases/" >}}). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-7 (April 2025)]({{< relref "/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-7-april2025" >}}).
 
 ## Downloads
 

content/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-7-april2025.md

@@ -32,7 +32,7 @@ Redis Enterprise for Kubernetes 7.22.0-7 is a feature release that includes enha
 
 ## Breaking changes
 
-By default, the operator no longer sets additional Linux capabilities in the security context. If your deployment requires capabilities such as `SYS_RESOURCE`, see [Enable privileged mode]({{<relref "/operate/kubernetes/security/enable-privileged-mode">}}).
+By default, the operator no longer sets additional Linux capabilities in the security context. If your deployment requires capabilities such as `SYS_RESOURCE`, see [Allow automatic resource adjustment]({{< relref "/operate/kubernetes/security/allow-resource-adjustment" >}}).
 
 ## Supported distributions
 

content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-april2025.md

@@ -26,4 +26,4 @@ For supported distributions, known limitations, and API changes, see [Redis Ente
 
 ## Known limitations
 
-See [7.8.6 releases]({{<relref "release-notes/7-8-6-releases">}}) for information on known limitations.
+See [7.8.6 releases]({{< relref "/operate/kubernetes/release-notes/7-8-6-releases/" >}}) for information on known limitations.

content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-march2025.md

@@ -15,7 +15,7 @@ weight: 50
 
 Redis Enterprise for Kubernetes 7.8.6-1 is a feature release that includes enhancements, bug fixes, platform updates, and support for [Redis Software 7.8.6-13]({{<relref "/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-13.md">}}).
 
-This release also includes the ability to [install the operator using Helm]({{<relref "deployment/helm.md">}}).
+This release also includes the ability to [install the operator using Helm]({{< relref "/operate/kubernetes/deployment/helm" >}}).
 
 Support for Helm is currently in public preview and is not supported on production workloads. Only new installations of the Redis operator are supported at this time.
 
@@ -93,4 +93,4 @@ Any distribution not listed below is not supported for production workloads.
 
 ## Known limitations
 
-See [7.8.6 releases]({{<relref "release-notes/7-8-6-releases">}}) for information on known limitations.
+See [7.8.6 releases]({{< relref "/operate/kubernetes/release-notes/7-8-6-releases/" >}}) for information on known limitations.

content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-may2025.md

@@ -24,4 +24,4 @@ For supported distributions, known limitations, and API changes, see [Redis Ente
 
 ## Known limitations
 
-See [7.8.6 releases]({{<relref "release-notes/7-8-6-releases">}}) for information on known limitations.
+See [7.8.6 releases]({{< relref "/operate/kubernetes/release-notes/7-8-6-releases/" >}}) for information on known limitations.

content/operate/kubernetes/upgrade/openshift-cli.md

@@ -132,7 +132,7 @@ redis-enterprise-operator   1/1     1            1           0m36s
 
 Upgrades to versions 7.22.0-6 and later run in **unprivileged mode** without any additional permissions or capabilities. If you don't specifally require additional capabilities, we recommend you maintain the default unprivileged mode, as its more secure. After upgrading, remove the existing `redis-enterprise-scc-v2` SCC and unbind it from the REC service account.
 
-To enable privileged mode, see [Enable privileged mode > OpenShift upgrades]({{<relref "/operate/kubernetes/security/enable-privileged-mode#openshift-upgrades">}}).
+To enable automatic resource adjustment, see [Allow automatic resource adjustment > OpenShift upgrades]({{< relref "/operate/kubernetes/security/allow-resource-adjustment#openshift-upgrades" >}}).
 
 ## Upgrade the Redis Enterprise cluster
 

content/operate/kubernetes/upgrade/upgrade-olm.md

@@ -77,7 +77,7 @@ You can monitor the upgrade from the **Installed Operators** page. A new Redis E
 
 Upgrades to versions 7.22.0-6 and later run in **unprivileged mode** without any additional permissions or capabilities. If you don't specifally require additional capabilities, we recommend you maintain the default unprivileged mode, as its more secure. After upgrading, remove the existing `redis-enterprise-scc-v2` SCC and unbind it from the REC service account.
 
-To enable privileged mode, see [Enable privileged mode > OpenShift upgrades]({{<relref "/operate/kubernetes/security/enable-privileged-mode#openshift-upgrades">}}).
+To enable automatic resource adjustment, see [Allow automatic resource adjustment > OpenShift upgrades]({{< relref "/operate/kubernetes/security/allow-resource-adjustment#openshift-upgrades" >}}).
 
 ## Upgrade the Redis Enterprise cluster