docs: update names in references to renamed tutorials (#17261)

* docs: update names for tutorial references

* docs: update more names for tutorial references

website/content/api-docs/operator/index.mdx

@@ -17,7 +17,7 @@ If ACLs are enabled then a token with operator privileges may be required in
 order to use this interface. Check the [ACL Rules documentation](/consul/docs/security/acl/acl-rules#operator-rules)
 for more information.
 
-Check the [Outage Recovery](/consul/tutorials/datacenter-operations/recovery-outage) tutorial for some examples of
+Check the [Disaster recovery for Consul clusters](/consul/tutorials/datacenter-operations/recovery-outage) tutorial for some examples of
 how these capabilities are used.
 
 Please choose a sub-section in the navigation for more information.

website/content/commands/operator/index.mdx

@@ -20,7 +20,7 @@ order to use this command. Requests are forwarded internally to the leader
 if required, so this can be run from any Consul node in a cluster. See the
 [ACL Guide](/consul/tutorials/security/access-control-setup-production) for more information.
 
-See the [Outage Recovery](/consul/tutorials/datacenter-operations/recovery-outage) guide for some examples of how
+See the [Disaster recovery for Consul clusters](/consul/tutorials/datacenter-operations/recovery-outage) guide for some examples of how
 this command is used. For an API to perform these operations programmatically,
 please see the documentation for the [Operator](/consul/api-docs/operator)
 endpoint.

website/content/docs/architecture/improving-consul-resilience.mdx

@@ -31,7 +31,7 @@ Without a quorum, Consul experiences an outage:
 it cannot provide most of its capabilities because they rely on
 the availability of this state information.
 If Consul has an outage, normal operation can be restored by following the
-[outage recovery guide](/consul/tutorials/datacenter-operations/recovery-outage).
+[Disaster recovery for Consul clusters guide](/consul/tutorials/datacenter-operations/recovery-outage).
 
 If Consul is deployed with 3 servers, the quorum size is 2. The deployment can lose 1
 server and still maintain quorum, so it has a fault tolerance of 1.

website/content/docs/connect/cluster-peering/index.mdx

@@ -53,7 +53,7 @@ The following resources are available to help you use Consul's cluster peering f
 
 ### Tutorials
 
-- To learn how to peer clusters and connect services across peers in AWS Elastic Kubernetes Service (EKS) and Google Kubernetes Engine (GKE) environments, complete the [Consul Cluster Peering on Kubernetes tutorial](/consul/tutorials/developer-mesh/cluster-peering).
+- To learn how to peer clusters and connect services across peers in AWS Elastic Kubernetes Service (EKS) and Google Kubernetes Engine (GKE) environments, complete the [Connect services between Consul datacenters with cluster peering tutorial](/consul/tutorials/developer-mesh/cluster-peering).
 
 ### Usage documentation
 

website/content/docs/nia/index.mdx

@@ -11,7 +11,7 @@ Network Infrastructure Automation (NIA) enables dynamic updates to network infra
 
 CTS executes one or more automation tasks with the most recent service variable values from the Consul service catalog. Each task consists of a runbook automation written as a CTS compatible Terraform module using resources and data sources for the underlying network infrastructure. The `consul-terraform-sync` daemon runs on the same node as a Consul agent.
 
-CTS is available as an open source and enterprise distribution. Follow the [Network Infrastructure Automation introduction tutorial](/consul/tutorials/network-infrastructure-automation/consul-terraform-sync-intro?utm_source=docs) to get started with CTS OSS or read more about [CTS Enterprise](/consul/docs/nia/enterprise).
+CTS is available as an open source and enterprise distribution. Follow the [Automate your network configuration with Consul-Terraform-Sync tutorial](/consul/tutorials/network-infrastructure-automation/consul-terraform-sync-intro?utm_source=docs) to get started with CTS OSS or read more about [CTS Enterprise](/consul/docs/nia/enterprise).
 
 ## Use Cases
 

website/content/docs/upgrading/instructions/general-process.mdx

@@ -173,7 +173,7 @@ all of your servers attempting to kick off leadership elections endlessly withou
 reaching a quorum and electing a leader.
 
 Most of these problems can be solved by following the steps outlined in our
-[Outage Recovery](/consul/tutorials/datacenter-operations/recovery-outage) document.
+[Disaster recovery for Consul clusters](/consul/tutorials/datacenter-operations/recovery-outage) document.
 If you are still having trouble after trying the recovery steps outlined there,
 then the following options for further assistance are available:
 

website/content/docs/upgrading/upgrade-specific.mdx

@@ -1408,7 +1408,7 @@ the file. Consul 0.7 also uses a new, automatically-created raft/peers.info file
 to avoid ingesting the `peers.json` file on the first start after upgrading (the
 `peers.json` file is simply deleted on the first start after upgrading).
 
-Please be sure to review the [Outage Recovery tutorial](/consul/tutorials/datacenter-operations/recovery-outage)
+Please be sure to review the [Disaster recovery for Consul clusters tutorial](/consul/tutorials/datacenter-operations/recovery-outage)
 before upgrading for more details.
 
 ## Consul 0.6.4