Update and rename sticky-endpoints.md to replica-aware-routing.md

Renamed feature to replica-aware routing

Author: krithika-ch

docs/en/cloud/manage/sticky-endpoints.md renamed to docs/en/cloud/manage/replica-aware-routing.md

@@ -1,15 +1,15 @@
 ---
-title: Sticky Endpoints
-slug: /en/manage/sticky-endpoints
-description: How to use Sticky Endpoints to increase cache re-use
-keywords: [cloud, sticky endpoints, sticky, endpoints, sticky routing, routing]
+title: Replica-aware routing
+slug: /en/manage/replica-aware-routing
+description: How to use Replica-aware routing to increase cache re-use
+keywords: [cloud, sticky endpoints, sticky, endpoints, sticky routing, routing, replica aware routing]
 ---
 
-# Sticky Endpoints (Private Preview)
+# Replica-aware routing (Private Preview)
 
-Sticky endpoints (sticky routing) utilizes [Envoy proxy’s ring hash load balancing](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancers#ring-hash). The main purpose of sticky endpoints is to increase the chance of cache reuse. It does not guarantee isolation.
+Replica-aware routing (sticky sessions, routing) utilizes [Envoy proxy’s ring hash load balancing](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancers#ring-hash). The main purpose of replica-aware routing is to increase the chance of cache reuse. It does not guarantee isolation.
 
-When enabling sticky endpoints for a service, we allow a wildcard subdomain on top of the service hostname. For a service with the host name `abcxyz123.us-west-2.aws.clickhouse.cloud`, you can use any hostname which matches `*.sticky.abcxyz123.us-west-2.aws.clickhouse.cloud` to visit the service:
+When enabling replica-aware routing for a service, we allow a wildcard subdomain on top of the service hostname. For a service with the host name `abcxyz123.us-west-2.aws.clickhouse.cloud`, you can use any hostname which matches `*.sticky.abcxyz123.us-west-2.aws.clickhouse.cloud` to visit the service:
 
 |Example hostnames|
 |---|
@@ -21,16 +21,16 @@ When Envoy receives a hostname that matches such a pattern, it will compute the
 
 Note the original hostname will still use `LEAST_CONNECTION` load balancing, which is the default routing algorithm.
 
-## Limitations of Sticky Endpoints
+## Limitations of Replica-aware routing
 
-### Sticky endpoints do not guarantee isolation
+### Replica-aware routing does not guarantee isolation
 
 Any disruption to the service, e.g. server pod restarts (due to any reason like a version upgrade, crash, vertical scaling up, etc.), server scaled out / in, will cause a disruption to the routing hash ring. This will cause connections with the same hostname to land on a different server pod.
 
-### Sticky endpoints do not work out of the box with private link
+### Replica-aware routing does not work out of the box with private link
 
 Customers need to manually add a DNS entry to make name resolution work for the new hostname pattern. It is possible that this can cause imbalance in the server load if customers use it incorrectly.
 
-## Configuring Sticky Endpoints
+## Configuring Replica-aware routing
 
-To enable sticky endpoints, please contact [our support team](https://clickhouse.com/support).
+To enable Replica-aware routing, please contact [our support team](https://clickhouse.com/support).