Fix wording

Author: vishaangelova

reference/fleet/remote-elasticsearch-output.md

@@ -40,10 +40,10 @@ To configure a remote {{es}} cluster for your {{agent}} data:
     ::::{dropdown} Find the remote host address of the remote cluster
     :open:
     1. In the remote cluster (Cluster B), open {{kib}}, and search for **Fleet settings** in the search bar. Select **Fleet/Settings** in the results.
-    2. In the **Outputs** section, copy the `Hosts` value of the `default` output. If the value is not visible in full, edit the `default` output to display the full value.
+    2. In the **Outputs** section, copy the `Hosts` value of the default {{es}} output. If the value is not visible in full, edit the default {{es}} output to display the full value.
     3. Back in your main cluster (Cluster A), paste the value you copied into the **Hosts** field of the remote output configuration.
 
-    Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page, scroll to the the **Remote cluster parameters** section, and copy the **Proxy Address**.
+    Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page, scroll to the the **Remote cluster parameters** section, and copy the **Proxy Address** to use it in the `Hosts` field of the remote output configuration.
     ::::
 
 5. In the **Service Token** field, add a service token to access the remote cluster (Cluster B). 
@@ -117,10 +117,10 @@ This feature is only available with certain subscriptions. For more information,
     ::::{dropdown} Find the remote host address of the remote cluster
     :open:
     1. In the remote cluster (Cluster B), open {{kib}}, and search for **Fleet settings** in the search bar. Select **Fleet/Settings** in the results.
-    2. In the **Outputs** section, copy the `Hosts` value of the `default` output. If the value is not visible in full, edit the `default` output to display the full value.
+    2. In the **Outputs** section, copy the `Hosts` value of the default {{es}} output. If the value is not visible in full, edit the default {{es}} output to display the full value.
     3. Back in your main cluster (Cluster A), paste the value you copied into the **Hosts** field of the remote output configuration.
 
-    Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page, scroll to the the **Remote cluster parameters** section, and copy the **Proxy Address**.
+    Alternatively, for cloud deployments, you can navigate to your deployment's `deployments/<deployment_id>/security` page, scroll to the the **Remote cluster parameters** section, and copy the **Proxy Address** to use it in the `Hosts` field of the remote output configuration.
     ::::
 
 4. Enable **Synchronize integrations**.