Fix malformed documentation link patterns

- Fix /do../../auditor/ patterns to /docs/auditor/
- Fix /do../../accessanalyzer/ patterns to /docs/accessanalyzer/
- Fix /do/docs/ patterns to /docs/
- These were causing broken link warnings in docusaurus builds

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: 2 people

docs/auditor/10.8/addon/connectwise/overview.md

@@ -60,7 +60,7 @@ Solution architecture and key components are shown in the figure below:
        the alert into the service queue.
 
 For details on the alert response action, see the
-[Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md.md) topic for
+[Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md) topic for
 additional information.
 
 - **Netwrix Auditor ConnectWise Manage Integration Service (Netwrix.ITSM.IntegrationServiceCW.exe)**

docs/auditor/10.8/addon/siem/deployment.md

@@ -34,5 +34,5 @@ By default, Auditor uses the _LocalSystem_ account to run PowerShell scripts. If
 another account, in the alert settings go to **Response Action**, select the **Use custom
 credentials** checkbox and specify user name and password. Make sure this account has **Log on as
 batch job** privilege. See the
-[Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md.md) topic for
+[Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md) topic for
 additional information.

docs/auditor/10.8/addon/siem/overview.md

@@ -77,13 +77,13 @@ This add-on works as response action to the alert, as follows:
 
 1. The administrator enables and configured response action for selected alert, as described in the
    following topic:
-   [Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md.md). Make sure
+   [Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md). Make sure
    to provide correct path to the script file and to select the Write data to CSV file option.
 2. When the alert is triggered, the script starts - it retrieves audit data (activity record fields)
    from the CSV file and processes it into log events. Each event contains the user account, action,
    time, and other details.
 3. The add-on creates a special Windows event log named Netwrix_Auditor_Integration and stores
    events there. These events are structured and ready for integration with SIEM system.
 
-See the [Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md.md)
+See the [Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md)
 topic for additional information on the alert response actions and CSV file.

docs/auditor/10.8/admin/alertsettings/create/create.md

@@ -36,4 +36,4 @@ See the [Navigation](/docs/auditor/10.8/admin/navigation/overview.md) topic for
 | Filters         | Apply a set of filters to narrow events that trigger a new alert. Alerts use the same interface and logic as search. <ul><li>Filter — Select general type of filter (e.g., "Who", "Data Source", "Monitoring plan", etc.)</li><li>Operator — Configure match types for selected filter (e.g., "Equals", "Does not contain", etc.)</li><li>Value — Specify filter value. See the [View and Search Collected Data](/docs/auditor/10.8/admin/search/overview.md) topic for additional information on how to create and modify filters. The Filters section contains required fields highlighted with red. Once you completed all filters, click Preview on the right pane to see search-based list of events that will trigger your alert. ![preview_thumb_0_0](/images/auditor/10.7/admin/alertsettings/preview_thumb_0_0.webp)</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | Thresholds      | If necessary, enable threshold to trigger the new alert. In this case, a single alert will be sent instead of many alerts. This can be helpful when Auditor detects many activity records matching the filters you specified. Slide the switch under the Send alert when the threshold is exceeded option and configure the following: <ul><li>Limit alerting to activity records with the same... — Select a filter in the drop-down list (e.g., who). Note that, Auditor will search for activity records with the same value in the filter you selected. Only alerts grouped by the Who parameter can be included in the Behavior Anomalies list. Mind that in this case, the product does not summarize risk scores and shows the value you associated with this alert. This may significantly reduce risk score accuracy.</li><li>Send alert for `<...>` activity records within `<...>` seconds — Select a number of changes that occurred in a given period (in seconds). For example, you want to receive an alert on suspicious activity. You select "_Action_" in the Limit alerting to activity records with the same list and specify a number of actions to be considered an unexpected behavior: _1000_ changes in _60_ seconds. When the selected threshold exceeded, an alert will be delivered to the specified recipients: one for every 1000 removals in 60 seconds, one for every 1000 failed removals in 60 seconds. So you can easily discover what is going on in your IT infrastructure.</li></ul>                                                                                                                                                                                                                                                                                                                                 |
 | Risk Score      | <ul><li>Slide the switch to On under Include this alert in Behavior Anomalies assessment. See the [Behavior Anomalies](/docs/auditor/10.8/admin/behavioranomalies/overview.md) topic for additional information.</li><li>Associate a risk score with the alert — Assign a risk score based on the type of anomaly and the severity of the deviation from the normal behavior. An action's risk score is a numerical value from 1 (Low) to 100 (High) that designates the level of risk with 100 being the riskiest and 1 the least risky. These are general guidelines you can adopt when setting a risk score:</li><li>High score — Assign to an action that requires your immediate response (e.g., adding account to a privileged group). Configure a non-threshold alert with email recipients.</li><li>Above medium score — Assign to a repetitive action occurring during a short period of time. While a standalone action is not suspicious, multiple actions merit your attention (e.g., mass deletions from a SharePoint site). Configure a threshold-based alert with email recipients.</li><li>Low score — Assign to an infrequent action. While a single action is safe, multiple occurrences aggregated over a long period of time may indicate a potential in-house bad actor (e.g., creation of potentially harmful files on a file share). Configure a non-threshold alert, email recipients are optional but make sure to regularly review the Behavior Anomalies dashboard.</li><li>Low score — Assign to a repetitive action that does not occur too often (e.g., rapid logons). Multiple occurrences of action sets may indicate a potential in-house bad actor or account compromise. Configure a threshold-based alert, email recipients are optional but make sure to regularly review the Behavior Anomalies dashboard.</li></ul> |
-| Response Action | You can instruct Auditor to perform a response action when the alert occurs — for example, start an executable file (command, batch file, or other) that will remediate the issue, or open a ticket with the help desk, and so on. For that, you will need an executable file stored locally on the Auditor server. Slide the switch to turn the feature **ON**, and see the [Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md.md) topic for additional information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Response Action | You can instruct Auditor to perform a response action when the alert occurs — for example, start an executable file (command, batch file, or other) that will remediate the issue, or open a ticket with the help desk, and so on. For that, you will need an executable file stored locally on the Auditor server. Slide the switch to turn the feature **ON**, and see the [Configure a Response Action for Alert](/docs/auditor/10.8/admin/alertsettings/responseaction.md) topic for additional information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

docs/kb/accessanalyzer/cannot-connect-to-sql-database.md

@@ -33,12 +33,12 @@ The database password in **Home** > **Configure Console** > **Database** has exp
 1. Ensure that the password for the Netwrix Access Analyzer database has been updated.
 2. Log in to AIC using the default `admin` user and password.
 
-> **NOTE:** If you need to reset the AIC Administrator password, see: /docs/kb/accessanalyzer/resetting-the-aic-administrator-password
+> **NOTE:** If you need to reset the AIC Administrator password, see: /docs/accessanalyzer/resetting-the-aic-administrator-password
 
 3. Navigate to **Home** > **Configure Console** > **Database**, enter the new database password for your SQL account, and click **Save**.
 4. Verify that AIC is now functioning correctly.
 
 > **NOTE:** Other users, apart from the `admin` user, cannot access AIC if the database password is expired or incorrect. It is recommended to log in as the `admin` user to update the database password.
 
 ## Related Link
-- Resetting the AIC Administrator Password: /docs/kb/accessanalyzer/resetting-the-aic-administrator-password
+- Resetting the AIC Administrator Password: /docs/accessanalyzer/resetting-the-aic-administrator-password

docs/kb/accessanalyzer/console-migration-workflow-step-1-staging-the-backup.md

@@ -24,9 +24,9 @@ knowledge_article_id: kA0Qk0000002OnpKAE
 
 # Console Migration Workflow: Step 1—Staging the Backup
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
 >
-> Proceed to the next section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database).
+> Proceed to the next section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database).
 
 ## Overview
 
@@ -98,5 +98,5 @@ Within the `NAA_Migration` folder, create a folder named **AIC**, and add the fo
 
 ## Related Links
 
-- [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md)
-- [Console Migration Workflow: Step 2—Prepare the Database](/docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database)
+- [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md)
+- [Console Migration Workflow: Step 2—Prepare the Database](/docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database)

docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database.md

@@ -24,11 +24,11 @@ knowledge_article_id: kA0Qk0000002OpRKAU
 
 # Console Migration Workflow: Step 2—Prepare the Database
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
 >
-> Return to the previous section via this link: [Console Migration Workflow: Step 1—Staging the Backup](/docs/kb/accessanalyzer/console-migration-workflow-step-1-staging-the-backup).
+> Return to the previous section via this link: [Console Migration Workflow: Step 1—Staging the Backup](/docs/accessanalyzer/console-migration-workflow-step-1-staging-the-backup).
 >
-> Proceed to the next section via this link: [Console Migration Workflow: Step 3—Rebuild the Console](/docs/kb/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console).
+> Proceed to the next section via this link: [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console).
 
 ## Overview
 
@@ -70,6 +70,6 @@ Where SA_Node = @OHost;
 
 ## Related Links
 
-- [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md)
-- [Console Migration Workflow: Step 1—Staging the Backup](/docs/kb/accessanalyzer/console-migration-workflow-step-1-staging-the-backup)
-- [Console Migration Workflow: Step 3—Rebuild the Console](/docs/kb/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console)
+- [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md)
+- [Console Migration Workflow: Step 1—Staging the Backup](/docs/accessanalyzer/console-migration-workflow-step-1-staging-the-backup)
+- [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console)

docs/kb/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console.md

@@ -22,11 +22,11 @@ knowledge_article_id: kA0Qk0000002Or3KAE
 
 # Console Migration Workflow: Step 3—Rebuild the Console
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
 >
-> Return to the previous section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database).
+> Return to the previous section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database).
 >
-> Proceed to the next section via this link: [Console Migration Workflow: Step 4—Validating the Migration](/docs/kb/accessanalyzer/console-migration-workflow-step-4-validate-the-migration)
+> Proceed to the next section via this link: [Console Migration Workflow: Step 4—Validating the Migration](/docs/accessanalyzer/console-migration-workflow-step-4-validate-the-migration)
 
 ## Overview
 
@@ -139,9 +139,9 @@ If using any of the below, please recreate the certificate for the new NAA Conso
 
 ## Related Links
 
-- Console Migration Workflow: /docs/kb/accessanalyzer/console-migration-workflow
-- Console Migration Workflow: Step 2—Prepare the Database: /docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database
-- Console Migration Workflow: Step 4—Validating the Migration: /docs/kb/accessanalyzer/console-migration-workflow-step-4-validate-the-migration
+- Console Migration Workflow: /docs/accessanalyzer/console-migration-workflow
+- Console Migration Workflow: Step 2—Prepare the Database: /docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database
+- Console Migration Workflow: Step 4—Validating the Migration: /docs/accessanalyzer/console-migration-workflow-step-4-validate-the-migration
 - Netwrix Help Center | Netwrix Access Analyzer 12.0 System Requirements: /docs/accessanalyzer/12.0/requirements
 - Access Analyzer Initial Configuration: /docs/accessanalyzer/12.0/install/application
 - Netwrix Access Analyzer for SharePoint Online: /docs/accessanalyzer/12.0/configuration/sharepointonline

docs/kb/accessanalyzer/console-migration-workflow-step-4-validate-the-migration.md

@@ -23,9 +23,9 @@ knowledge_article_id: kA0Qk0000002OsfKAE
 
 # Console Migration Workflow: Step 4—Validate the Migration
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
 >
-> Return to the previous section via this link: [Console Migration Workflow: Step 3—Rebuild the Console](/docs/kb/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console).
+> Return to the previous section via this link: [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console).
 
 ## Overview
 
@@ -43,5 +43,5 @@ After completing Steps 1-3, please verify the following:
 
 ## Related Links
 
-- [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md)
-- [Console Migration Workflow: Step 3—Rebuild the Console](/docs/kb/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console)
+- [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md)
+- [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console)