Merge pull request #6961 from mestew/prslimit

add 200 limit for script packages in prs

Author: PRMerger14

memdocs/analytics/proactive-remediations.md

@@ -2,7 +2,7 @@
 title: Tutorial - Proactive remediations
 titleSuffix: Microsoft Endpoint Manager
 description: A tutorial on using Proactive remediations to enhance the user
-ms.date: 12/17/2021
+ms.date: 03/07/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-analytics
 ms.topic: tutorial
@@ -59,10 +59,10 @@ Proactive remediations requires the [licensing for Endpoint analytics](enroll-in
 
 ### <a name="bkmk_requirements"></a> Script requirements
 
+- You can have up to 200 script packages
+   - A script package can contain a detection script only or both a detection script and a remediation script
 - Ensure the scripts are encoded in UTF-8.
-
 - The maximum allowed output size limit is 2048 characters.
-
 - If the option **Enforce script signature check** is enabled in the [Settings](#bkmk_prs_deploy) page of creating a script package, the script runs using the device's PowerShell execution policy. The default execution policy for Windows client computers is **Restricted**. The default execution for Windows Server devices is **RemoteSigned**. For more information, see [PowerShell execution policies](/powershell/module/microsoft.powershell.core/about/about_execution_policies#powershell-execution-policies).
    - Scripts built into Proactive remediations are signed and the certificate is added to the **Trusted Publishers** certificate store of the device.
    - When using third-party scripts that are signed, make sure the certificate is in the **Trusted Publishers** certificate store. As with any certificate, the certificate authority must be trusted by the device.