Update hdinsight-upgrade-cluster.md

Updated missing bookmark

Author: nicjohn79

articles/hdinsight/hdinsight-upgrade-cluster.md

@@ -50,7 +50,7 @@ For more information about database backup and restore, see [Recover a database
 As mentioned above, Microsoft recommends that HDInsight clusters be regularly migrated to the latest version in order to take advantage of new features and fixes. Please see the following list of reasons we would request that a cluster be deleted and redeployed:
 
 * The cluster version is [Retired](hdinsight-retired-versions.md) or in [Basic support](hdinsight-36-component-versioning.md) and you are having a cluster issue that would be resolved with a newer version.
-* The root cause of a cluster issue is determined to be related to an undersized VM. [View Microsoft's recommended node configuration](hdinsight-supported-node-configuration.md#all-supported-regions-except-brazil-south-and-japan-west).
+* The root cause of a cluster issue is determined to be related to an undersized VM. [View Microsoft's recommended node configuration](hdinsight-supported-node-configuration.md).
 * A customer opens a support case and the Microsoft engineering team determines the issue has already been fixed in a newer cluster version.
 * A default metastore database (Ambari, Hive, Oozie, Ranger) has reached it’s utilization limit. Microsoft will ask you to recreate the cluster using a [custom metastore](hdinsight-use-external-metadata-stores.md#custom-metastore) database.
 * The root cause of a cluster issue is due to an **Unsupported Operation**. Here are some of the common unsupported operations: