AutoOps for self-managed FAQ and related updates (#4436)

<!--
Thank you for contributing to the Elastic Docs! 🎉
Use this template to help us efficiently review your contribution.
-->

## Summary
Closes elastic/opex-product#684 and
elastic/autoops-services#3008

## Generative AI disclosure
<!--
To help us ensure compliance with the Elastic open source and
documentation guidelines, please answer the following:
-->
1. Did you use a generative AI (GenAI) tool to assist in creating this
contribution?
- [ ] Yes  
- [x] No  
<!--
2. If you answered "Yes" to the previous question, please specify the
tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used:
-->

Author: wajihaparvez

deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md

@@ -107,7 +107,9 @@ macOS is not a supported platform for installing {{agent}} to connect to AutoOps
 :::
 
 :::{important} 
-Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes.
+Each cluster that you want to connect requires a new, dedicated {{agent}}. You must install the agent even if you already have an existing one for other purposes.
+
+You only need to install the agent once per cluster. 
 :::
 
 To learn more about how AutoOps securely gathers data from your cluster, refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#data-gathering).
@@ -265,9 +267,7 @@ Complete the following steps to run the command:
 
 It might take a few minutes for your cluster details to be validated and the first metrics to be shipped to AutoOps.
 
-If the connection is unsuccessful, an error message is displayed with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md#potential-errors).
-
-Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us).
+If the connection is unsuccessful, an error message is displayed with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md#potential-errors). Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us).
 
 To uninstall the agent, refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md).
 
@@ -303,7 +303,9 @@ By default, each cluster has a name made up of a string of characters, but you c
 
 To connect more clusters, repeat the steps to [connect to AutoOps](#connect-to-autoops).
 
-You can use the same installation command to connect multiple clusters, but each cluster needs a separate, dedicated {{agent}}.
+Or, if you don't need to change any of your [configuration settings](#configure-agent) for the additional clusters, you can skip ahead and reuse the same installation command to connect them.
+
+Remember that you must run the command to install a separate, dedicated {{agent}} for each cluster. You only need to install the agent once per cluster. 
 
 ### Disconnect a cluster
 

deploy-manage/monitor/autoops/ec-autoops-faq.md

@@ -41,6 +41,8 @@ Whether you are using AutoOps in your [{{ech}} deployment](/deploy-manage/monito
 * [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech)
 * [Can I use macOS to set up AutoOps for my self-managed clusters?](#macos-install)
 * [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address)
+* [Do I have to install {{agent}} separately for each node in my cluster?](#agent-nodes)
+* [Do I have to re-run the installation wizard to connect more clusters?](#connect-more-clusters)
 
 **Collected metrics and data in AutoOps for self-managed clusters**
 * [Where are metrics stored in AutoOps for self-managed clusters?](#sm-autoops-metrics-storage)
@@ -116,6 +118,12 @@ $$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable t
 
 :   For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md).
 
+$$$agent-nodes$$$ **Do I have to install {{agent}} separately for each node in my cluster?**
+:    No, to run AutoOps in your self-managed environment, you only have to install the agent once per cluster.
+
+$$$connect-more-clusters$$$**Do I have to re-run the installation wizard to connect more clusters?**
+:   Not necessarily. Refer to [Connect additional clusters](../autoops/cc-connect-self-managed-to-autoops.md#connect-additional-clusters) for more information.
+
 ### Collected metrics and data in AutoOps for self-managed clusters
 
 $$$sm-autoops-metrics-storage$$$ **Where are metrics stored in AutoOps for self-managed clusters?**