updates

docs/reference/reference-architectures/hot-frozen.asciidoc

@@ -1,7 +1,7 @@
 [[hot-frozen-architecture]]
 == Hot / Frozen - High Availability
 
-The Hot / Frozen – High Availability architecture is cost optimized for large time-series datasets. In this architecture, the hot tier is primarily used for indexing and immediate searching (<1 day), https://www.elastic.co/guide/en/elasticsearch/reference/current/searchable-snapshots.html[searchable snapshots] are taken from hot to the object store using Index and Snapshot lifecycle management. Any amount of the snapshot data can be automatically cached in the frozen tier for high speed search. Data in the object store is accessible through the nodes in the frozen tier.
+The Hot / Frozen high availability architecture is cost optimized for large time-series datasets. In this architecture, the hot tier is primarily used for indexing, searching, and continuity for automated processes. https://www.elastic.co/guide/en/elasticsearch/reference/current/searchable-snapshots.html[Searchable snapshots] are taken from hot into the object store and then cached to any desired volume in the Frozen tier. Data in the Object Store is indexed for fast retrieval and accessed on-demand from the Frozen nodes. Index and Snapshot lifecycle management are used to automate this process. 
 
 This architecture is ideal for time-series use cases, such as Observability or Security, that do not require updating. All the necessary components of the Elastic Stack are included and this is not intended for sizing workloads, but rather as a basis to ensure your cluster is ready to handle any desired workload with resiliency. A very high level representation of data flow is included, and for more detail around ingest architecture see our https://www.elastic.co/guide/en/ingest/current/use-case-arch.html[ingest architectures] documentation.