WIP: NDC Release 5.7.12 Documentation Update

[BenHayman-Netwrix]

No description provided.

[github-actions]

Auto-Fix Summary

72 issues fixed, 6 skipped across 6 files

Category	Fixes
Contractions	3
Substitutions	6
AllowsYouTo (rewrite)	2
CanBeUsedTo (rewrite)	2
FollowTheStepsTo (rewrite)	2
OxfordComma (rewrite)	1
Dale: exclamatory-sentences	1
Dale: passive-voice	38
Dale: undefined-acronyms	1
Dale: wordiness	16

Skipped (needs manual review)	Reason

| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:44 — Dale: positional-references | "in the bottom" refers to a physical UI location in the properties window, not to other content on the page |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserverews.md:29 — Dale: positional-references | "bottom-left corner" refers to a physical UI location, not to other content on the page |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:50 — Dale: wordiness | "Select Since if you want to periodically re-crawl content" — "if you want to" is the established conditional-option phrasing used consistently across all source tables; rewording one instance would break consistency |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md:16 — Dale: wordiness | "Templating allows an administrator to preconfigure" — multiple valid rewrites and the sentence is already direct; left to the author |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md:18 — Dale: positional-references | "review the associated templating guide" has no target link; adding or resolving one would require content the page doesn't provide |
| docs/dataclassification/5.7/introduction/upgrade.md:57 — Dale: wordiness | "you should run the installer as the NDC service account if possible" — the hedging is deliberate guidance; tightening it would change the strength of the recommendation |

Ask @claude on this PR if you'd like an explanation of any fix.

[github-actions]

Auto-Fix Summary

9 issues fixed, 7 skipped across 6 files

Category	Fixes
Contractions	1
Substitutions	1
Dale: misplaced-modifiers	2
Dale: passive-voice	3
Dale: wordiness	2

Skipped (needs manual review)	Reason

| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:26 — Dale: misplaced-modifiers | 'The user must have a mailbox connected to it to crawl Exchange.' — the trailing infinitive is ambiguous (whether the user or the product crawls Exchange); rewriting could change the technical meaning |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:9 — Dale: passive-voice | 'content stored in a single Exchange mailbox' is a reduced relative clause used consistently across all five source topics; rewriting would diverge from sibling pages without improving clarity |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxgraph.md:18 — Dale: passive-voice | heading text — not modified to avoid breaking anchor links |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserverews.md:10 — Dale: misplaced-modifiers | 'multiple Exchange mailboxes from the same Exchange server using the Exchange Web Services (EWS)' — 'using' could attach to the crawl action or to the server; the intended attachment is clear enough from context and any rewrite risks changing the technical claim |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md:9 — Dale: passive-voice | 'SharePoint Online sites hosted in Office 365' is a reduced relative clause reading naturally as an adjective phrase; rewriting adds words without improving clarity |
| docs/dataclassification/5.7/introduction/upgrade.md:42 — Dale: wordiness | This second 'Step 4 -' block duplicates Step 3 and the following warning, and its step number collides with the Index-files Step 4 above it. Removing or renumbering it is a content/structure decision for the author, not a style fix |
| docs/dataclassification/5.7/introduction/upgrade.md:52 — Dale: wordiness | 'After taking the preceding preparatory steps' is mildly redundant, but trimming it risks losing the deliberate back-reference to the prerequisites section |

Ask @claude on this PR if you'd like an explanation of any fix.

[github-actions]

Auto-Fix Summary

16 issues fixed, 6 skipped across 8 files

Category	Fixes
Substitutions	2
FirstPersonPlural (rewrite)	1
Dale: misplaced-modifiers	4
Dale: passive-voice	4
Dale: wordiness	5

Skipped (needs manual review)	Reason

| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxgraph.md:9 — Dale: wordiness | Sentence 'For on-premises Exchange mailboxes, Exchange Mailbox (EWS).' is missing its verb. The intended verb is ambiguous (use / see / configure), so a rewrite could change meaning — needs author input rather than a Dale fix |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:11 — Dale: wordiness | 'Due to the imminent deprecation of EWS for connecting to Exchange Online' is wordy, but every concise rewrite either drops 'imminent' or adds a claim about Microsoft's timeline that the source doesn't make |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:52 — Dale: wordiness | 'taking into account the last crawl date for each object' is mildly wordy; tightening it risks losing the precise re-crawl semantics being described |
| docs/dataclassification/5.7/introduction/introduction/exchange/exchange.md:9 — Dale: misplaced-modifiers | 'When preparing your Exchange Server for data classification:' is an incomplete lead-in with no main clause. Cannot determine the intended subject and predicate from context |
| docs/dataclassification/5.7/introduction/introduction/exchange/exchange.md:49 — Dale: wordiness | 'Add your user as a member and/or assign your user for Modern Authentication set up to this Role as well' is unclear; multiple valid interpretations of what should be assigned |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md:16 — Dale: wordiness | 'Templating allows an administrator to preconfigure classification settings' uses the 'allows ... to' construction, which Vale handles rather than Dale; no Dale rule violation confirmed |

Ask @claude on this PR if you'd like an explanation of any fix.

[github-actions]

Auto-Fix Summary

29 issues fixed, 9 skipped across 12 files

Category	Fixes
Dale: misplaced-modifiers	2
Dale: passive-voice	24
Dale: wordiness	3

Skipped (needs manual review)	Reason

| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:43 — Dale: positional-references | 'click the "wrench" icon at Settings in the bottom' describes a location in the product UI, not a cross-reference to other documentation content, so rewording it would lose the on-screen orientation the reader needs |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxgraph.md:31 — Dale: positional-references | Same UI-location phrasing ('in the bottom') — refers to screen position, not to other doc content |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:50 — Dale: wordiness | 'Select Since if you want to periodically re-crawl content...' — the conditional is accurate for an optional setting and matches the phrasing used consistently across every source-settings table; tightening it to 'Select Since to...' would read as an instruction rather than an option |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserverews.md:65 — Dale: wordiness | Same 'if you want to' conditional in the Crawl Range row — left consistent with the other source tables |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:49 — Dale: wordiness | 'the settings can be like the following example' is vague, but the correct phrasing depends on whether the example is illustrative or prescriptive — ambiguous without product knowledge |
| docs/dataclassification/5.7/introduction/upgrade.md:20 — Dale: undefined-acronyms | 'NDC' is the Netwrix Data Classification product short name and the full product name already appears earlier in the article, which the rule explicitly exempts |
| docs/dataclassification/5.7/introduction/introduction/exchange/exchange.md:91 — Dale: passive-voice | 'each of the mailboxes / users configured for collection' — reduced passive clause inside a permission definition; naming an actor would imply who performs the configuration, which the source doesn't state |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/overview.md:12 — Dale: wordiness | 'A group can either be "mixed", which allows it to contain all source types, or source-specific' — restructuring risks changing which clause the 'either/or' governs |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:2 — Dale: undefined-acronyms | heading text — not modified to avoid breaking anchor links |

Ask @claude on this PR if you'd like an explanation of any fix.

[github-actions]

Documentation PR Review

Editorial Review

docs/dataclassification/5.7/introduction/introduction/exchange/exchange.md

• Structure — Line 17: The added sentence "On-premise Exchange servers support this method" scopes Basic Authentication to on-premises only, but the section that follows still contains an ### Exchange Online subsection (lines 27–50) with an Exchange Online procedure. A reader following the new note at line 12 ("Exchange Online requires Modern authentication") will hit a contradiction two paragraphs later. Suggested fix: move the ### Exchange Online subsection under Modern Authentication, or if those steps are still needed for Basic, restate what they apply to.
• Completeness — Line 39: "select the Microsoft.Graph Mail.Read, Mail.ReadWrite, and User.Read.All permissions" now appears inside the Basic Authentication section, but Graph permissions are what the new Modern Authentication section (lines 83–87) says the Graph implementation requires. Either this step belongs under Modern Authentication, or the reader needs a sentence explaining why Graph permissions are set up during a Basic authentication procedure.
• Structure — Lines 25–27: Removing "Review the related procedure that corresponds to your Exchange deployment: - Exchange Online - Exchange Server (On-Premise)" leaves ### Exchange Online (H3) and ## Exchange Server (On-Premise) (H2) as siblings in the reader's mind but at different heading levels, with no lead-in explaining that these are two alternative procedures. Suggested fix: restore a one-line lead-in and make both headings the same level (### under Basic Authentication).
• Clarity — Line 81: "The permissions required differ between the EWS and Graph implementations." "Implementation" isn't defined anywhere in this document, and a reader won't know it maps to the source types they pick in the console. Suggested fix: "The permissions you need depend on whether you use an Exchange (EWS) or Exchange (Graph) source type," with links to the two source pages.
• Consistency — Line 85: "Mail.Read-Allows the application to read..." uses a hyphen where the surrounding bullets use an em dash. Line 86 also uses " - necessary for the Exchange workflow actions" mid-sentence. Suggested fix: "Mail.Read—Allows..." and "Mail.ReadWrite—Allows the application to move and delete mail in all mailboxes, which the Exchange workflow actions require."
• Completeness — Lines 99–100: Step 2 points only to the Exchange Server (Graph) and Exchange Server (EWS) source pages, but this page is also the rights-assignment reference linked from both Exchange Mailbox pages. Suggested fix: add the Exchange Mailbox (Graph) and Exchange Mailbox (EWS) pages to the list, or reword to "Configure your Exchange source settings" with all four links.

docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/exchangegraph.md

• Completeness — Lines 21–22: Both Detection Period and Re-Index Period say the value "applies to all Exchange and Exchange Online source groups configured under the URL you enter in the URL text field," but this table has no URL field — the Exchange API Url row exists only on the EWS page. The reader is told to look for a control that isn't on this screen. Suggested fix: drop the URL clause, or replace it with whatever actually scopes the setting for Graph source groups (for example, the tenant selected in Cloud Environment).
• Completeness — Lines 15–22: The EWS page documents an Authentication Type row, but this page lists no authentication options at all. A reader arriving here from the EWS page won't know whether Graph source groups need a tenant ID, certificate, and application ID the way the Exchange Server (Graph) source does. Suggested fix: add an authentication row (or a short paragraph) stating what Graph dynamic source groups use, and link to the Azure AD app setup topic.
• Completeness — Line 9: This page never mentions the EWS deprecation that motivates its existence, and it doesn't link back to the Exchange (EWS) page. The EWS page's new warning points readers here, but the relationship is one-directional. Suggested fix: add a sentence such as "Use Exchange (Graph) dynamic source groups for all new Exchange Online source groups. To crawl on-premises Exchange servers, use Dynamic Source Groups — Exchange (EWS)."

docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeservergraph.md

• Completeness — Line 10: "To crawl mailboxes on an on-premises Exchange server, use Exchange Server (EWS)" names the alternative but doesn't link to it, while the parallel sentence on the Exchange Mailbox (Graph) page does link. Suggested fix: link to /docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserverews.md.
• Completeness — Lines 26–33: The Authentication table tells the reader where to get the Tenant ID, certificate thumbprint, and application ID, but never states which Graph API permissions the Azure AD app needs. The Exchange Server (EWS) page links to Configure Microsoft Exchange for Crawling and Classification for rights assignment; this page has no equivalent pointer. Suggested fix: add a lead-in sentence before the table linking to that topic for the required Mail.Read, Mail.ReadWrite, and User.Read.All permissions.
• Clarity — Line 43: "Define rules with wildcards to limit which mailboxes the product crawls" conflicts with every other Match Rules description in this PR, which calls them regular expressions — and the examples given (.*@netwrix.com, .*) are regular expressions, not wildcards. Suggested fix: "Define regular expressions that limit which mailboxes the product crawls."
• Structure — Line 43: "You must define at least one match rule" is buried at the end of the cell, after both examples. The reader needs the requirement before deciding what to enter. Suggested fix: lead with it — "You must define at least one match rule. Match rules are regular expressions. Examples: ..."
• Consistency — Line 22: "click the "wrench" icon next to Settings" leaves Settings unbolded, while every other UI element reference on this page is bold. Suggested fix: "next to Settings".

docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxgraph.md

• Completeness — Lines 19–26: Same gap as the Exchange Server (Graph) page — the Authentication section never states which permissions the Azure AD app requires, and doesn't link to Configure Microsoft Exchange for Crawling and Classification. The Exchange Mailbox (EWS) page provides that link in its Basic authentication row, so a reader switching to Graph loses it. Suggested fix: add the link in a lead-in sentence above the table.
• Completeness — Line 17: The EWS page has an explicit Authentication type field ("Select Modern (O365)"); this page has none, and doesn't say why. A reader comparing the two will look for the missing control. Suggested fix: add a sentence stating that Graph sources always use modern authentication, so there's no authentication type to select.
• Consistency — Line 9: "Use the Exchange Mailbox (Graph) source" doesn't bold the source name, while the EWS page opens with "Use the Exchange Mailbox (EWS) source". Suggested fix: bold the source name for consistency across the four Exchange source pages.
• Consistency — Line 37: "Select the Azure instance hosting the Exchange Online server." The same Cloud Environment field is described four different ways across this PR: "the Exchange Online server" here, "the Exchange Online tenancy" (exchangeservergraph.md line 41), "the Azure Cloud Environment hosting the Exchange tenancy" (sourcegroups/exchangegraph.md line 17), and "the Azure instance that hosts your SharePoint Online tenant" (sharepointonline.md line 31). "Exchange Online server" is also inaccurate — Exchange Online is a service, not a server the customer hosts. Suggested fix: standardize on one phrasing, for example "Select the Azure environment that hosts your Exchange Online tenant."

docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserverews.md

• Completeness — Line 10: "Netwrix recommends using Exchange Server (Graph) for any new sources" doesn't link to the Exchange Server (Graph) page, while the parallel sentence on the Exchange Mailbox (EWS) page does link to its Graph counterpart. Suggested fix: link to /docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeservergraph.md.
• Clarity — Line 10: "Due to the imminent deprecation of EWS" gives the reader no date to plan against, and "imminent" is a relative time reference that goes stale. The Exchange (EWS) source group page states the concrete deadline (April 2027). Suggested fix: "Microsoft is deprecating EWS for Exchange Online and will fully disable it in April 2027. Netwrix recommends using Exchange Server (Graph) for any new sources that crawl Exchange Online."
• Structure — Lines 31–35: Moving the note out of Authentication type: Modern authentication left the heading followed by three blank lines and then the lead-in sentence. Suggested fix: remove the extra blank lines.
• Consistency — Line 29: "click the "wrench" icon next to Settings in the bottom-left corner" drops the bold on Settings that the original line had, and there's a double space after "Step 3 –". Suggested fix: "Step 3 – To display all settings, click the "wrench" icon next to Settings in the bottom-left corner."
• Consistency — Line 66: "Define which mailboxes to crawl as part of an Exchange Server source" still uses the pre-rename name. Suggested fix: "as part of an Exchange Server (EWS) source."

docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md

• Clarity — Lines 11–12: "Due to the imminent deprecation of EWS for connecting to Exchange Online" — same relative time reference as the Exchange Server (EWS) page. Suggested fix: state the April 2027 disablement date, matching the warning on the Exchange (EWS) source group page.
• Clarity — Line 10: "using the Exchange Web Services (EWS)" reads awkwardly with the article, and this is the first spelled-out use in the body. Suggested fix: "...or in Exchange Online, using Exchange Web Services (EWS)."
• Consistency — Line 12: "for any new sources intended to crawl Exchange Online mailboxes" is passive-leaning and differs from the Exchange Server (EWS) wording for the same recommendation. Suggested fix: use identical phrasing on both pages so readers recognize it as the same guidance.

docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/exchangeews.md

• Completeness — Line 15: "you should use the Exchange (Graph) dynamic source group" doesn't link to the new page it's directing the reader to. Suggested fix: link to /docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/exchangegraph.md.
• Consistency — Line 15: "you should use" differs from the "Netwrix recommends using" construction used for the identical recommendation on the two EWS source pages. Suggested fix: "Netwrix recommends using the Exchange (Graph) dynamic source group for all new Exchange Online dynamic source groups."
• Structure — Line 13: The deprecation warning sits after the paragraph about toggling Basic and Advanced settings, so the reader gets a UI navigation detail before learning the feature is being retired. Suggested fix: move the warning directly below the H1, before the configuration paragraph.

docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/exchangemailbox.md

• Clarity — Line 9: "For the various Exchange sources" is vague — the reader can't tell which sources this page covers. Suggested fix: name them, for example "For the Exchange Mailbox (EWS), Exchange Mailbox (Graph), Exchange Server (EWS), and Exchange Server (Graph) sources..."
• Completeness — Line 12: Step 1 tells the reader to click Exchange Mailbox (EWS) or Exchange Mailbox (Graph), but the retitled page and the new opening line promise coverage of all Exchange sources. A reader with an Exchange Server source has no path through this procedure. Suggested fix: either add the server source types to Step 1, or narrow the title and intro back to mailbox sources.
• Clarity — Line 23: "wherever they are within any mailbox" — "any mailbox" is ambiguous between "every mailbox in the source" and "whichever mailbox you're configuring." Suggested fix: "wherever they appear in the mailboxes the source crawls."

docs/dataclassification/5.7/introduction/upgrade.md

• Clarity — Line 27: "Step 3 – Stop all NDC services. Netwrix recommends the following:" — the new warning at line 33 makes clear that stopping services is required, not recommended, so "Netwrix recommends the following" now undercuts the step. Suggested fix: "Step 3 – Stop all NDC services. Do the following:"
• Structure — Lines 37–38: Merging the index backup bullets into "Step 4 – Back up the Index files. Locate the folder containing the index files..." left the continuation line indented two spaces (" Files\Netwrix\Data Classification\Index"), a leftover from the bullet it used to be. Suggested fix: remove the leading indentation so the paragraph renders as one block.
• Completeness — Line 31: "If you upgrade a Distributed Query Server (DQS) environment, stop all services on all instances before upgrading any instance" overlaps with the Upgrading a DQS Environment section further down, which adds the primary-before-secondary ordering requirement. A reader who acts on Step 3 alone may upgrade instances in the wrong order. Suggested fix: add "See Upgrading a DQS Environment for the required upgrade order."
• Consistency — Line 56: "Distributed Query Server (DQS)" spells out the acronym a second time, now that line 31 defines it first. Suggested fix: use "DQS" alone in the later section.

docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md

• Completeness — Line 31: The new Cloud Environment row says "Select the Azure instance that hosts your SharePoint Online tenant" but doesn't tell the reader what the choices are or when the default is wrong. Most readers on commercial tenants won't know whether to change it. Suggested fix: name the available environments (for example, commercial and government clouds) and state which to select if unsure.
• Clarity — Line 9: "If you are an Office 365 customer" — contractions are encouraged in Netwrix documentation. Suggested fix: "If you're an Office 365 customer".

docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/overview.md

• No issues found.

docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md

• No issues found.

Summary

30 editorial suggestions across 10 files. Two are worth prioritizing: the Basic Authentication section in exchange.md now contradicts itself (it's scoped to on-premises but still contains an Exchange Online procedure with Graph permissions), and the new sourcegroups/exchangegraph.md describes settings as scoped by "the URL text field," a control that page's table doesn't have. The recurring themes elsewhere are missing cross-links to the new Graph pages and four different descriptions of the same Cloud Environment field.

Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

6 issues fixed, 8 skipped across 12 files

Category	Fixes
Dale: misplaced-modifiers	2
Dale: passive-voice	3
Dale: undefined-acronyms	1

Skipped (needs manual review)	Reason

| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeservergraph.md:10 — Dale: undefined-acronyms | EWS is undefined in this file, but it appears only as part of the literal source-type name 'Exchange Server (EWS)' shown in the product UI; expanding it inside the UI label would misname the control. |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxgraph.md:9 — Dale: undefined-acronyms | EWS appears only inside the link text 'Exchange Mailbox (EWS)', which is the UI source-type name and the title of the linked page, not body prose the reader must decode. |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md:24 — Dale: undefined-acronyms | EWS and Graph appear only in link text matching the destination page titles; the rule excludes acronyms outside body prose. |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/exchangemailbox.md:23 — Dale: misplaced-modifiers | 'Adding an exclusion of this type will match any folders...' attributes the matching to the act of adding rather than to the exclusion, but the gerund subject is not a participial modifier and rewriting it would restructure the sentence rather than move a modifier. |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailboxews.md:44 — Dale: positional-references | 'in the bottom' describes where a control sits in the product UI, not a cross-reference to other content on the page; the rule targets spatial references to document content. |
| docs/dataclassification/5.7/introduction/introduction/exchange/exchange.md:49 — Dale: wordiness | 'assign your user for Modern Authentication set up to this Role as well' is ambiguous — the intended meaning could not be determined with confidence, so rewriting risked changing it. |
| docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md:15 — Dale: wordiness | 'set up the resources needed to enable and configure Netwrix Data Classification' is vague about which resources, so a shorter rewrite could not be verified as meaning-preserving. |
| docs/dataclassification/5.7/introduction/upgrade.md:37 — Dale: wordiness | 'Back up the Index files. Locate the folder containing the index files ... and back it up.' is redundant, but condensing it would merge a step heading with its instruction and change the documented step structure. |

Ask @claude on this PR if you'd like an explanation of any fix.