prettier fixes

Author: jtviolet

.prettierignore

@@ -1,3 +1,10 @@
 # Ignore artifacts:
 build
 coverage
+
+# Ignore Claude configuration
+.claude/
+
+# Temporary ignore
+versioned_docs/*
+versioned_sidebars/*

.prettierrc

@@ -6,14 +6,15 @@
   "tabWidth": 2,
   "overrides": [
     {
-      "files": "*.md",
+      "files": "**/*.md",
       "options": {
+        "parser": "markdown",
         "proseWrap": "always",
         "tabWidth": 4
       }
     },
     {
-      "files": "*.ts",
+      "files": "**/*.ts",
       "options": {
         "semi": true
       }

docs/auditor/auditor/addon/cyberark/parameters.md

@@ -7,7 +7,7 @@ Most parameters are optional; you can skip or define parameters depending on you
 and security policies.
 
 The service uses the default values unless parameters are explicitly defined
-(\_<parameter>**_value_**</parameter>\_).
+(_<parameter>\*\*\_value_\*\*</parameter>\_).
 
 Parameters in **Settings.xml** can be grouped as follows:
 

docs/auditor/auditor/addon/hyperv/parameters.md

@@ -4,7 +4,7 @@ To configure the add-on parameters, you need to edit the **settings.xml** file i
 You must define connection details: Auditor Server host, user credentials, etc.
 
 Most parameters are optional, the service uses the default values unless parameters are explicitly
-defined (\_<parameter>**_value_**</parameter>\_). You can skip or define parameters depending on
+defined (_<parameter>\*\*\_value_\*\*</parameter>\_). You can skip or define parameters depending on
 your execution scenario and security policies.
 
 | Parameter                            | Default value                                            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |

docs/auditor/auditor/addon/qumulo/parameters.md

@@ -4,7 +4,7 @@ To configure the add-on parameters, you need to edit the **settings.xml** file i
 You must define connection details: Netwrix Auditor Server host, user credentials, etc.
 
 Most parameters are optional, the service uses the default values unless parameters are explicitly
-defined (\_<parameter>**_value_**</parameter>\_). You can skip or define parameters depending on
+defined (_<parameter>\*\*\_value_\*\*</parameter>\_). You can skip or define parameters depending on
 your execution scenario and security policies.
 
 Parameters in **settings.xml** can be grouped as follows:

docs/auditor/auditor/admin/reports/types/stateintime/overview.md

@@ -26,8 +26,8 @@ reports** option when you configure a monitoring plan for the selected data sour
 topic for additional information.
 
 The state-in-time reports are available under the Reports node. Depending on the data source,
-navigate to the corresponding subfolder, for example, **Predefined\_\_**>\_**\_Active
-Directory\_\_**>\_**\_Active Directory\_\_**>\_**\_State-in-Time**.
+navigate to the corresponding subfolder, for example, **Predefined\_\_**>_**\_Active
+Directory\_\_**>_**\_Active Directory\_\_**>\_**\_State-in-Time**.
 
 In the report filters, select a monitoring plan you want to generate a report for. To review data
 sources and items included in each plan, navigate to the Monitoring Plans section.

docs/auditor/auditor/tools/auditconfigurationassistant.md

@@ -15,7 +15,7 @@ necessary rights.
 
 **Audit Configuration Assistant** is a part of Netwrix Auditor product setup. It is installed
 together with the Auditor client and can be launched from the **Start** **menu** **>\_\_**Netwrix
-Auditor\_**\_>\_\_**Netwrix Auditor Audit Configuration Assistant\_\_. Alternatively, you can launch
+Auditor\*\*\*\*>**\*\*Netwrix Auditor Audit Configuration Assistant**. Alternatively, you can launch
 this utility from the monitoring plan wizard for Active Directory data source. See the Launch Audit
 Configuration Assistant section for additional information.
 

docs/changetracker/changetracker/overview.md

@@ -25,7 +25,7 @@ exhibiting changes, for example, when pre-staging patches, or from observed chan
 Change Tracker. Planned Changes comprise the devices to assess, change window and details of the
 changes to match, such as a file change or registry value, for example.
 
-This \_Closed-Loop**\_,** Intelligent Change Controlclosely aligns to COBIT or ITIL Change Control
+This _Closed-Loop\*\*_,\*\* Intelligent Change Controlclosely aligns to COBIT or ITIL Change Control
 processes whereby changes are pre-approved via a ‘Request For Change’ process, then reviewed for
 accuracy and quality via a QA Testing or Post-implementation review. Netwrix offer a ServiceNow
 Certified ITSM Integration Module to automatically pull in Change Requests from most leading ITSM

docs/groupid/groupid/admincenter/identitystore/configure/directoryservice/outofbounds.md

@@ -123,14 +123,14 @@ Smart Group Update schedule responsible for updating the respective group.
 
         Membership change is the difference between new membership and the existing membership.
         Percentage change in membership is calculated by the following formula:  
-        (newMemberCount - oldMemberCount) x 100 / oldMemberCount
+         (newMemberCount - oldMemberCount) x 100 / oldMemberCount
 
         Let’s assume you specify 20 in this field. When group membership changes by 20% or more,
         Directory Manager considers it as an exception.
 
         So, if Group A has 500 members and 200 new members are to be added, the formula will be as  
-        (newMemberCount - oldMemberCount) x 100 / oldMemberCount  
-        (700-500) x 100 / 500 = 40
+         (newMemberCount - oldMemberCount) x 100 / oldMemberCount  
+         (700-500) x 100 / 500 = 40
 
         Since 40 is greater than 20, Directory Manager treats it as an out-of-bounds exception.
 

docs/groupid/groupid/admincenter/identitystore/history/view.md

@@ -85,8 +85,8 @@ value, old value, and more.
 
     **Add more filters** - On adding a filter, the next row is displayed, so you can add another
     filter.  
-    **Remove a filter row** - To remove a filter row, click **Remove** for it.  
-    **Remove the filter** - To remove all the filter rows, click **Clear**.
+     **Remove a filter row** - To remove a filter row, click **Remove** for it.  
+     **Remove the filter** - To remove all the filter rows, click **Clear**.
 
 7. To apply the filter, click **Apply**. With multiple filters, history items that satisfy all the
    filters are displayed.