updates for acrolinx

Author: sevend2

support/windows/win32/client-application-error-create-com-plus-component.md

@@ -37,10 +37,10 @@ This problem occurs because the Component Object Model (COM) initialization coun
 
 ## Resolution
 
-To resolve this problem, remove the `CoInitialize` calls and the `CoUninitialize` calls from the affected COM DLL. A COM DLL that exposes COM components and is loaded through COM calls from a client should not call the `CoInitialize` function or the `CoUninitialize` function on any thread that is used to load or to start the DLL. These threads are owned by the client application, by the COM runtime, or by the COM+ runtime. Only the COM DLL should call these APIs on additional threads that were explicitly created by the COM DLL. However, it is a common bug for COM DLLs to call the `CoInitialize` function and the `CoUninitialize` function in response to attach events and detach events in the `DllMain` function.
+To resolve this problem, remove the `CoInitialize` calls and the `CoUninitialize` calls from the affected COM DLL. A COM DLL that exposes COM components and is loaded through COM calls from a client shouldn't call the `CoInitialize` function or the `CoUninitialize` function on any thread that is used to load or to start the DLL. These threads are owned by the client application, by the COM runtime, or by the COM+ runtime. Only the COM DLL should call these APIs on additional threads that were explicitly created by the COM DLL. However, it's a common bug for COM DLLs to call the `CoInitialize` function and the `CoUninitialize` function in response to attach events and detach events in the `DllMain` function.
 
 > [!NOTE]  
-> It is correct for a standard Win32 DLL that isn't loaded through COM to call these APIs if the standard Win32 DLL plans to use COM APIs. However, these functions should not be called from the `DllMain` function.
+> It's correct for a standard Win32 DLL that isn't loaded through COM to call these APIs if the standard Win32 DLL plans to use COM APIs. However, these functions shouldn't be called from the `DllMain` function.
 
 For more information about the `CoInitialize` function, see [CoInitialize function](/windows/win32/api/objbase/nf-objbase-coinitialize).
 
@@ -56,24 +56,24 @@ To determine which COM component contains the affected code, use the Microsoft I
 1. [Download and install DebugDiag](https://www.microsoft.com/download/details.aspx?id=58210).
 2. Create a crash rule in DebugDiag. To do this, follow these steps:
 
-   1. Click **Start**, point to **Programs**, point to **IIS Diagnostics (32bit)**, point to **Debug Diagnostics Tool**, and then click **Debug Diagnostics Tool 1.0**.
-   2. If the **Select Rule Type** dialog box opens, click **Cancel**.
-   3. On the **Tools** menu, click **Options And Settings**.
-   4. Click the **Folders and Search Paths** tab, and then enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols` in the **Symbol Search Path For Analysis** field.
-   5. In the **Symbol Search Path For Debugging** field, enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols`, and then click **OK**.
-   6. Click **Add Rule**.
-   7. Click **Crash**, and then click **Next**.
-   8. Click **A specific MTS/COM+ application (included high and medium isolation websites)**, and then click **Next**.
-   9. Click the appropriate COM+ application, and then click **Next**.
-   10. In the **Advanced Configuration (Optional)** dialog box, click **Breakpoints**.
-   11. In the **Configure Breakpoints** dialog box, click **Add Breakpoint**.
-   12. In the **Configure Breakpoint** dialog box, enter *ole32!CoInitializeEx* in the **Breakpoint Expression** field, enter *1000* in the **Action Type** field, keep **Log Stack Trace** in the **Action Type** field, and then click **OK**.
-   13. In the **Configure Breakpoints** dialog box, click **Add Breakpoint**.
-   14. In the **Configure Breakpoint** dialog box, enter *ole32!CoUninitialize* in the **Breakpoint Expression** field, enter *1000* in the **Action Limit** field, and then click **OK**.
-   15. In the **Configure Breakpoints** dialog box, click **Save & Close**.
-   16. In the **Advanced Configuration (Optional)** dialog box, click **Next**.
-   17. In the **Select Dump Location And Rule Name (Optional)** dialog box, click **Next**.
-   18. In the **Rule Completed** dialog box, click **Activate the rule now**, and then click **Finish**.
+   1. Select **Start**, point to **Programs**, point to **IIS Diagnostics (32bit)**, point to **Debug Diagnostics Tool**, and then select **Debug Diagnostics Tool 1.0**.
+   2. If the **Select Rule Type** dialog box opens, select **Cancel**.
+   3. On the **Tools** menu, select **Options And Settings**.
+   4. Select the **Folders and Search Paths** tab, and then enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols` in the **Symbol Search Path For Analysis** field.
+   5. In the **Symbol Search Path For Debugging** field, enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols`, and then select **OK**.
+   6. Select **Add Rule**.
+   7. Select **Crash**, and then select **Next**.
+   8. Select **A specific MTS/COM+ application (included high and medium isolation websites)**, and then select **Next**.
+   9. Select the appropriate COM+ application, and then select **Next**.
+   10. In the **Advanced Configuration (Optional)** dialog box, select **Breakpoints**.
+   11. In the **Configure Breakpoints** dialog box, select **Add Breakpoint**.
+   12. In the **Configure Breakpoint** dialog box, enter *ole32!CoInitializeEx* in the **Breakpoint Expression** field, enter *1000* in the **Action Type** field, keep **Log Stack Trace** in the **Action Type** field, and then select **OK**.
+   13. In the **Configure Breakpoints** dialog box, select **Add Breakpoint**.
+   14. In the **Configure Breakpoint** dialog box, enter *ole32!CoUninitialize* in the **Breakpoint Expression** field, enter *1000* in the **Action Limit** field, and then select **OK**.
+   15. In the **Configure Breakpoints** dialog box, select **Save & Close**.
+   16. In the **Advanced Configuration (Optional)** dialog box, select **Next**.
+   17. In the **Select Dump Location And Rule Name (Optional)** dialog box, select **Next**.
+   18. In the **Rule Completed** dialog box, select **Activate the rule now**, and then select **Finish**.
 
 DebugDiag monitors the selected COM+ application when the application runs. Every time that DebugDiag experiences one of the selected breakpoints, DebugDiag adds data to a log file. By default, the log file will be named:  
 `C:\Program Files\IIS Resources\DebugDiag\Logs\dllhost__PID__\<pid>\__Date__\<date> __Time\_\<time> Log.txt`

support/windows/win32/coinitializeex-fails-after-calling-htmlhelp-same-thread.md

@@ -9,17 +9,17 @@ ms.custom: sap:Component Development\COM, DCOM, and COM+ Programming and Runtime
 ---
 # CoInitializeEx function fails after calling the HtmlHelp function on the same thread
 
-This article discusses an issue where the [CoInitializeEx function](/windows/win32/api/combaseapi/nf-combaseapi-coinitializeex) fails after calling the `HtmlHelp` function on the same thread.
+This article discusses an issue where the [CoInitializeEx](/windows/win32/api/combaseapi/nf-combaseapi-coinitializeex) function fails after calling the `HtmlHelp` function on the same thread.
 
 _Applies to:_   All supported operating system
 
 ## Symptoms
 
-If an application calls `HtmlHelp` before calling `CoInitializeEx` with the specified `COINIT_MULTITHREADED` value, `CoInitializeEx` can return `RPC_E_CHANGED_MODE (0x80010106)`. As a result, the application may crash, hang, or display unexpected behavior.
+If an application calls `HtmlHelp` before calling `CoInitializeEx` with the specified `COINIT_MULTITHREADED` value, `CoInitializeEx` can return `RPC_E_CHANGED_MODE (0x80010106)`. As a result, the application might crash, hang, or display unexpected behavior.
 
 ## Cause
 
-If a thread that calls `HtmlHelp` hasn't been initialized with `CoInitialize` or `CoInitializeEx`, `HtmlHelp` initializes the thread as apartment-threaded with `COINIT_APARTMENTTHREADED`.
+If a thread that calls `HtmlHelp` isn't initialized with `CoInitialize` or `CoInitializeEx`, `HtmlHelp` initializes the thread as apartment-threaded with `COINIT_APARTMENTTHREADED`.
 
 ## Workaround
 

support/windows/win32/xa-transaction-require-registry-entry.md

@@ -26,26 +26,26 @@ For example, when you upgrade an existing system to Windows Server 2003, and the
 > [!IMPORTANT]
 > This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see [How to back up and restore the registry in Windows](https://support.microsoft.com/help/322756).
 
-A security risk occurs when MS DTC uses user-specified DLLs. These DLLs are loaded directly in the MS DTC process. MS DTC uses these DLLs to communicate with the Transaction Manager (TM) of the XA partner. This scenario can expose the Resource Manager (RM) databases to serious data corruption. This scenario can also permit denial-of-service attacks if a malicious or defective XA DLL does not verify that the distributed transaction commits or aborts correctly. Also, if a malicious or defective XA DLL contains code that is not security-enhanced, an attacker might exploit this weakness to cause a denial-of-service attack.
+A security risk occurs when MS DTC uses user-specified DLLs. These DLLs are loaded directly in the MS DTC process. MS DTC uses these DLLs to communicate with the Transaction Manager (TM) of the XA partner. This scenario can expose the Resource Manager (RM) databases to serious data corruption. This scenario can also permit denial-of-service attacks if a malicious or defective XA DLL doesn't verify that the distributed transaction commits or aborts correctly. Also, if a malicious or defective XA DLL contains code that isn't security-enhanced, an attacker might exploit this weakness to cause a denial-of-service attack.
 
 To help to prevent this security risk, Windows Server 2003 turns off all XA transactions when you upgrade to Windows Server 2003. If the support for XA transactions is turned off, Windows Server 2003 helps to protect MS DTC from denial-of-service attacks.
 
 You may have to turn on support for XA transactions. To do this, follow these steps:
 
 1. Open **Component Services**.
 2. Expand the tree view to locate the computer on which you want to turn on support for XA transactions (for example, **My Computer**).
-3. Right-click the computer name, and then click **Properties**.
-4. Click the **MSDTC** tab, and then click **Security Configuration**.
+3. Right-click the computer name, and then select **Properties**.
+4. Select the **MSDTC** tab, and then select **Security Configuration**.
 5. Under **Security Settings**, select the check box for **XA Transactions** to turn on this support.
 
-Windows Server 2003 provides a registry entry for you to specify the XA DLLs that you will use. When you upgrade to Windows Server 2003, you can work with XA transactions in the same way that you worked with them in earlier versions of Microsoft Windows Server.
+Windows Server 2003 provides a registry entry for you to specify the XA DLLs that you'll use. When you upgrade to Windows Server 2003, you can work with XA transactions in the same way that you worked with them in earlier versions of Microsoft Windows Server.
 
 To do this, create a registry named-value under the following registry subkey:  
 `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL`
 
-In your registry named-value, **Name** can be the file name of the XA DLL (for example, dllname.dll), although you are not required to use this naming convention. Also in this named-value, **Type** is String (REG_SZ), and the value is the full path name (including the file name) of the DLL file.
+In your registry named-value, **Name** can be the file name of the XA DLL (for example, dllname.dll), although you aren't required to use this naming convention. Also in this named-value, **Type** is String (REG_SZ), and the value is the full path name (including the file name) of the DLL file.
 
-Create an entry for each XA DLL file that you plan to use. Also, if you are configuring MS DTC on a cluster, you must create these registry entries on each node in the cluster.
+Create an entry for each XA DLL file that you plan to use. Also, if you're configuring MS DTC on a cluster, you must create these registry entries on each node in the cluster.
 
 ## References