I figured out a better way to phrase this and patched the document!
The current version, 5.15.22, should resolve the issue.
Wonderful! Thank you!
No problem!
