Merge pull request #5205 from meghapriyams/docs-editor/mde-linux-prerequisites-1759763073

Update mde-linux-prerequisites.md

Author: paulinbar

defender-endpoint/mde-linux-prerequisites.md

@@ -15,7 +15,7 @@ ms.collection:
 ms.topic: conceptual
 ms.subservice: linux
 search.appverid: met150
-ms.date: 08/19/2025
+ms.date: 10/27/2025
 ---
 
 # Prerequisites for Microsoft Defender for Endpoint on Linux
@@ -110,9 +110,7 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
 - SUSE Linux Enterprise Server 15 (SP5, SP6) ARM64
 
 > [!NOTE]
-> The workstation and desktop versions of these distributions are unsupported
-> Distributions and versions that aren't explicitly listed are unsupported (even if they're derived from the officially supported distributions).
-> After a new package version is released, support for the previous two versions is reduced to technical support only. Versions older than that which are listed in this section are provided for technical upgrade support only.
+> Distributions and versions that aren't explicitly listed above, and custom operating systems, are unsupported (even if they're derived from the officially supported distributions). 
 > Microsoft Defender for Endpoint is kernel-version agnostic for all other supported distributions and versions. The minimal requirement for the kernel version is `3.10.0-327` or later.
 
 > [!WARNING]
@@ -143,8 +141,7 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
 |`xfs`|
 
 > [!NOTE]
-> NFS v3 mount points to be scanned thoroughly and are required to set the `no_root_squash` export option on these mount points.
-> Without this option, scanning NFS v3 can potentially fail due to lack of permissions. 
+> To scan NFS v3 mount points, make sure to set the `no_root_squash` export option. Without this option, scanning NFS v3 can potentially fail due to lack of permissions. 
 
 ## Verify if devices can connect to Defender for Endpoint cloud services
 
@@ -201,7 +198,7 @@ There are several methods and tools that you can use to deploy Microsoft Defende
 - [Guidance for Defender for Endpoint on Linux Server with SAP](/defender-endpoint/mde-linux-deployment-on-sap)
 
 > [!IMPORTANT]
-> Installing Microsoft Defender for Endpoint in any location other than the default install path isn't supported. On Linux, Microsoft Defender for Endpoint creates an mdatp user with random UID and GID values. If you want to control these values, create an mdatp user before installation using the `/usr/sbin/nologin` shell option. Here's an example: `mdatp:x:UID:GID::/home/mdatp:/usr/sbin/nologin`.
+> On Linux, Microsoft Defender for Endpoint creates an mdatp user with random UID and GID values. If you want to control these values, create an mdatp user before installation using the `/usr/sbin/nologin` shell option. Here's an example: `mdatp:x:UID:GID::/home/mdatp:/usr/sbin/nologin`.
 
 If you experience any installation issues, self-troubleshooting resources are available. See the links in the [Related content section](#related-content).