updates

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

@@ -1,5 +1,5 @@
 [[elastic-cloud-architecture]]
-=== Elastic Cloud - Multi-Availability Zone
+=== Elastic Cloud - Multi-availability zone
 
 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

@@ -1,11 +1,21 @@
 [[reference-architectures]]
 = Reference architectures
 
-Elasticsearch Reference Architectures serve as blueprints for deploying, managing, and optimizing Elasticsearch clusters tailored to different use cases. These architectures are designed by Solutions Architectures to provide standardized, proven solutions that help users with best practices for infrastructure setup, data ingestion, indexing, search performance, and high availability. Whether you're handling logs, metrics, or sophisticated search applications, these reference architectures ensure scalability, reliability, and efficient resource utilization. By leveraging these guidelines, organizations can confidently deploy Elasticsearch, achieving optimal performance while minimizing risks and complexities.
+Elasticsearch reference architectures serve as blueprints for deploying, managing, and optimizing Elasticsearch clusters tailored to different use cases. Whether you're handling logs, metrics, or sophisticated search applications, these reference architectures ensure scalability, reliability, and efficient resource utilization. By leveraging these guidelines, organizations can confidently deploy Elasticsearch, minimizing risks and complexities.
+
+These architectures are designed by Solutions Architectures to provide standardized, proven solutions that help users with best practices for:
+
+* Infrastructure setup
+* Data ingestion
+* Indexing
+* Search performance
+* High availability. 
+
+
 
 TIP: You can host {es} on your own hardware or send your data to {es} on {ecloud} or serverless. 
 
-These reference architectures are recommendations and should be adapted to fit your specific environment and needs. Each solution can vary based on the unique requirements and conditions of your setup.
+These reference architectures are recommendations and should be adapted to fit your specific environment and needs. Each solution can vary based on the unique requirements and conditions of your deployment. In these architectures we discuss about how to deploy cluster components. For information about designing ingest architectures to feed content into your cluster, refer to https://www.elastic.co/guide/en/ingest/current/use-case-arch.html[Ingest architectures]
 
 [discrete]
 [[reference-architectures-time-series-2]]
@@ -49,12 +59,12 @@ a|
 |
 |===
 
-[discrete]
-[[reference-architectures-ingest-architectures]]
-=== Ingest architectures
+include::general-cluster-guidance.asciidoc[]
 
-Additionally, we have architectures specifically tailored to the ingestion portion of your architecture and these can be found at, https://www.elastic.co/guide/en/ingest/current/use-case-arch.html[Ingest architectures]
+include::multi-region-two-datacenter-architecture.asciidoc[]
 
-include::general-cluster-guidance.asciidoc[]
+include::elastic-cloud-architecture.asciidoc[]
+
+include::self-managed-single-datacenter.asciidoc[]
 
-include::architecture-diagrams.asciidoc[]
+include::three-availability-zones.asciidoc[]

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

@@ -1,5 +1,5 @@
 [[multi-region-two-datacenter-architecture]]
-=== Multi-Region - Two Datacenters
+=== Multi-region - two datacenters
 
 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,5 @@
 [[self-managed-single-datacenter]]
-=== Self Managed - Single Datacenter
+=== Self managed - single datacenter
 
 This architecture ensures high availability during normal operations and node maintenance.