[qnap_nas] Update documentation

[jrmolin]

Proposed commit message

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

Vale Linting Results

Summary: 10 warnings, 10 suggestions found

⚠️ Warnings (10)

File	Line	Rule	Message
packages/qnap_nas/docs/README.md	205	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/qnap_nas/docs/README.md	227	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/qnap_nas/docs/README.md	247	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/qnap_nas/docs/README.md	283	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/qnap_nas/docs/README.md	283	Elastic.DontUse	Don't use 'please'.
packages/qnap_nas/docs/README.md	284	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/qnap_nas/docs/README.md	284	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/qnap_nas/docs/README.md	284	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/qnap_nas/docs/README.md	284	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/qnap_nas/docs/README.md	285	Elastic.DontUse	Don't use 'Note that'.

💡 Suggestions (10)

File	Line	Rule	Message
packages/qnap_nas/_dev/build/docs/README.md	39	Elastic.FirstPerson	Avoid first-person pronouns such as ' I '.
packages/qnap_nas/_dev/build/docs/README.md	59	Elastic.FirstPerson	Avoid first-person pronouns such as ' I '.
packages/qnap_nas/docs/README.md	39	Elastic.FirstPerson	Avoid first-person pronouns such as ' I '.
packages/qnap_nas/docs/README.md	59	Elastic.FirstPerson	Avoid first-person pronouns such as ' I '.
packages/qnap_nas/docs/README.md	276	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/qnap_nas/docs/README.md	283	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/qnap_nas/docs/README.md	283	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/qnap_nas/docs/README.md	309	Elastic.Wordiness	Consider using 'all' instead of 'All of '.
packages/qnap_nas/docs/README.md	315	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/qnap_nas/docs/README.md	315	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 7c9a4e7

History

• 💔 Build #37621 failed dfc5710