Merge pull request #4828 from EnterpriseDB/efm/upgrade-text-removed

removed text that was not needed

product_docs/docs/efm/4/upgrading.mdx

@@ -26,9 +26,6 @@ Failover Manager provides a utility to assist you when upgrading a cluster manag
 
 3.  Modify the `.properties` and `.nodes` files for Failover Manager 4.7, specifying any new preferences. Use your choice of editor to modify any additional properties in the properties file (located in the `/etc/edb/efm-4.7` directory) before starting the service for that node. For detailed information about property settings, see [The cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties).
 
-!!! Note
-    `db.bin` is a required property. When modifying the properties file, ensure that the `db.bin` property specifies the location of the Postgres `bin` directory.
-
 4.  If you're using Eager Failover, you must disable it before stopping the Failover Manager cluster. For more information, see [Disabling Eager Failover](04_configuring_efm/06_configuring_for_eager_failover/#disabling-eager-failover).
 
 5. Use a version-specific command to stop the old Failover Manager cluster. For example, you can use the following command to stop a version 4.4 cluster:
@@ -54,9 +51,6 @@ Upgrade of files is finished. The owner and group for properties and nodes files
 
 If you're [using a Failover Manager configuration without sudo](04_configuring_efm/04_extending_efm_permissions/#running_efm_without_sudo), include the `-source` flag and specify the name of the directory in which the configuration files reside when invoking `upgrade-conf`. If the directory isn't the configuration default directory, the upgraded files are created in the directory from which the `upgrade-conf` command was invoked.
 
-!!! Note
-    If you're using a unit file, manually update the file to reflect the new Failover Manager service name when you perform an upgrade.
-
 ## Uninstalling Failover Manager
 
 !!! Note