Skip to content

Password Secure: Release 26.5.1#881

Merged
florian-berger-netwrix merged 1 commit into
devfrom
passwordsecure-release-26_5_1-2
May 11, 2026
Merged

Password Secure: Release 26.5.1#881
florian-berger-netwrix merged 1 commit into
devfrom
passwordsecure-release-26_5_1-2

Conversation

@florian-berger-netwrix
Copy link
Copy Markdown
Contributor

@florian-berger-netwrix florian-berger-netwrix commented May 11, 2026

  • Adds the changeset of the latest Password Secure version (26.5.1)

@github-actions
Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/passwordsecure/current/introduction/versionhistory/version_26.5.1.34120.md

  • Clarity — Line 15: "The web app" uses an informal short form inconsistent with the rest of this file (and surrounding section heading "Web application: Advanced view"). Suggested fix: "The web application no longer displays the file path of a document in the documents list…"
  • Completeness — Line 20: "Fixed heavy performance issues when using the Windows application" is vague — readers can't tell which scenarios were affected (large databases? specific actions? startup?). Suggested fix: name the affected scenario, for example: "Fixed performance issues that occurred when loading large password lists in the Windows application."
  • Structure — Line 18: The blank line between ## Fixed and ### Windows application is missing (line 18→19 has no separator unlike the other top-level sections, which have a blank line before the ### heading). Suggested fix: add a blank line after ## Fixed to match the formatting of ## New and ## Improved.
  • Structure — Line 17: Double blank line between the ## Improved bullet and ## Fixed. Suggested fix: collapse to a single blank line to match the spacing used between other sections.

docs/passwordsecure/current/introduction/versionhistory/version_history.md

  • No issues found.

docs/passwordsecure/current/msp_system.md

  • Structure — Line 22: **CAUTION:** is rendered as bold inline text instead of a :::warning admonition. Per Netwrix style, cautions/warnings belong in admonition blocks. Suggested fix:
    :::warning
    Don't use SQL Server Express edition because of its limitations.
    :::
    
  • Completeness — Line 22: "because of its limitations" is vague — readers don't know which limitations matter (database size cap, single-CPU restriction, memory limit, feature set?). Suggested fix: name the specific limits, e.g., "Don't use SQL Server Express edition — its 10 GB database size cap and limited memory don't support production MSP workloads."
  • Clarity — Lines 13 and 31: "The following minimum system requirements should manage around 10 customers…" — "should manage" is awkward; requirements don't manage anything. Suggested fix: "The following minimum system requirements support around 10 customers…" (apply to both the SQL Server and Application Server sections).
  • Structure — Line 45: RECOMMENDED:, is a malformed inline label (stray comma after the colon) and should also be an admonition. Suggested fix:
    :::tip
    Use one application server for a maximum of about 100 customers. If you reach 100 customers, set up a second application server or use load balancing between application servers.
    :::
    
  • Structure — Lines 48 and 50: Two more **CAUTION:** inline labels that should be :::warning admonitions. Suggested fix: wrap each in a :::warning::: block.
  • Clarity — Line 7 (heading "MSP System"): "MSP" appears in the H1 and throughout the page but isn't expanded until line 54 inside an admonition near the end. Suggested fix: expand on first use at the top of the page — for example, change the intro to: "To ensure optimal operation of a Managed Service Provider (MSP) system, provide the following hardware resources:"
  • Structure — Line 56: File is missing a trailing newline. Suggested fix: add a newline at end of file.

Summary

10 editorial suggestions across 3 files. 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
Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 5 skipped across 3 files

Skipped (needs manual review) Reason

| docs/passwordsecure/current/msp_system.md:13 — Dale: misplaced-modifiers | Subject-verb mismatch ('requirements should manage') is awkward but not a participial/dangling modifier; rewriting could shift meaning of 'less than 20 users each'. |
| docs/passwordsecure/current/msp_system.md:31 — Dale: misplaced-modifiers | Same pattern as line 13 — 'requirements should manage' is awkward but not a clear misplaced modifier; skipping to avoid altering meaning. |
| docs/passwordsecure/current/msp_system.md:45 — Dale: wordiness | 'you should use ... to handle a max of about 100 customers' is wordy, but the leading 'RECOMMENDED:,' is malformed admonition formatting (outside Dale's scope); any safe rewrite requires fixing the admonition structure too. |
| docs/passwordsecure/current/introduction/versionhistory/version_26.5.1.34120.md:20 — Dale: passive-voice | 'Fixed heavy performance issues...' is conventional changelog format with implicit subject under a '## Fixed' heading, not true passive voice. |
| docs/passwordsecure/current/introduction/versionhistory/version_26.5.1.34120.md:21 — Dale: passive-voice | Same changelog convention as line 20. |

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

@florian-berger-netwrix florian-berger-netwrix merged commit c8691af into dev May 11, 2026
10 checks passed
@florian-berger-netwrix florian-berger-netwrix deleted the passwordsecure-release-26_5_1-2 branch May 11, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants