Skip to content

EPP Changes to be committed:#1023

Merged
krzysztofstaszalek merged 2 commits into
devfrom
eppminor20260527
May 27, 2026
Merged

EPP Changes to be committed:#1023
krzysztofstaszalek merged 2 commits into
devfrom
eppminor20260527

Conversation

@krzysztofstaszalek
Copy link
Copy Markdown
Collaborator

modified:   docs/endpointprotector/gettingstarted.md
modified:   docs/endpointprotector/index.md

	modified:   docs/endpointprotector/gettingstarted.md
	modified:   docs/endpointprotector/index.md
@github-actions
Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/endpointprotector/gettingstarted.md

  • Consistency — Lines 20–23: Each bullet in the System Requirements list now ends with a trailing comma (Windows, macOS, Linux,). Bulleted items should not end with commas. Suggested fix: Remove the trailing comma from each of the four bullets.
  • Consistency — Line 21: "CPU x86 64bit or ARM64 bit" is the only bullet in this list missing the Label: value pattern used by the surrounding items, and the bit-width formatting is inconsistent (64bit vs. ARM64 bit). Suggested fix: - CPU: x86 64-bit or ARM 64-bit
  • Structure — Lines 150 and 155: "Method 1:" and "Method 2:" appear as plain-text labels inside an indented bullet list, with no visual hierarchy to distinguish them from regular content. A reader scanning the page may miss that these are alternative deployment paths. Suggested fix: Bold the labels (**Method 1: Install from a USB drive** / **Method 2: Deploy through EPP Notifier**) or promote them to sub-bullets with clear descriptions.
  • Clarity — Line 156: "EPP" appears here for the first time in this file without being spelled out. Netwrix style requires defining acronyms on first use. Suggested fix: "Click the Endpoint Protector (EPP) Notifier Deploy button..." — or simply use "Endpoint Protector Notifier" if EPP is not needed elsewhere in this document.
  • Completeness — Line 156: "next to the USB drive in the device list" doesn't tell the reader where the device list lives in the Management Console. Method 1 above tells the reader exactly where to download and run the installer, but Method 2 assumes the reader already knows how to reach the device list. Suggested fix: Add a navigation path, e.g., "On the Devices page, click the Deploy button in the EPP Notifier column next to the USB drive."

docs/endpointprotector/index.md

  • Accuracy — Line 35: The sentence states "Netwrix Endpoint Protector 2605 is now the current supported version" but then recommends "upgrading to version 2602 or later." If 2605 is current, the recommendation should also point to 2605. Suggested fix: "Netwrix recommends upgrading to version 2605 or later."
  • Clarity — Line 35 vs. lines 39–40: The opening statement names 2605 as "the current supported version," but the Support Status Overview table below lists the EPP Server at 2604 and the EPP Client & EE at 2605. A reader will be uncertain which component "2605" refers to in the lead sentence. Suggested fix: Distinguish the components in the opening statement, e.g., "Netwrix Endpoint Protector Server 2604 and Client/EE 2605 are now the current supported versions."
  • Consistency — Line 41: The new bullet ends with a period (...technical assistance.), while the two preceding bullets in the same list (lines 39–40) do not end with periods. Suggested fix: Either remove the trailing period from line 41 or add periods to lines 39 and 40 so all three bullets match.

Summary

8 editorial suggestions across 2 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

7 issues fixed, 6 skipped across 2 files

Category Fixes
Substitutions 1
BoilerplateCrossRef (rewrite) 5
Dale: wordiness 1
Skipped (needs manual review) Reason

| docs/endpointprotector/gettingstarted.md:31 — Dale: passive-voice | 'IP address configured during the deployment process' is a natural participial phrase; active rewrite would change meaning. |
| docs/endpointprotector/gettingstarted.md:146 — Dale: passive-voice | 'USB devices recognized as Trusted Device Level 1' is a natural participial modifier; rewriting risks distorting the description. |
| docs/endpointprotector/gettingstarted.md:9 — Dale: minimizing-difficulty | 'Welcome to...your solution' is marketing tone but does not minimize a user task; not covered by Dale rules. |
| docs/endpointprotector/gettingstarted.md:12 — Dale: minimizing-difficulty | 'connect seamlessly' describes device behavior, not a user task — ambiguous whether this minimizes difficulty. |
| docs/endpointprotector/index.md:20 — Dale: passive-voice | 'sensitive data remains protected' is passive but the active alternative would alter the meaning. |
| docs/endpointprotector/index.md:15 — Dale: wordiness | 'robust suite of features' is marketing tone; trimming would change meaning and Dale does not have a marketing rule. |

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

@krzysztofstaszalek krzysztofstaszalek merged commit 2ec8bab into dev May 27, 2026
10 checks passed
@krzysztofstaszalek krzysztofstaszalek deleted the eppminor20260527 branch May 27, 2026 16:54
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.

3 participants