more updates

Author: georgewallace

deploy-manage/distributed-architecture.md

@@ -1,6 +1,9 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/_data_store_architecture.html
+applies_to:
+  stack:
+  serverless:
 ---
 
 % Update the overview so Kibana is represented too.

deploy-manage/distributed-architecture/discovery-cluster-formation.md

@@ -5,6 +5,8 @@ applies_to:
   stack:
 ---
 
+% Discovery and cluster formation content (7 pages): add introductory note to specify that the endpoints/settings are possibly for self-managed only, and review the content.
+
 # Discovery and cluster formation [modules-discovery]
 
 The discovery and cluster formation processes are responsible for discovering nodes, electing a master, forming a cluster, and publishing the cluster state each time it changes.

deploy-manage/distributed-architecture/kibana-tasks-management.md

@@ -11,7 +11,7 @@ mapped_pages:
 * **Scaling**: Multiple {{kib}} instances can read from and update the same task queue in {{es}}, allowing the work load to be distributed across instances. If a {{kib}} instance no longer has capacity to run tasks, you can increase capacity by adding additional {{kib}} instances.
 * **Load Balancing**: Task Manager is equipped with a reactive self-healing mechanism, which allows it to reduce the amount of work it executes in reaction to an increased load related error rate in {{es}}. Additionally, when Task Manager experiences an increase in recurring tasks, it attempts to space out the work to better balance the load.
 
-::::{important} 
+::::{important}
 Task definitions for alerts and actions are stored in the index called `.kibana_task_manager`.
 
 You must have at least one replica of this index for production deployments.