Skip to content

Update databasecustompathwindows.md#1187

Open
brichmond31 wants to merge 5 commits into
devfrom
brichmond31-patch-1
Open

Update databasecustompathwindows.md#1187
brichmond31 wants to merge 5 commits into
devfrom
brichmond31-patch-1

Conversation

@brichmond31

Copy link
Copy Markdown
Collaborator

Reviewed document as I believe some of the steps could be confusing and some of the information is outdated or no longer relevant.

Added additional steps, service names, files names and paths.

Reviewed document as I believe some of the steps could be confusing and some of the information is outdated or no longer relevant.

Added additional steps, service names, files names and paths.
@brichmond31 brichmond31 requested a review from a team as a code owner July 1, 2026 16:04
@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

1 issues fixed, 0 skipped across 1 files

Category Fixes
Dale: positional-references 1

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

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 0 skipped across 1 files

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

Same as PR 1187.
@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/changetracker/8.0/install/databasecustompath/windows.md

  • Completeness — Line 20: The screenshot now points to a temporary GitHub upload URL (https://github.com/user-attachments/assets/...) instead of a versioned asset under static/images/. These attachment URLs are not permanent and are not guaranteed to render in the published docs, so readers may see a broken image. Suggested fix: save the screenshot as a .webp file under static/images/changetracker/8.0/install/deployment/ and reference it with an absolute path, e.g. ![Custom database path on Windows](/images/changetracker/8.0/install/deployment/customdatabasepathwindows.webp).
  • Completeness — Line 18: Step 4 tells the reader to edit the dbpath parameter to change the location for DB files, but no longer shows what a valid entry looks like (the removed text referenced "the config line as below"). A newer user won't know the expected format. Suggested fix: add an example of the edited line, e.g. Set dbpath to the new folder, for example: dbpath: "D:\ChangeTracker\Data".
  • Clarity — Line 16: Step 3 says to edit mongod.cfg but doesn't say how to open it. Suggested fix: name the action and note the permission needed, e.g. "Open the mongod.cfg file in a text editor with administrator privileges. The file is located in C:\Program Files\NNT Change Tracker Suite\Gen7\MongoDB\bin."

docs/changetracker/8.1/install/databasecustompathoverview/databasecustompathwindows.md

  • Completeness — Line 20: Same temporary GitHub upload URL issue as above. Suggested fix: save the screenshot as a .webp under static/images/changetracker/8.1/install/deployment/ and reference it with an absolute /images/... path.
  • Completeness — Line 18: Step 4 no longer shows an example of the dbpath value. Suggested fix: add a sample edited line, e.g. dbpath: "D:\ChangeTracker\Data".
  • Clarity — Line 16: Step 3 doesn't say how to open mongod.cfg. Suggested fix: "Open the mongod.cfg file in a text editor with administrator privileges. The file is located in C:\Program Files\NNT Change Tracker Suite\Gen7\MongoDB\bin."

docs/changetracker/8.2/install/databasecustompathoverview/databasecustompathwindows.md

  • Completeness — Line 20: Same temporary GitHub upload URL issue as above. Suggested fix: save the screenshot as a .webp under static/images/changetracker/8.2/install/deployment/ and reference it with an absolute /images/... path.
  • Completeness — Line 18: Step 4 no longer shows an example of the dbpath value. Suggested fix: add a sample edited line, e.g. dbpath: "D:\ChangeTracker\Data".
  • Clarity — Line 16: Step 3 doesn't say how to open mongod.cfg. Suggested fix: "Open the mongod.cfg file in a text editor with administrator privileges. The file is located in C:\Program Files\NNT Change Tracker Suite\Gen7\MongoDB\bin."

Summary

9 editorial suggestions across 3 files. The three files are identical, so each carries the same three suggestions. The most important item is the screenshot reference: all three now point to a temporary GitHub attachment URL rather than a versioned static/images/ asset, which risks a broken image in production. 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

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 3 skipped across 3 files

Skipped (needs manual review) Reason

| docs/changetracker/8.0/install/databasecustompath/windows.md:16 — Dale: passive-voice | 'the mongod.cfg file located in' reads as passive, but 'located' functions as an idiomatic adjectival phrase here; rewording risks altering meaning/formatting for low benefit |
| docs/changetracker/8.1/install/databasecustompathoverview/databasecustompathwindows.md:16 — Dale: passive-voice | same as 8.0 — 'located in' is idiomatic; skipped to preserve meaning |
| docs/changetracker/8.2/install/databasecustompathoverview/databasecustompathwindows.md:16 — Dale: passive-voice | same as 8.0 — 'located in' is idiomatic; skipped to preserve meaning |

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.

3 participants