updates with new titles

docs/reference/reference-architectures/elastic-cloud-architecture.asciidoc

@@ -1,5 +1,8 @@
 [[elastic-cloud-architecture]]
-=== Elastic Cloud - Multi-availability zone
+=== Elastic Cloud Hot-Frozen Architecture for Time Series Data
+++++
+<titleabbrev>Architecture: Elastic Cloud hot-frozen</titleabbrev>
+++++
 
 The Hot-Frozen Elasticsearch cluster architecture is cost optimized for large time-series datasets while keeping all of the data **fully searchable**. There is no need to "re-hydrate" archived data. In this architecture, the hot tier is primarily used for indexing and immediate searching (1-3 days) with a majority of the search being handled by the frozen tier. Since the data is moved to searchable snapshots in an object store, the cost of keeping all of the data searchable is dramatically reduced.
 

docs/reference/reference-architectures/index.asciidoc

@@ -58,10 +58,10 @@ a|
 |
 |===
 
-include::multi-region-two-datacenter-architecture.asciidoc[leveloffset=-1]
+include::multi-region-two-datacenter-architecture.asciidoc[]
 
-include::elastic-cloud-architecture.asciidoc[leveloffset=-1]
+include::elastic-cloud-architecture.asciidoc[]
 
-include::self-managed-single-datacenter.asciidoc[leveloffset=-1]
+include::self-managed-single-datacenter.asciidoc[]
 
-include::three-availability-zones.asciidoc[leveloffset=-1]
+include::three-availability-zones.asciidoc[]

docs/reference/reference-architectures/multi-region-two-datacenter-architecture.asciidoc

@@ -1,5 +1,8 @@
 [[multi-region-two-datacenter-architecture]]
-=== Multi-region - two datacenters
+=== Self-managed hot-frozen multi-region architecture for time series data
+++++
+<titleabbrev>Architecture: Self-managed - two datacenter</titleabbrev>
+++++
 
 This article defines a scalable and highly available architecture for Elasticsearch using two datacenters in separate geographical regions. 
 

docs/reference/reference-architectures/self-managed-single-datacenter.asciidoc

@@ -1,5 +1,8 @@
 [[self-managed-single-datacenter]]
-=== Self managed - single datacenter
+=== Self-managed hot-frozen multi-region architecture for time series data
+++++
+<titleabbrev>Architecture: Self-managed - multi-region</titleabbrev>
+++++
 
 This architecture is designed to ensure high availability during normal operations and node maintenance. It reduces cost by leveraging the frozen tier as soon as it makes sense from an ingest and most frequently read documents perspective. It significantly reduces the likelihood of hot-spotting due to the sharding strategy. Additionally it eliminates network and disk overhead caused by rebalancing attempts that would occur during maintenance due to setting forced awareness. For more information on elements of this architecture, see https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-design-large-clusters.html#high-availability-cluster-design-two-zones[Resilience in larger clusters - Two-zone clusters]. 
 

docs/reference/reference-architectures/three-availability-zones.asciidoc

@@ -1,5 +1,8 @@
 [[three-availability-zones]]
-=== Three availability zones
+=== Self-managed hot-frozen three availability zone architecture for time series data
+++++
+<titleabbrev>Architecture: Self-managed - one region</titleabbrev>
+++++
 
 This article outlines a scalable and highly available architecture for Elasticsearch using three availability zones. The architecture encompasses all essential components of the Elastic Stack and serves as a foundational blueprint to ensure your deployment is resilient and ready to handle any desired workload. While this overview includes high-level representations of data flow, detailed implementation will be covered in subsequent documentation.