From 959dd92eb73c88a87c503547c18239cf9e146ac8 Mon Sep 17 00:00:00 2001 From: james-haytko_nwx Date: Fri, 27 Feb 2026 19:32:23 -0600 Subject: [PATCH 1/7] doc review test 11 --- docs/passwordsecure/9.2/index.md | 8 ++++---- docs/passwordsecure/9.3/index.md | 12 ++++++------ 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/passwordsecure/9.2/index.md b/docs/passwordsecure/9.2/index.md index f25fed5e95..95bb5969cc 100644 --- a/docs/passwordsecure/9.2/index.md +++ b/docs/passwordsecure/9.2/index.md @@ -9,17 +9,17 @@ sidebar_position: 1 ## Users depend on passwords Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, -and they need to be professionally managed. Passwords should be safe, have at least 12 characters, +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, changing every month, and including uppercase and lowercase as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet this challenge in private settings. In a large corporate environment, you wouldn’t be able to -adequately manage this task without the use of a professional password management tool. +adequately manage this task without the use of a professional password management tool. I love passwords ## Scalability -The scalability of Netwrix Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large +The scaleability of Netwrix Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor behind our development to meet the ever-changing requirements of modern and safety-conscious companies. NPS is the perfect software solution for companies that wish to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption -level. +level. Bad passwords are for buffoons diff --git a/docs/passwordsecure/9.3/index.md b/docs/passwordsecure/9.3/index.md index d20f964489..95bb5969cc 100644 --- a/docs/passwordsecure/9.3/index.md +++ b/docs/passwordsecure/9.3/index.md @@ -8,18 +8,18 @@ sidebar_position: 1 ## Users depend on passwords -Passwords are used constantly and everywhere, -and they must be professionally managed. Passwords should be safe, have at least 12 characters, +Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, changing every month, and including uppercase and lowercase as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporateee environment, you wouldn’t be able to -adequately manage this task without the use of a professional password management tool. +this challenge in private settings. In a large corporate environment, you wouldn’t be able to +adequately manage this task without the use of a professional password management tool. I love passwords ## Scalability -The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large +The scaleability of Netwrix Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor behind our development to meet the ever-changing requirements of modern and safety-conscious companies. NPS is the perfect software solution for companies that wish to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption -level. +level. Bad passwords are for buffoons From a27a29fffc6c7c3735ccd89a3205f4df4e14b230 Mon Sep 17 00:00:00 2001 From: james-haytko_nwx Date: Mon, 2 Mar 2026 10:36:30 -0600 Subject: [PATCH 2/7] Added CLAUDE.md to docs and updated style guide --- CLAUDE.md | 142 +++++++++++++++++++++++++++++++++++++++++ netwrix_style_guide.md | 4 +- 2 files changed, 144 insertions(+), 2 deletions(-) create mode 100644 CLAUDE.md diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000000..d98bb5013e --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,142 @@ +# Netwrix Product Documentation — Claude Code Guide + +A Docusaurus v3.8.1 site serving documentation for 27+ Netwrix security products across 6 categories, with multi-version support and a centralized configuration system. + +## Development Commands + +```bash +npm run start # Dev server on port 4500 +npm run build # Production build (16 GB heap pre-configured) +npm run clear # Clear Docusaurus cache +npm run serve # Serve production build after build + +# Build/run a single product for faster iteration: +export DOCS_PRODUCT="pingcastle" +npm run start +``` + +Available product IDs are defined in `src/config/products.js`. + +## Architecture + +### Single Source of Truth: `src/config/products.js` + +All product and version configuration lives here. Never manually edit `docusaurus.config.js` to add products, routes, or plugins — `products.js` auto-generates all of that. Changing a product means changing this file. + +### Versioned Documentation + +Docs live at `docs///` (for example, `docs/accessanalyzer/12.0/`). Edits to one version do not propagate to others — update each version that needs the change explicitly. + +Single-version (SaaS) products use `docs//` without a version subfolder. + +### Sidebars + +Each product version has a sidebar config in `sidebars//.js` (or `sidebars/.js` for single-version). These are separate from the doc content. Most use `autogenerated` and don't need manual editing unless custom ordering is required. + +### KB (Knowledge Base) System + +`docs/kb/` is the canonical source for KB articles. The script `scripts/copy-kb-to-versions.mjs` distributes articles into versioned product folders at build time (runs automatically as a pre-build step). + +**Never manually copy KB articles into versioned product folders.** Edit the source in `docs/kb/` and control distribution via `kb_allowlist.json`. + +## Adding Content + +### New product + +1. Add an entry to the `PRODUCTS` array in `src/config/products.js` +2. Create `docs//` +3. Create `sidebars/.js` + +### New version of an existing product + +1. Update the `versions` array for that product in `src/config/products.js` — set `isLatest: true` on the new version and `isLatest: false` on the previous one +2. Create `docs///` +3. Create `sidebars//.js` + +### New product category + +Add to the `PRODUCT_CATEGORIES` array in `src/config/products.js`. + +## Writing Style + +The full standards are in `netwrix_style_guide.md` at the project root. Read it when in doubt. + +**Always run Vale before finishing any documentation edit. Run it iteratively — fix all reported issues, then run again until Vale reports zero errors.** Fixes can occasionally introduce new violations. + +```bash +vale +``` + +Vale enforces 26 Netwrix-specific rules in CI. Rules are in `.vale/styles/Netwrix/`. + +If Vale isn't installed, install it first: + +```bash +# macOS +brew install vale + +# Windows +choco install vale +# or download from https://github.com/errata-ai/vale/releases + +# Linux +snap install vale --edge +``` + +### Fixing Vale errors + +Most errors are simple substitutions — Vale reports the exact file, line, and column. Three rules require extra care: + +- **`NoteThat`** — Replace inline "Note that..." or "Please note..." with a Docusaurus admonition block: + ```md + :::note + Content here. + ::: + ``` + Use `:::warning` for warnings and `:::tip` for tips. + +- **`BoilerplateCrossRef`** and **`WeakLinkText`** — Read the surrounding context and the link destination before rewriting. The fix must reflect what the reader will actually find at the destination. + +- **`ImpersonalConstructions`** — Read the full sentence before rewriting. Restructure with an active subject rather than simply removing the flagged phrase. + +### Rules Vale doesn't catch + +Vale handles pattern-based violations automatically — run it and fix everything it reports. The following rules require judgment that Vale can't apply: + +**Voice and structure** +- Active voice and present tense throughout +- Second person ("you") — address the reader directly +- Contractions are encouraged: don't, can't, you'll +- Keep sentences to one idea per sentence +- Write for a global audience — avoid metaphors, idioms, and culturally specific references that don't translate +- Omit "currently", "presently", and "as of this writing" — documentation should read as permanently accurate + +**Document structure** +- Order: overview → prerequisites → procedures +- Task headings use imperative verbs: "Configure the monitoring plan" +- Concept/overview headings use gerunds: "Configuring the monitoring plan" +- Examples immediately follow the concept they illustrate +- Images: store in `static/img/product_docs//`, use `.webp`, reference with absolute paths (`/img/product_docs/...`) + +**Terminology** +- Spell out acronyms on first use: "group Managed Service Account (gMSA)" +- Use angle brackets for placeholders: `` not `[report-name]` +- Sentence case for feature names; capitalize Netwrix product names correctly +- Oxford comma required in lists + +## CI/CD Context + +**Vale linter** — runs on every PR touching `.md` files, posts inline review comments. Does not block merges but issues are visible. + +**Doc reviewer** (Claude Opus 4.6) — runs on every PR, reads full files, categorizes issues as "in PR changes" vs "preexisting", and posts inline suggestions reviewers can apply with one click. + +**Doc fixer** — triggered by an `@claude` comment on a PR. Claude applies fixes and pushes. Fork PRs cannot be pushed to and receive a notice instead. + +**Branch workflow** — PRs target `dev`. Merges to `main` trigger production deployment. + +## Common Mistakes to Avoid + +- Don't add products or routes by editing `docusaurus.config.js` — use `src/config/products.js` +- Don't copy KB content manually into versioned product folders — it's managed by the KB script +- Don't skip Vale before submitting — it will catch issues in CI anyway +- Don't target `main` in PRs — use `dev` diff --git a/netwrix_style_guide.md b/netwrix_style_guide.md index 5f1c449b02..7de66e7f8c 100644 --- a/netwrix_style_guide.md +++ b/netwrix_style_guide.md @@ -153,8 +153,8 @@ This style guide establishes the specific rules for grammar, punctuation, and st | Rule | Description | Do | Don't | |------|-------------|-----|-------| | **Headings** | Use sentence case for headings. Capitalize only the first word and proper nouns. | Configure the monitoring plan | Configure the Monitoring Plan

Configure The Monitoring Plan | -| **Headings with infinitives** | Start task-based headings with infinitives. | Install Netwrix Auditor

Configure monitoring plans | Installing Netwrix Auditor (in a heading for a section with multiple steps)

Configuring monitoring plans | -| **Headings with gerunds** | Start headings with gerunds ("-ing" verbs) when the topics are concepts, overviews, or when they describe continuous actions. | Reviewing audit logs | Review audit logs (unless it's a task) | +| **Task-based headings** | Start task-based headings with imperative verbs. | Install Netwrix Auditor

Configure monitoring plans | Installing Netwrix Auditor (in a heading for a section with multiple steps)

Configuring monitoring plans | +| **Conceptual headings** | Start headings with gerunds ("-ing" verbs) when the topics are concepts, overviews, or when they describe continuous actions. | Reviewing audit logs | Review audit logs (unless it's a task) | | **Bold text** | Use bold for UI elements, buttons, and menu items. | Click **Add** to create a new monitoring plan. | Click "Add" to create a new monitoring plan.

Click Add to create a new monitoring plan. | | **Italic text** | Avoid italics. | This process is known as agentless monitoring. | Click the *Add* button. | | **Code formatting** | Use monospace formatting for code, commands, file paths, and technical values. | Run the `Get-NWXUser`cmdlet to retrieve user information.

Edit the`C:\Program Files\Netwrix\config.xml` file. | Run the Get-NWXUser cmdlet to retrieve user information.

Edit the C:\\Program Files\\Netwrix\\config.xml file. | From a2d4d0489afa6d8ee5dc11f4e424af8e0224dc57 Mon Sep 17 00:00:00 2001 From: james-haytko_nwx Date: Mon, 2 Mar 2026 10:48:28 -0600 Subject: [PATCH 3/7] doc reviewer test 12 preexisting issues --- docs/passwordsecure/9.2/index.md | 2 +- docs/passwordsecure/9.3/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/passwordsecure/9.2/index.md b/docs/passwordsecure/9.2/index.md index 95bb5969cc..c2668f6ef9 100644 --- a/docs/passwordsecure/9.2/index.md +++ b/docs/passwordsecure/9.2/index.md @@ -13,7 +13,7 @@ and they need to be professionally managed. Passwords should be safe, have at le including uppercase and lowercase as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet this challenge in private settings. In a large corporate environment, you wouldn’t be able to -adequately manage this task without the use of a professional password management tool. I love passwords +adequately manage this task without the use of a professional password management tool. I love passwordsaa ## Scalability diff --git a/docs/passwordsecure/9.3/index.md b/docs/passwordsecure/9.3/index.md index 95bb5969cc..d81fd81a2f 100644 --- a/docs/passwordsecure/9.3/index.md +++ b/docs/passwordsecure/9.3/index.md @@ -22,4 +22,4 @@ companies, and global corporations. The flexibility required for this task is th behind our development to meet the ever-changing requirements of modern and safety-conscious companies. NPS is the perfect software solution for companies that wish to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption -level. Bad passwords are for buffoons +level. Bad passwords are for buffoonsaa From b3f627008f865f753623172cea42974d50746d19 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Mon, 2 Mar 2026 17:13:33 +0000 Subject: [PATCH 4/7] Fix all documentation issues in Password Secure 9.2 and 9.3 Fixed both PR changes and preexisting issues: - Corrected run-on sentences with unclear parallel structure - Removed nonsensical and unprofessional text fragments - Fixed misspelling: scaleability -> scalability - Removed duplicate product name - Replaced first-person plural language - Changed "wish to" to "want to" All changes verified with Vale linter (0 errors, 0 warnings, 0 suggestions). Co-authored-by: jth-nw --- docs/passwordsecure/9.2/index.md | 13 ++++++------- docs/passwordsecure/9.3/index.md | 13 ++++++------- 2 files changed, 12 insertions(+), 14 deletions(-) diff --git a/docs/passwordsecure/9.2/index.md b/docs/passwordsecure/9.2/index.md index c2668f6ef9..987328ea46 100644 --- a/docs/passwordsecure/9.2/index.md +++ b/docs/passwordsecure/9.2/index.md @@ -9,17 +9,16 @@ sidebar_position: 1 ## Users depend on passwords Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, -and they need to be professionally managed. Passwords should be safe, have at least 12 characters, changing every month, and -including uppercase and lowercase as well as special characters. In the best case, a separate access +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. Change them regularly (at least monthly). In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet this challenge in private settings. In a large corporate environment, you wouldn’t be able to -adequately manage this task without the use of a professional password management tool. I love passwordsaa +adequately manage this task without the use of a professional password management tool. ## Scalability -The scaleability of Netwrix Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large +The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor -behind our development to meet the ever-changing requirements of modern and safety-conscious -companies. NPS is the perfect software solution for companies that wish to effectively manage +behind the development to meet the ever-changing requirements of modern and safety-conscious +companies. NPS is the perfect software solution for companies that want to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption -level. Bad passwords are for buffoons +level. diff --git a/docs/passwordsecure/9.3/index.md b/docs/passwordsecure/9.3/index.md index d81fd81a2f..987328ea46 100644 --- a/docs/passwordsecure/9.3/index.md +++ b/docs/passwordsecure/9.3/index.md @@ -9,17 +9,16 @@ sidebar_position: 1 ## Users depend on passwords Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, -and they need to be professionally managed. Passwords should be safe, have at least 12 characters, changing every month, and -including uppercase and lowercase as well as special characters. In the best case, a separate access +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. Change them regularly (at least monthly). In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet this challenge in private settings. In a large corporate environment, you wouldn’t be able to -adequately manage this task without the use of a professional password management tool. I love passwords +adequately manage this task without the use of a professional password management tool. ## Scalability -The scaleability of Netwrix Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large +The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor -behind our development to meet the ever-changing requirements of modern and safety-conscious -companies. NPS is the perfect software solution for companies that wish to effectively manage +behind the development to meet the ever-changing requirements of modern and safety-conscious +companies. NPS is the perfect software solution for companies that want to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption -level. Bad passwords are for buffoonsaa +level. From ec3a154e99a12879fda3185eca9c58580d28a5bc Mon Sep 17 00:00:00 2001 From: james-haytko_nwx Date: Mon, 2 Mar 2026 11:17:04 -0600 Subject: [PATCH 5/7] passwordsecure fixes --- docs/passwordsecure/9.1/index.md | 17 +++++++---------- docs/passwordsecure/9.2/index.md | 8 +++----- docs/passwordsecure/9.3/index.md | 8 +++----- 3 files changed, 13 insertions(+), 20 deletions(-) diff --git a/docs/passwordsecure/9.1/index.md b/docs/passwordsecure/9.1/index.md index 5e385247f6..f78f5565df 100644 --- a/docs/passwordsecure/9.1/index.md +++ b/docs/passwordsecure/9.1/index.md @@ -6,20 +6,17 @@ sidebar_position: 1 # Why Netwrix Password Secure? -## Users depend on passwords - -Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, -and they need to be professionally managed. Passwords should be safe, have at least 12 characters, -including uppercase and lowercase as well as special characters. In the best case, a separate access +Users depend on passwords now more than ever in their day-to-day business worldwide. Passwords are used constantly and everywhere, +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporate environment, you wouldn’t be able to +this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. adequately manage this task without the use of a professional password management tool. ## Scalability -The scalability of Netwrix Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large +The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor -behind our development to meet the ever-changing requirements of modern and safety-conscious -companies. NPS is the perfect software solution for companies that wish to effectively manage +behind the development to meet the ever-changing requirements of modern and safety-conscious +companies. NPS is the perfect software solution for companies that want to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption -level. \ No newline at end of file +level. diff --git a/docs/passwordsecure/9.2/index.md b/docs/passwordsecure/9.2/index.md index 987328ea46..f78f5565df 100644 --- a/docs/passwordsecure/9.2/index.md +++ b/docs/passwordsecure/9.2/index.md @@ -6,12 +6,10 @@ sidebar_position: 1 # Why Netwrix Password Secure? -## Users depend on passwords - -Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, -and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. Change them regularly (at least monthly). In the best case, a separate access +Users depend on passwords now more than ever in their day-to-day business worldwide. Passwords are used constantly and everywhere, +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporate environment, you wouldn’t be able to +this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. adequately manage this task without the use of a professional password management tool. ## Scalability diff --git a/docs/passwordsecure/9.3/index.md b/docs/passwordsecure/9.3/index.md index 987328ea46..f78f5565df 100644 --- a/docs/passwordsecure/9.3/index.md +++ b/docs/passwordsecure/9.3/index.md @@ -6,12 +6,10 @@ sidebar_position: 1 # Why Netwrix Password Secure? -## Users depend on passwords - -Now more than ever in their day-to-day business worldwide. They are used constantly and everywhere, -and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. Change them regularly (at least monthly). In the best case, a separate access +Users depend on passwords now more than ever in their day-to-day business worldwide. Passwords are used constantly and everywhere, +and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporate environment, you wouldn’t be able to +this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. adequately manage this task without the use of a professional password management tool. ## Scalability From 60d9d554313e11ce2bdc8ea5098ac0b24d0b42fe Mon Sep 17 00:00:00 2001 From: james-haytko_nwx Date: Mon, 2 Mar 2026 11:24:01 -0600 Subject: [PATCH 6/7] Speed up doc reviewer by using shallow checkout Replace fetch-depth: 0 (full clone) with fetch-depth: 1 plus a targeted fetch of just the base commit. This gives git everything it needs for the PR diff without downloading the entire repository history. Generated with AI Co-Authored-By: Claude Code --- .github/workflows/claude-documentation-reviewer.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/claude-documentation-reviewer.yml b/.github/workflows/claude-documentation-reviewer.yml index 7de88b35ba..9f5499e494 100644 --- a/.github/workflows/claude-documentation-reviewer.yml +++ b/.github/workflows/claude-documentation-reviewer.yml @@ -23,7 +23,10 @@ jobs: with: # Check out by SHA to prevent TOCTOU attacks from forks. ref: ${{ github.event.pull_request.head.sha }} - fetch-depth: 0 + fetch-depth: 1 + + - name: Fetch base commit for diff + run: git fetch --depth=1 origin ${{ github.event.pull_request.base.sha }} - name: Get changed markdown files id: changed-files From 28ce2a9c91ab372e764c98b9c665adf02e46f3bf Mon Sep 17 00:00:00 2001 From: jth-nw Date: Mon, 2 Mar 2026 11:29:45 -0600 Subject: [PATCH 7/7] Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- docs/passwordsecure/9.1/index.md | 7 +++---- docs/passwordsecure/9.2/index.md | 7 +++---- docs/passwordsecure/9.3/index.md | 7 +++---- 3 files changed, 9 insertions(+), 12 deletions(-) diff --git a/docs/passwordsecure/9.1/index.md b/docs/passwordsecure/9.1/index.md index f78f5565df..be5beb4363 100644 --- a/docs/passwordsecure/9.1/index.md +++ b/docs/passwordsecure/9.1/index.md @@ -6,17 +6,16 @@ sidebar_position: 1 # Why Netwrix Password Secure? -Users depend on passwords now more than ever in their day-to-day business worldwide. Passwords are used constantly and everywhere, +Users depend on passwords in their day-to-day business worldwide. Passwords are used constantly and everywhere, and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. -adequately manage this task without the use of a professional password management tool. +this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. ## Scalability The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor behind the development to meet the ever-changing requirements of modern and safety-conscious -companies. NPS is the perfect software solution for companies that want to effectively manage +companies. NPS is a software solution for companies that want to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption level. diff --git a/docs/passwordsecure/9.2/index.md b/docs/passwordsecure/9.2/index.md index f78f5565df..be5beb4363 100644 --- a/docs/passwordsecure/9.2/index.md +++ b/docs/passwordsecure/9.2/index.md @@ -6,17 +6,16 @@ sidebar_position: 1 # Why Netwrix Password Secure? -Users depend on passwords now more than ever in their day-to-day business worldwide. Passwords are used constantly and everywhere, +Users depend on passwords in their day-to-day business worldwide. Passwords are used constantly and everywhere, and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. -adequately manage this task without the use of a professional password management tool. +this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. ## Scalability The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor behind the development to meet the ever-changing requirements of modern and safety-conscious -companies. NPS is the perfect software solution for companies that want to effectively manage +companies. NPS is a software solution for companies that want to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption level. diff --git a/docs/passwordsecure/9.3/index.md b/docs/passwordsecure/9.3/index.md index f78f5565df..be5beb4363 100644 --- a/docs/passwordsecure/9.3/index.md +++ b/docs/passwordsecure/9.3/index.md @@ -6,17 +6,16 @@ sidebar_position: 1 # Why Netwrix Password Secure? -Users depend on passwords now more than ever in their day-to-day business worldwide. Passwords are used constantly and everywhere, +Users depend on passwords in their day-to-day business worldwide. Passwords are used constantly and everywhere, and they need to be professionally managed. Passwords should be safe, have at least 12 characters, and include uppercase and lowercase characters as well as special characters. In the best case, a separate access password should be used for each account. It should be changed regularly. It is hard enough to meet -this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. -adequately manage this task without the use of a professional password management tool. +this challenge in private settings. In a large corporate environment, adequately managing passwords without the use of a professional password management tool is difficult. ## Scalability The scalability of Netwrix Password Secure (NPS) makes it suitable for use in SMEs, large companies, and global corporations. The flexibility required for this task is the driving factor behind the development to meet the ever-changing requirements of modern and safety-conscious -companies. NPS is the perfect software solution for companies that want to effectively manage +companies. NPS is a software solution for companies that want to effectively manage security-relevant data such as passwords, documents, or certificates at a very high encryption level.