updates to policheck-flagged text

Author: v-kents

docs/big-data-cluster/cluster-troubleshooter-notebooks.md

@@ -75,7 +75,7 @@ A set of notebooks for repairing known situations and states of a SQL Server Big
 |Name |Description |
 |---|---|---|---|
 |TSG005 - Forwarding loop detected|Use this notebook to dealing with forwarding loop detected since the utility dnsmasq can put a local loopback in resolv.conf, which can cause the controller pods to go into a CrashLoopBackOff during initial cluster deployment: https://askubuntu.com/questions/627899/nameserver-127-0-1-1-in-resolv-conf-wont-go-away|
-|TSG011 - Restart sparkhistory server|Use this notebook to restart sparkhistory server since the sparkhistory java process can hang during startup. Restarting the sparkhistory server (supervisorctl restart sparkhistory) can resolve this issue.|
+|TSG011 - Restart sparkhistory server|Use this notebook to restart sparkhistory server since the sparkhistory java process can stop responding during startup. Restarting the sparkhistory server (supervisorctl restart sparkhistory) can resolve this issue.|
 |TSG018 - Kill sqlservr process on the master pool| Use this notebook when T-SQL SHUTDOWN does not successfully re-cycle the ./sqlservr process. Use this notebook to kill the main sqlservr process which will get automatically restarted by the ./sqlservr front end process.|
 |TSG024 - Namenode is in safe mode| Use this notebook when HDFS gets itself into Safe mode. For example if too many Pods are re-cycled too quickly in the Storage Pool then Safe mode may be automatically enabled.|
 |TSG028 - Restart node manager on all storage pool nodes| Use this notebook when needs to restart node manager on all storage pool nodes.|
@@ -99,4 +99,3 @@ A set of notebooks for repairing known situations and states of a SQL Server Big
 ## Next steps
 
 For more information about big data clusters, see [What are [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)]](big-data-cluster-overview.md).
-

docs/big-data-cluster/troubleshoot-ad-hung-deployment-unhealthy-sparkhead-pods.md

@@ -1,7 +1,7 @@
 ---
 title: AD mode deployment hangs - unhealthy `sparkhead` pods
 titleSuffix: SQL Server Big Data Cluster
-description: Troubleshooting hung deployment of a SQL Server Big Data Cluster in an Active Directory domain with unhealthy `sparkhead` pods.
+description: Troubleshooting unresponsive deployment of a SQL Server Big Data Cluster in an Active Directory domain with unhealthy `sparkhead` pods.
 author: macarv-ms
 ms.author: macarv
 ms.reviewer: mikeray

docs/ssms/release-notes-ssms.md

@@ -118,7 +118,7 @@ SSMS 18.7 is the latest general availability (GA) release of SSMS. If you need a
 | Analysis Services | Fixed an issue that may have resulted in an error when trying to connect to SSAS via msmdpump.dll. See [SQL Server User Feedback](https://feedback.azure.com/forums/908035-sql-server/suggestions/40144696). |
 | Backup/Restore | Fixed an issue where selecting "View Connection Properties" yielded a SMO error on HostDistribution prop being missing for SQL 2016 and earlier. |
 | Database Designer | Fixed an issue, which was causing SSMS to crash when handling decimal numbers. |
-| Database Diagrams | Fixed an issue that could cause SSMS to crash or hang when using Database Diagrams where "Add Table" dialog was not properly displayed. |
+| Database Diagrams | Fixed an issue that could cause SSMS to crash or stop responding when using Database Diagrams where "Add Table" dialog was not properly displayed. |
 | Database Mirroring | Fixed an issue that was causing mirror configuration to fail. See [SQL Server User Feedback](https://feedback.azure.com/forums/908035-sql-server/suggestions/32897281). |
 | General SSMS | Fixed an issue where trying to connect to an Azure SQL DB, which could take several seconds (SQL login in a user database). |
 | General SSMS | Fixed an issue where SSMS was not handling/displaying deadlock captured (.xdl files). |