Skip to content

AB#401336#756

Merged
claudi-dev merged 4 commits intodevfrom
feature/419088
Apr 14, 2026
Merged

AB#401336#756
claudi-dev merged 4 commits intodevfrom
feature/419088

Conversation

@claudi-dev
Copy link
Copy Markdown
Contributor

No description provided.

@claudi-dev claudi-dev requested a review from a team as a code owner April 14, 2026 18:40
@claudi-dev claudi-dev requested review from leo-st-nwx and lferreronetwrix and removed request for leo-st-nwx April 14, 2026 18:41
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@claudi-dev
Copy link
Copy Markdown
Contributor Author

@claude Apply suggested fix to Line 128

Replace 'objects' with 'components' for consistency with table updates
and add missing terminal period.

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/platgovsalesforce/changemanagement/setting_up_policies.md

  • Completeness — Line 95: After removing the misplaced Health Check text from the Control Changes section, the section now contains only "Controls the change level required for different types of changes." plus an image. This gives readers no context about what control changes govern or what options to configure. Suggested fix: Add a brief description of what falls under control changes — for example, the types of metadata or settings this section applies to — similar to the opening descriptions in other sections.

  • Completeness — Lines 106–113 (Health Check Changes section): The descriptive paragraph was correctly moved here from the Control Changes section, but the action instruction was removed in the same edit. Previously the section told readers: "Select the change level for Health Check Changes: None, Log Changes Only, Change Request, Sandbox Development & Testing, or Full Software Development Lifecycle." Without this, readers see a description and an image but no guidance on what to do. Suggested fix: Restore the instruction for selecting the change level, either as a prose sentence or a procedure step (e.g., "Select the change level that applies to Health Check Changes. The available levels are: None, Log Changes Only, Change Request, Sandbox Development & Testing, and Full Software Development Lifecycle.").

  • Completeness — Line 128 (Uncategorized Changes section): "This change control level applies to any components not included in the other categories." explains the purpose of the section but gives readers nothing actionable. The previous Customization Policies section had a named field with instructions. Suggested fix: Add what the reader needs to do here — either describe the available change level options or explain what configuration fields appear in this section of the UI.

  • Structure — Document-level (Details list, lines 32 and 34, not modified in this PR but made inconsistent by it): The Details overview list still names "Customization Policies" (renamed to "Uncategorized Changes" in this PR) and "Change Enablement Defaults" (removed in this PR). Readers who use that list to orient themselves before reading will be confused when the section names don't match. Suggested fix: Update line 32 from "Customization Policies" to "Uncategorized Changes" and remove line 34 ("Change Enablement Defaults") from the Details list to reflect the sections that now exist.

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.

@github-actions
Copy link
Copy Markdown
Contributor

Auto-Fix Summary

1 issues fixed, 0 skipped across 1 files

Category Fixes
Dale: passive-voice 1

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

Copy link
Copy Markdown
Contributor

@lferreronetwrix lferreronetwrix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@claudi-dev claudi-dev merged commit c223f59 into dev Apr 14, 2026
10 checks passed
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