You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarity — Line 14: "by separating search values by space" uses "by" twice in a row, creating awkward grammar. Suggested fix: "by separating search values with a space."
Clarity — Line 30: Uses second person ("When you use...") while the rest of the changelog uses third person ("When filtering...", "the application now transmits..."). This creates a POV inconsistency within the same section. Suggested fix: "When the 'Exchange form' is used in the Windows application with 'Create as new' selected as the action for the field, the application now transmits the password value correctly."
Clarity — Line 36: The sentence "Following the suggested Content-Security-Policy header for the web server, it wasn't possible to cause any damage." is difficult to parse. The participial phrase "Following the suggested..." has no clear subject, and "cause any damage" is vague for a security disclosure. Suggested fix: "With the recommended Content-Security-Policy header configured on the web server, this issue did not allow execution of arbitrary scripts."
Clarity — Line 50: "It is possible now to permanently delete users that created an API key." has two issues: (1) the word order "possible now" is inverted — standard English puts the adverb before "possible"; (2) "users that" should be "users who" when referring to people. Suggested fix: "It is now possible to permanently delete users who created an API key."
Summary
4 editorial suggestions across 1 file. 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the changeset of the new Password Secure version (26.4.10)