DOC-7104: Migrate content/operate/rs/references/ (excl. rest-api) to render hooks

content/operate/rs/references/alerts/_index.md

@@ -24,10 +24,9 @@ Configured alerts are shown:
 - In the **log**
 - In email notifications, if you configure [email alerts](#send-alerts-by-email)
 
-{{< note >}}
-If you enable alerts for "Node joined" or "Node removed" actions,
-you must also enable "Receive email alerts" so that the notifications are sent.
-{{< /note >}}
+> [!NOTE]
+> If you enable alerts for "Node joined" or "Node removed" actions,
+> you must also enable "Receive email alerts" so that the notifications are sent.
 
 To enable alerts for a cluster:
 
@@ -55,8 +54,8 @@ To enable alerts for a database:
 To send cluster and database alerts by email:
 
 1. In **Cluster > Alert Settings**, click **Edit**.
-1. Select **Set an email** to configure the [email server settings]({{< relref "/operate/rs/clusters/configure/cluster-settings#configure-email-server-settings" >}}).
+1. Select **Set an email** to configure the [email server settings](/content/operate/rs/clusters/configure/cluster-settings.md#configure-email-server-settings).
 1. In **Configuration** for the database, click **Edit**.
 1. Select the **Alerts** section to open it.
 1. Select **Receive email alerts** and click **Save**.
-1. In **Access Control**, select the [database and cluster alerts]({{< relref "/operate/rs/security/access-control/create-users#add-users" >}}) that you want each user to receive.
+1. In **Access Control**, select the [database and cluster alerts](/content/operate/rs/security/access-control/create-users.md#add-users) that you want each user to receive.

content/operate/rs/references/alerts/alerts-v1-to-v2.md

@@ -10,7 +10,7 @@ linkTitle: Transition cluster manager alerts to Prometheus
 weight: 50
 ---
 
-As Redis Software transitions from the [deprecated monitoring system]({{<relref "/operate/rs/monitoring/v1_monitoring">}}) to the [new metrics stream engine]({{<relref "/operate/rs/monitoring/metrics_stream_engine">}}), some internal cluster manager alerts were deprecated in favor of external monitoring solutions.
+As Redis Software transitions from the [deprecated monitoring system](/content/operate/rs/monitoring/v1_monitoring.md) to the [new metrics stream engine](/content/operate/rs/monitoring/metrics_stream_engine/_index.md), some internal cluster manager alerts were deprecated in favor of external monitoring solutions.
 
 You can use the following table to transition from the deprecated alerts and set up equivalent alerts in Prometheus with [PromQL (Prometheus Query Language)](https://prometheus.io/docs/prometheus/latest/querying/basics/):
 

content/operate/rs/references/cli-utilities/_index.md

@@ -23,9 +23,8 @@ Administrators can use these CLI tools to manage and test a Redis Software clust
 
 The `/opt/redislabs/bin/` directory also contains utilities used internally by Redis Software and for troubleshooting.
 
-{{<warning>}}
-Do not use these tools for normal operations.
-{{</warning>}}
+> [!WARNING]
+> Do not use these tools for normal operations.
 
 | Utility | Description |
 |---------|-------------|

content/operate/rs/references/cli-utilities/crdb-cli/_index.md

@@ -11,7 +11,7 @@ linkTitle: crdb-cli (manage Active-Active)
 weight: $weight
 ---
 
-An [Active-Active database]({{< relref "/operate/rs/databases/active-active/_index.md" >}}) (also known as CRDB or conflict-free replicated database)
+An [Active-Active database](/content/operate/rs/databases/active-active/_index.md) (also known as CRDB or conflict-free replicated database)
 replicates your data across Redis Software clusters located in geographically distributed regions.
 Active-Active databases allow read-write access in all locations, making them ideal for distributed applications that require fast response times and disaster recovery.
 
@@ -20,7 +20,7 @@ Each cluster that hosts an instance is called a **participating cluster**.
 
 An Active-Active database requires two or more participating clusters.
 Each instance is responsible for updating the instances that reside on other participating clusters with the transactions it receives.
-Write conflicts are resolved using [conflict-free replicated data types]({{< relref "/operate/rs/databases/active-active" >}}) (CRDTs).
+Write conflicts are resolved using [conflict-free replicated data types](/content/operate/rs/databases/active-active/_index.md) (CRDTs).
 
 To programmatically maintain an Active-Active database and its instances, you can use the `crdb-cli` command-line tool.
 
@@ -44,6 +44,6 @@ By default, the command runs immediately and displays the result in the output.
 
 If you use the <nobr>`--no-wait`</nobr> flag, the command runs in the background so that your application is not delayed by the response.
 
-Use the [`crdb-cli task` commands]({{< relref "/operate/rs/references/cli-utilities/crdb-cli/task/" >}}) to manage Active-Active database tasks.
+Use the [`crdb-cli task` commands](/content/operate/rs/references/cli-utilities/crdb-cli/task/_index.md) to manage Active-Active database tasks.
 
 For each `crdb-cli` command, you can use <nobr>`--help`</nobr> for additional information about the command.

content/operate/rs/references/cli-utilities/crdb-cli/crdb/add-instance.md

@@ -24,7 +24,7 @@ crdb-cli crdb add-instance --crdb-guid <guid>
 | Parameter | Value   | Description |
 |-----------|---------|-------------|
 | crdb-guid | string  | The GUID of the database (required) |
-| instance fqdn=\<cluster_fqdn\>,username=\<username\>,password=\<password\>,url=https://\<hostname-or-IP\>:9443,replication_endpoint=\<hostname-or-IP\>:\<port\>,replication_tls_sni=\<hostname\> | strings | The connection information for the new participating cluster (required)<br/><br/>**Required:**<br/>• `fqdn` - Cluster fully qualified domain name<br/>• Either a username and password, or certificate credentials:<br/>&nbsp;&nbsp;- `username` and `password` - Cluster username and password<br/>&nbsp;&nbsp;- `client_cert` and `client_key` - Client certificate and its private key, as PEM strings<br/><br/>Don't provide both for the same cluster. The command fails with `Use either username/password or client_cert/client_key/trusted_ca, not both`.<br/><br/>**Optional:**<br/>• `trusted_ca` - CA that validates the API certificate the peer cluster presents, as a PEM string. Only valid with certificate credentials. If you omit it, the cluster uses the certificates in its `mtls_trusted_ca.pem` file.<br/>• `url` - URL to access the cluster's REST API<br/>• `replication_endpoint` - Address to access the database instance for peer replication<br/>• `replication_tls_sni` - Cluster [Server Name Indication (SNI)](https://en.wikipedia.org/wiki/Server_Name_Indication) hostname for TLS connections<br/><br/>See [Certificate-based authentication for cluster management]({{<relref "/operate/rs/security/certificates/certificate-based-authentication#certificate-based-authentication-for-cluster-management">}}). |
+| instance fqdn=\<cluster_fqdn\>,username=\<username\>,password=\<password\>,url=https://\<hostname-or-IP\>:9443,replication_endpoint=\<hostname-or-IP\>:\<port\>,replication_tls_sni=\<hostname\> | strings | The connection information for the new participating cluster (required)<br/><br/>**Required:**<br/>• `fqdn` - Cluster fully qualified domain name<br/>• Either a username and password, or certificate credentials:<br/>&nbsp;&nbsp;- `username` and `password` - Cluster username and password<br/>&nbsp;&nbsp;- `client_cert` and `client_key` - Client certificate and its private key, as PEM strings<br/><br/>Don't provide both for the same cluster. The command fails with `Use either username/password or client_cert/client_key/trusted_ca, not both`.<br/><br/>**Optional:**<br/>• `trusted_ca` - CA that validates the API certificate the peer cluster presents, as a PEM string. Only valid with certificate credentials. If you omit it, the cluster uses the certificates in its `mtls_trusted_ca.pem` file.<br/>• `url` - URL to access the cluster's REST API<br/>• `replication_endpoint` - Address to access the database instance for peer replication<br/>• `replication_tls_sni` - Cluster [Server Name Indication (SNI)](https://en.wikipedia.org/wiki/Server_Name_Indication) hostname for TLS connections<br/><br/>See [Certificate-based authentication for cluster management](/content/operate/rs/security/certificates/certificate-based-authentication.md#certificate-based-authentication-for-cluster-management). |
 | compression | 0-6 | The level of data compression: <br /><br > 0 = No compression <br /><br > 6 = High compression and resource load (Default: 3) |
 | wait | | Prevents `crdb-cli` from running another command before this command finishes |
 | no-wait | | `crdb-cli` can run another command before this command finishes |