NPS-D: update landing page and fix version numbers in container deployment docs

[TM-PO-Netwrix]

Summary

• Updated NPS-D landing page (index.md): removed duplicate title/headings, removed version number from title, added upgrade note highlighting new features in 26.03+ (Entra ID integration, container-based deployment, active development)
• Updated container-based deployment version examples from 2.22.14/26.03.2 to 2.22.13/26.03.1 across overview.md and deploysecureone.md

Test plan

• Verify landing page renders correctly with note at the bottom
• Verify version numbers are consistent across container-based deployment pages
• Confirm build passes with no broken anchors

Generated with AI

Co-Authored-By: Claude Code ai@netwrix.com

[github-actions]

Documentation PR Review

Editorial Review

docs/privilegesecurediscovery/2.22/index.md

• Clarity — Line 18: The acronym "NPS-D" appears for the first time in the "Release Lines" section without being introduced. The opening paragraph uses the full product name "Netwrix Privilege Secure for Discovery" but does not establish the abbreviation. Per the style guide, acronyms should be spelled out on first use. Suggested fix: introduce the acronym in the opening paragraph — "Netwrix Privilege Secure for Discovery (NPS-D, formerly Remediant SecureONE) enables IT administrators..."
• Clarity — Line 26: "This documentation covers both release lines." This page lives under the versioned 2.22/ folder, so a reader who selected 2.22 from the version switcher may be confused that the index describes both 2.22 and 26.03+. Suggested fix: clarify the scope — for example, "Although this section is grouped under the 2.22 documentation, the content covers both release lines unless noted otherwise."
• Completeness — Line 20: "Legacy release line, approaching end of support." Readers (especially newer users) have no way to gauge how soon support ends or what "approaching" means here. Suggested fix: link to the Netwrix product lifecycle or support policy page, or state the end-of-support timeframe inline.

docs/privilegesecurediscovery/2.22/installation/containerbaseddeployment/deploysecureone.md

No issues found.

docs/privilegesecurediscovery/2.22/installation/containerbaseddeployment/overview.md

No issues found.

Summary

3 editorial suggestions across 1 file (2 other files contained version-number updates only). 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

3 issues fixed, 7 skipped across 3 files

Category	Fixes
Dale: passive-voice	1
Dale: wordiness	2

Skipped (needs manual review)	Reason

| docs/privilegesecurediscovery/2.22/index.md:13 — Dale: wordiness | Marketing-style product description ('effectively preventing... significantly reducing...') — modifiers may be intentional emphasis; changing meaning risk too high |
| docs/privilegesecurediscovery/2.22/index.md:21 — Dale: passive-voice | 'actively developed' is a participial adjective that mirrors the parallel structure of the adjacent '2.22' bullet ('approaching end of support'); preserving parallelism |
| docs/privilegesecurediscovery/2.22/index.md:9 — Dale: wordiness | 'enables...to have visibility' is wordy but part of established product description; refactor risks changing the marketed framing |
| docs/privilegesecurediscovery/2.22/installation/containerbaseddeployment/deploysecureone.md:165 — Dale: passive-voice | 'installed automatically by setup if missing' appears in a Prerequisites list using fragment form; rewriting to active voice would break the list pattern |
| docs/privilegesecurediscovery/2.22/installation/containerbaseddeployment/deploysecureone.md:166 — Dale: passive-voice | Same Prerequisites fragment pattern as line 165 |
| docs/privilegesecurediscovery/2.22/installation/containerbaseddeployment/deploysecureone.md:167 — Dale: passive-voice | '(other distributions not tested)' is a short parenthetical fragment; rewrite to active would need to introduce a subject ('Netwrix has not tested...'), changing the form |
| docs/privilegesecurediscovery/2.22/installation/containerbaseddeployment/deploysecureone.md:164 — Dale: passive-voice | 'AWS CLI installed and authenticated' is a Prerequisites list fragment; same pattern as other list items |

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