Merge pull request #4886 from moti-ba/docs-editor/tvm-weaknesses-1756707273

Update tvm-weaknesses.md

Author: KesemSharabi

defender-vulnerability-management/tvm-weaknesses.md

@@ -44,8 +44,8 @@ The Weaknesses page opens with a list of the CVEs your devices are exposed to. Y
 If there's no official CVE-ID assigned to a vulnerability, the vulnerability name is assigned by Defender Vulnerability Management using the format **TVM-2020-002**.
 
 > [!NOTE]
-> The maximum number of records you can export from the weaknesses page to a CSV file is 8,000 and the export must not exceed 64 KB. If you receive a message stating the results are too large to export, refine your query to include fewer records.
->
+> The maximum number of records you can export from the weaknesses page to a CSV file is 6,000 and the export must not exceed 64 KB. If you receive a message stating the results are too large to export, refine your query to include fewer records.
+> 
 > Currently, Defender Vulnerability Management doesn't distinguish between 32-bit and 64-bit system architectures when correlating vulnerabilities (CVEs) to devices. This limitation can lead to false positives, especially in cases where a CVE applies only to one architecture type. For example, on a Windows Server 2016 machine, PHP was incorrectly flagged with `CVE-2024-11236`, which affects only 32-bit systems. Since architecture isn't currently factored into the correlation process, the CVE was incorrectly associated with a 64-bit server. This is a known issue, and a solution is on the roadmap.
 
 ## Breach and threat insights