documentor updates

Author: haywoodsloan

support/sql/database-engine/agent/intermittent-crashes.md

@@ -6,13 +6,13 @@ ms.custom: sap:SQL Agent (Jobs, Alerts, Operators)\SQL Agent Service is unable t
 ms.reviewer: prmadhes, v-shaywood
 ---
 
-# SQL Agent services crashes intermittently
+# SQL Agent service crashes intermittently
 
 This article provides troubleshooting guidance for an issue where the SQL Agent service repeatedly crashes on a regular interval.
 
 ## Symptoms
 
-The SQL Agent service crashes intermittently on a SQL Server Always On Cluster. When the SQL Agent service crashes the following error message is added to the ???? log: <!-- Ask SME where the error message is reported. Popup, command output, log entry? -->
+The SQL Agent service crashes intermittently on a SQL Server Always On Cluster. When the SQL Agent service crashes, the following error message is added to the ???? log: <!-- Ask SME where the error message is reported. Popup, command output, log entry? -->
 
 > [510] SQLAgent failed, dump generated in \<SQL_Instance_Log_Directory\>
 > [LOG] Exception 29539 caught at line 233 of file sql\mpu\SqlAgent\src\autostrt.cpp. SQLServerAgent initiating self-termination.
@@ -23,9 +23,9 @@ These crashes occur when the SQL Agent service fails to retrieve the following r
 
 `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceID>\SQLServerAgent\AutoRegistryRefresh`
 
-When the registry key retrieve fails, the SQL Agent service reports an exception in the log then terminates itself.
+When the registry key retrieval fails, the SQL Agent service reports an exception in the log then terminates itself.
 
-Registry key retrieval can fail due to the following:
+Registry key retrieval can fail due to the following reasons:
 
 - Antivirus or endpoint protection software interfering with registry access.
 - Missing or misconfigured registry keys.
@@ -38,14 +38,14 @@ Use the following steps to resolve this issue:
 ### Step 1: Verify the registry key
 
 1. Open the Registry Editor (`regedit.exe`).
-1. Navigate to the following path: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceID>\SQLServerAgent`.
+1. Go to the following path: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceID>\SQLServerAgent`.
 1. Check if the `AutoRegistryRefresh` key exists.
-1. If the `AutoRegistryRefresh` key is missing, create a new _DWORD (32-bit) Value_ named `AutoRegistryRefresh` and set its value to `1`
+1. If the `AutoRegistryRefresh` key is missing, create a new _DWORD (32-bit) Value_ named `AutoRegistryRefresh` and set its value to `1`.
 
 ### Step 2: Exclude SQL Server from antivirus scanning
 
 > [!IMPORTANT]
-> The process of adding an exclusion to your antivirus or endpoint protection software will vary by publisher. Check with the publisher of your software for specific instructions.
+> The process of adding an exclusion to your antivirus or endpoint protection software varies by publisher. Check with the publisher of your software for specific instructions.
 
 1. Configure your antivirus or endpoint protection software to exclude the common SQL Server processes:
     1. `sqlservr.exe`
@@ -54,7 +54,7 @@ Use the following steps to resolve this issue:
     1. `msmdsrv.exe`
     1. `fdlauncher.exe`
     1. `fdhost.exe`
-1. Also, exclude the directory where SQL Server is installed, for example `C:\Program Files\Microsoft SQL Server\`
+1. Also, exclude the directory where SQL Server is installed, for example `C:\Program Files\Microsoft SQL Server\`.
 
 For more info on configuring your antivirus or endpoint protection software to work with SQL Server, see [Configure antivirus software to work with SQL Server](/troubleshoot/sql/database-engine/security/antivirus-and-sql-server).