Consider adding examples of why one would skip corrections in a parity check

[ScribbleGhost]

If you wish to run purely a check without writing correction, uncheck the checkbox that says Write corrections to parity before starting the check. In this mode, parity errors will be notated but not actually fixed during the check operation.

https://github.com/unraid/docs/blob/87d646a603e683142833e5c748e6e4aeff997a6a/docs/unraid-os/manual/storage-management.md?plain=1#L1067C30-L1069C39

Why would anyone want to do that? Are there any practical use cases? Would be interesting with some examples.

[aptalca]

If an array drive is not totally reliable, such as having had some minor or seemingly benign smart issues in the near past, I might trust the parity data more. In those cases, I do a parity check without correction (correction would trust the array drive data and overwrite the parity), and if there are a bunch of sync errors coming up, I'd probably replace the drive and rebuild from parity instead.