Skip to content

Commit 5fae513

Browse files
authored
Update Mover Settings path in diagnostics documentation (#306)
Clarify GUI location of mover logging Before Submitting This PR, Please Ensure You Have Completed The Following: 1. [x] Are internal links to wiki documents using [relative file links](https://docusaurus.io/docs/markdown-features/links)? 2. [x] Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)? 3. [x] Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files? 4. [x] Have you checked to ensure there aren't other open [Pull Requests](../../../pulls) for the same update/change? 5. [x] Is the build succeeding? <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Corrected UI navigation for Mover Settings to Settings > Scheduler > Mover Settings in the Diagnostics Information troubleshooting guide. * Improved accuracy of instructions for anonymizing diagnostic data to help users locate settings and follow steps reliably. * Ensures users can successfully verify and adjust Mover behavior when collecting diagnostics without searching through outdated menu paths. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
1 parent 53492cc commit 5fae513

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/unraid-os/troubleshooting/diagnostics-information.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The diagnostics are a single zip file containing multiple files. If it seems to
3434

3535
### Anonymization of diagnostic data
3636

37-
While diagnostic data is anonymized, if you enable mover logging under ***Settings > Mover Settings***, the syslog will give details of files that mover is operating on.
37+
While diagnostic data is anonymized, if you enable mover logging under ***Settings > Scheduler > Mover Settings***, the syslog will give details of files that mover is operating on.
3838

3939
In this particular scenario, you have intentionally enabled mover logging to investigate a problem where it is beneficial to gather as much detail as possible, in order to resolve an issue.
4040

0 commit comments

Comments
 (0)