Added Windows Server 2025 and SQL Server 2025 as supported OS and data storage

docs/accessanalyzer/11.6/install/application/upgrade/overview.md

@@ -11,14 +11,14 @@ that are no longer supported, contact [Netwrix Support](https://www.netwrix.com/
 assistance.
 
 :::note
-If a Netwrix Engineer has made any customizations, ensure custom work isn't lost during the
+If a Netwrix Engineer has made any customizations, ensure you preserve the custom work during the
 upgrade process. The Upgrade Wizard archives customizations before solution upgrades. These
 archives are available after the solution upgrades finish. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional
 information.
 :::
 
 
-This document provides the basic steps needed for upgrading Enterprise Auditor
+This document provides the basic steps for upgrading Enterprise Auditor
 and the stock solutions. Contact [Netwrix Support](https://www.netwrix.com/support.html) for
 additional information.
 
@@ -35,25 +35,25 @@ schema, corruption to Enterprise Auditor’s system tables can result.
 
 **SQL Server Supported Version Change for the Enterprise Auditor Database**
 
-With the release of Enterprise Auditor v11.6, SQL Server 2016 through SQL Server 2022 are the
+With the release of Enterprise Auditor v11.6, SQL Server 2016 through SQL Server 2025 are the
 supported versions for the Enterprise Auditor database.
 
-To grant access to additional Solutions in an existing Enterprise Auditor installation, a new
-license key is required. To update the Enterprise Auditor license key without installing a new
+Granting access to additional Solutions in an existing Enterprise Auditor installation requires a
+new license key. To update the Enterprise Auditor license key without installing a new
 version of the Enterprise Auditor Console, see the
 [Update License Key](/docs/accessanalyzer/11.6/install/application/updatelicense.md)
 topic for instructions.
 
 **License Key Changes**
 
-The following changes in licensing requires the organization needing a new key:
+The following licensing changes require the organization to get a new key:
 
 - Enterprise Auditor v11.6
 
-    - No additional licenses are required for this version
+    - This version requires no additional licenses
 
 - StealthAUDIT v11.5
-    - No additional licenses are required for this version
+    - This version requires no additional licenses
 - StealthAUDIT v11.0
     - The new Data Privacy functionality is now a licensable feature.
     - All database platforms are available as part of a single SQL license.

docs/accessanalyzer/11.6/install/filesystemproxy/overview.md

@@ -37,6 +37,7 @@ topic for information on the required prerequisites.
 You can install the File System Proxy Service for the Enterprise Auditor File System Solution on
 the following Windows operating systems:
 
+- Windows Server 2025
 - Windows Server 2022
 - Windows Server 2019
 - Windows Server 2016
@@ -65,15 +66,16 @@ Two options are available for implementing the proxy scanning architecture:
 
 When you run File System scans in proxy mode with applet, Enterprise Auditor deploys the File
 System applet to the Windows proxy server when the job runs to conduct data collection. The proxy
-server where the applet is deployed initiates the data collection processing and uses a
+server hosting the applet initiates the data collection processing and uses a
 local mode-type scan to each of the target hosts. The final step in data collection is to compress
 and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise
 Auditor Console server.
 
 ![Diagram of Enterprise Auditor server sending an FSAA applet to a proxy server](/images/accessanalyzer/11.6/install/filesystemproxy/proxymodewithapplet.webp)
 
-The diagram illustrates the Enterprise Auditor server sending an FSAA applet to a proxy server,
-which runs the scan against a file server, and then returns data to the Enterprise Auditor server.
+The diagram illustrates the Enterprise Auditor server sending a FileSystemAccess (FSAA) applet to a
+proxy server, which runs the scan against a file server, and then returns data to the Enterprise
+Auditor server.
 
 ### Proxy Mode as a Service
 
@@ -107,8 +109,8 @@ The diagram illustrates the Enterprise Auditor server communicating securely wit
 on a proxy server, which runs the scan against a file server, collecting the data locally and
 securely. Then the proxy service returns data securely to the Enterprise Auditor server.
 
-When you initiate a proxy mode scan from the Enterprise Auditor Console, it distributes hosts to
-be scanned across all proxy hosts. Enterprise Auditor monitors the scans from the central console.
+When you initiate a proxy mode scan from the Enterprise Auditor Console, it distributes hosts for
+scanning across all proxy hosts. Enterprise Auditor monitors the scans from the central console.
 Once all proxy hosts complete scanning, they return all results and SQLite databases to the
 Enterprise Auditor Console server.
 

docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md

@@ -7,7 +7,7 @@ sidebar_position: 40
 # Sensitive Data Discovery Add-On Installation
 
 The Sensitive Data Discovery Add-On enables Enterprise Auditor to scan files for criteria matches
-which indicate the existence of sensitive data. You can run Sensitive Data Discovery scans against
+that indicate sensitive data. You can run Sensitive Data Discovery scans against
 Windows file system servers, Network Attached Storage (NAS) devices, SharePoint on-premises,
 SharePoint Online, OneDrive for Business, DropBox for Business, SQL Server databases, and Exchange
 mailboxes.
@@ -21,7 +21,7 @@ The version of the SharePoint Agent must also match the major version of Enterpr
 
 You can install the Sensitive Data Discovery Add-On on the following servers:
 
-- Windows Server 2016 through Windows Server 2022
+- Windows Server 2016 through Windows Server 2025
     - On the Enterprise Auditor Console Server
     - On the Windows proxy server hosting the File System Proxy service
         - See the

docs/accessanalyzer/11.6/requirements/databases/sql/sql.md

@@ -11,14 +11,15 @@ database environments to collect permissions, sensitive data, and activity event
 
 - Azure SQL
 
-- SQL Server 2022
+- SQL Server 2025
+- SQL Server 2022
 - SQL Server 2019
 - SQL Server 2017
 - SQL Server 2016
 
 **Target SQL Server Requirements**
 
-The following are requirements for the SQL Server to be scanned:
+The target SQL Server must meet the following requirements:
 
 - WINRM Service installed
 - Ensure the following rights are in the `ROOT\Microsoft\SQLServer` and `ROOT\Interop` WMI
@@ -35,7 +36,7 @@ The following are requirements for the SQL Server to be scanned:
 
 - For Activity Auditing – SQL Server Audit:
 
-    - SQL Server Audit Specifications to be configured on the target databases
+    - Configure SQL Server Audit Specifications on the target databases
     - Audit destination must be a binary file
     - See the Microsoft
       [Create a server audit and database audit specification](https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/create-a-server-audit-and-database-audit-specification)
@@ -79,9 +80,9 @@ This solution employs the following data collector to scan the target environmen
 - For permissions for data collection:
 
     - Read access to SQL instance
-    - Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the
-      target SQL instances when using the **Scan full rows for sensitive data** option on the
-      Options wizard page
+    - Requires the SQL Full-Text and Semantic Extractions for Search feature on the target SQL
+      instances when you use the **Scan full rows for sensitive data** option on the Options
+      wizard page
     - Grant Authenticate Server to [DOMAIN\USER]
     - Grant Connect SQL to [DOMAIN\USER]
     - Grant View any database to [DOMAIN\USER]
@@ -111,4 +112,4 @@ The following firewall ports are needed:
 
 **For SQL Data Collector**
 
-- Specified by Instances table (default is 1433)
+- The Instances table specifies the port (default is 1433)

docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md

@@ -19,7 +19,7 @@ Access Auditing and Sensitive Data Discovery Auditing support CIFS and NFSv3.
 :::
 
 
-Ports and permissions vary based on the scan mode option selected as well as the target environment.
+Ports and permissions vary based on the selected scan mode option and the target environment.
 
 **Data Collectors**
 
@@ -52,13 +52,14 @@ The following firewall ports are needed:
 
 **Permissions and Ports for FileSystemAccess Data Collector**
 
-- Permissions vary based on the Scan Mode Option selected. See the File System Supported Platforms
+- Permissions vary based on the selected Scan Mode Option. See the File System Supported Platforms
   topic for additional information.
 
 ## Supported Windows Platforms
 
 The following are supported Microsoft® Windows® operating systems:
 
+- Windows Server 2025
 - Windows Server 2022
 - Windows Server 2019
 - Windows Server 2016
@@ -125,7 +126,7 @@ for target environment requirements.
 - Cluster-Mode 8.2+
 
     :::note
-    The Resiliency feature introduced in ONTAP 9.0 isn't supported.
+    Enterprise Auditor doesn't support the Resiliency feature introduced in ONTAP 9.0.
     :::
 
 

docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/proxymodeserver.md

@@ -6,32 +6,31 @@ sidebar_position: 10
 
 # Proxy Mode Server Requirements
 
-The Enterprise Auditor File System Proxy requirements apply for servers where either the service is
-installed or the applet will be deployed unless otherwise stated.
+The Enterprise Auditor File System Proxy requirements apply for servers where you either install the
+service or deploy the applet, unless otherwise stated.
 
 :::note
-Align the proxy server requirements to match the environment size the proxy server will be
-handling.
+Align the proxy server requirements to match the size of the environment the proxy server
+handles.
 :::
 
 
 The server can be physical or virtual. The requirements for Enterprise Auditor are:
 
-- Windows Server 2016 through Windows Server 2022
+- Windows Server 2016 through Windows Server 2025
 
-    - US English language installation
+    - English (United States) language installation
     - Domain member
 
 **RAM, CPU, and Disk Space**
 
-RAM, CPU, and Disk Space are dependent upon the size of the target environment:
+RAM, CPU, and Disk Space depend on the size of the target environment:
 
 :::warning
 If running Sensitive Data Discovery (SDD) scans, you must increase the
 minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By
-default, SDD scans are configured to run two concurrent threads. For example, if the job is
-configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are
-required (8x2x2=32).
+default, SDD scans run two concurrent threads. For example, a job configured to scan 8 hosts at a
+time with two concurrent SDD threads requires an extra 32 GB of RAM (8x2x2=32).
 :::
 
 
@@ -65,9 +64,9 @@ required (8x2x2=32).
     - 2 CPU Cores
     - 130 GB Disk Space
 
-This recommended disk space sizing information is based on the needs of Enterprise Auditor as
-well as the File System solution for running Permission scans with the default configuration (500
-MB per million files and folders), that means no tag collection, file-level scanning, activity, or
+This recommended disk space sizing information is based on the needs of Enterprise Auditor and
+the File System solution for running Permission scans with the default configuration (500
+MB per million files and folders), which means no tag collection, file-level scanning, activity, or
 sensitive data.
 
 - For tag collection, add 125 MB per million documents to these totals
@@ -77,8 +76,8 @@ sensitive data.
   total size of the documents scanned for sensitive data (depending on targeted document types and
   selected criteria) to these totals
 
-For example, to scan 200 million files and folders, of which 10 million files will be
-scanned for tag collection and sensitive data with a total size of 6 TB, you would need: 160 GB for
+For example, to scan 200 million files and folders, of which you scan 10 million files
+for tag collection and sensitive data with a total size of 6 TB, you would need: 160 GB for
 permission collection + 1.25 GB for tag collection (10x125 MB) + 100 GB for sensitive data
 collection (200x500 MB) + 600 GB additional for sensitive data collection (10% of 6 TB) = 861.25 GB
 Disk Space.
@@ -90,7 +89,7 @@ The following are additional requirements for the server:
 - .NET Framework 4.7.2 Installed
 
     :::note
-    .NET Framework 4.7.2 can be downloaded from the link in the Microsoft
+    Download .NET Framework 4.7.2 from the link in the Microsoft
     [.NET Framework 4.7.2 offline installer for Windows](https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-7-2-offline-installer-for-windows-05a72734-2127-a15d-50cf-daf56d5faec2)
     article.
     :::
@@ -99,14 +98,14 @@ The following are additional requirements for the server:
 - Remote Registry Service enabled
 
     :::note
-    The Remote Registry Service only needs to be enabled when running Applet Mode or Proxy
+    You only need to enable the Remote Registry Service when running Applet Mode or Proxy
     Mode with Applet scans.
     :::
 
 
 **Sensitive Data Discovery Auditing**
 
-The following is required to run Sensitive Data Discovery scans:
+Running Sensitive Data Discovery scans requires the following:
 
 - Sensitive Data Discovery Add-On installed on the proxy server