Merge pull request #89905 from changeworld/patch-17

Fix typo

Author: Court72

articles/hdinsight/hbase/hbase-troubleshoot-pegged-cpu-region-server.md

@@ -36,7 +36,7 @@ If you are running HBase cluster v3.4, you might have been hit by a potential bu
 
 1. Depending on the data on cluster, it might take a few minutes to up to an hour for the cluster to reach stable state. The way you confirm the cluster reaches stable state is by either checking HMaster UI (all region servers should be active) from Ambari (refresh) or from headnode run HBase shell and then run status command.
 
-To verify that your upgrade was successful, check that the relevant HBase processes are started using the appropriate java version - for instance for region server check as:
+To verify that your upgrade was successful, check that the relevant HBase processes are started using the appropriate Java version - for instance for region server check as:
 
 ```
 ps -aux | grep regionserver, and verify the version like '''/usr/lib/jvm/java-8-openjdk-amd64/bin/java