Merge pull request #3183 from EnterpriseDB/matthew_gwillam_efm_01_clu…

…ster_properties_patch

updating 01_cluster_properties.mdx and 07_using_efm_utility.mdx

product_docs/docs/efm/4/04_configuring_efm/01_cluster_properties.mdx

@@ -555,7 +555,7 @@ stop.failed.primary=true
 
 <div id="primary_shutdown_as_failure" class="registered_link"></div>
 
-Use the `primary.shutdown.as.failure` property to treat any shutdown of the Failover Manager agent on the primary node as a failure. If this property is set to `true` and the primary agent is shut down, the rest of the cluster treats the shutdown as a failure. This includes any proper shutdown of the agent such as a shutdown of the whole node. None of the timeout properties apply in this case: when the agent exits, the rest of the cluster is notified immediately. After the agent exits, the rest of the cluster performs the regular failover steps that happen in the case of agent failure. The regular failover steps include attempting to connect to the primary database, seeing if the VIP is reachable if used, and so on).
+Use the `primary.shutdown.as.failure` property to treat any shutdown of the Failover Manager agent on the primary node as a failure. If this property is set to `true` and the primary agent is shut down, the rest of the cluster treats the shutdown as a failure. This includes any proper shutdown of the agent such as a shutdown of the whole node. None of the timeout properties apply in this case: when the agent exits, the rest of the cluster is notified immediately. After the agent exits, the rest of the cluster performs [checks](../11_supported_scenarios/#primary_agent_exits) that happen in the case of a primary agent failure. The [checks](../11_supported_scenarios/#primary_agent_exits) include attempting to connect to the primary database, seeing if the VIP is reachable if used, and so on).
 
 -   If the database is reached, a notification is sent informing you of the agent status.
 -   If the database isn't reached, a failover occurs.

product_docs/docs/efm/4/07_using_efm_utility.mdx

@@ -108,7 +108,7 @@ Invoke the `efm encrypt` command to encrypt the database password before includi
 
 The `efm promote` command instructs Failover Manager to perform a manual failover of standby to primary.
 
-Attempt manual promotion only if the status command reports that the cluster includes a standby node that is up to date with the primary. If there is no up-to-date standby, Failover Manager prompts you before continuing.
+Attempt a manual promotion only during a maintenance window for your database cluster and if the status command reports that all standbys in the cluster are up to date with the primary.
 
 Include the `–switchover` clause to promote a standby node and reconfigure a primary node as a standby node. Include the `-sourcenode` keyword, and specify a node address to indicate the node whose recovery settings to copy to the old primary node, which makes it a standby. Include the `-quiet` keyword to suppress notifications during the switchover process. Include the `-noscripts` keyword to instruct Failover Manager not to invoke fencing or post-promotion scripts.