Skip to content

Revise USN check command and script instructions - #1275

Draft
ShameenShahid wants to merge 2 commits into
devfrom
ShameenShahid-patch-2
Draft

Revise USN check command and script instructions#1275
ShameenShahid wants to merge 2 commits into
devfrom
ShameenShahid-patch-2

Conversation

@ShameenShahid

Copy link
Copy Markdown
Collaborator

Updated command to check USN. Previous command was obselete and doesn't work.

Updated command to check USN. Previous command was obselete and doesn't work.
@github-actions

Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/privilegesecurediscovery/2.22/administration/systemmanagement/403zerousns.md

  • Structure — Lines 45–48: The new fenced code block breaks out of the list item. The bullet at line 43 is a list entry (its continuation line "domain zerored…" is indented two spaces), but the added blank line and the opening ``` start at column 0, which ends the list item and renders the command as a separate top-level block instead of as part of the note. Suggested fix: indent the fence and the command to align under the list item (two spaces), and remove the stray blank line at line 45 so the code stays attached to its bullet:
    - Command to check USNs by NetBIOS. Script runs this before and after zeroing for the
      domain. Including here for manual runs:
    
    
    sudo docker exec -it $(sudo docker ps | grep mongo | cut -d' ' -f1) mongo SecureONE --eval 'DBQuery.shellBatchSize = 999999999; db.secureone_config.find({type: "ldap_config"}).pretty()' | grep "fqdn|highest|previous"
  • Clarity — Line 46: The opening code fence has a trailing space (```) and the command on line 47 is indented two spaces inside the block. The leading whitespace renders as part of the command, which is misleading for a reader copying it to run manually. Suggested fix: use a bare ``` opening fence with no trailing space, and start the command at column 0 within the block.
  • Completeness — Line 43: The note says "Command to check USNs by NetBIOS" but doesn't state where the reader runs it. The command invokes sudo docker/mongo, so it must be run from the Privilege Secure appliance shell — context a newer user needs. Suggested fix: name the location, for example "Run this from the Privilege Secure appliance shell to check USNs by NetBIOS."

Summary

3 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

7 issues fixed, 2 skipped across 1 files

Category Fixes
CanBeUsedTo (rewrite) 1
FormalHedging (rewrite) 1
Idioms (rewrite) 1
Dale: passive-voice 4
Skipped (needs manual review) Reason

| docs/privilegesecurediscovery/2.22/administration/systemmanagement/403zerousns.md:14 — Dale: undefined-acronyms | USN is an Active Directory replication term in the same family as known AD acronyms (SID, GPO, OU) that a sysadmin audience recognizes; also appears in the title. Not confident it requires definition. |
| docs/privilegesecurediscovery/2.22/administration/systemmanagement/403zerousns.md:31 — Dale: wordiness | Bullet 'User selects the number for the domain will zero...' is grammatically broken, but rewriting risks changing meaning in a terse script-flow list; ambiguous intent. |

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

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