Merge pull request #5158 from mestew/CIremedi2002tweak4261411

2002cbTweak-CiRemediations-4261411

Author: PRMerger12

sccm/compliance/deploy-use/create-custom-configuration-items-for-windows-desktop-and-server-computers-managed-with-the-client.md

@@ -368,7 +368,7 @@ Compliance rules specify the conditions that define the compliance of a configur
     - **Critical with event**: Computers that fail this compliance rule report a failure severity of **Critical**. This severity level is also logged as a Windows event in the application event log.  
 
 
-## <a name="bkmk_track"></a> Track remediation history when supported
+## <a name="bkmk_track"></a> Track configuration item remediations
 <!--42631411-->
 *(Introduced in version 2002)*
 

sccm/core/plan-design/changes/whats-new-in-version-2002.md

@@ -184,7 +184,7 @@ The **All Windows 10 (ARM64)** platform is available in the list of supported OS
 For more information on Configuration Manager's support for ARM64 devices, see [Windows 10 on ARM64](/configmgr/core/plan-design/configs/support-for-windows-10#bkmk_arm64).
 
 
-### Track remediation history when supported
+### Track configuration item remediations
 <!--42631411-->
 You can now **Track remediation history when supported** on your configuration item compliance rules. When this option is enabled, any remediation that occurs on the client for the configuration item generates a state message. The history is stored in the Configuration Manager database.