[sonicwall] Update documentation

[jrmolin]

Proposed commit message

[sonicwall] Update documentation

• Generated new documentation with LLM tooling
• Updated output to comply with requirements

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: 21 warnings, 11 suggestions found

⚠️ Warnings (21)

File	Line	Rule	Message
packages/sonicwall_firewall/docs/README.md	280	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/sonicwall_firewall/docs/README.md	295	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/sonicwall_firewall/docs/README.md	343	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	351	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	358	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	366	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/sonicwall_firewall/docs/README.md	368	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	368	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/sonicwall_firewall/docs/README.md	371	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	371	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/sonicwall_firewall/docs/README.md	417	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	418	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/README.md	422	Elastic.DontUse	Don't use 'and/or'.
packages/sonicwall_firewall/docs/README.md	425	Elastic.DontUse	Don't use 'Note that'.
packages/sonicwall_firewall/docs/README.md	425	Elastic.DontUse	Don't use 'just'.
packages/sonicwall_firewall/docs/knowledge_base/service_info.md	110	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/knowledge_base/service_info.md	126	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/sonicwall_firewall/docs/knowledge_base/service_info.md	143	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/sonicwall_firewall/docs/knowledge_base/service_info.md	147	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/sonicwall_firewall/docs/knowledge_base/service_info.md	196	Elastic.DontUse	Don't use 'and/or'.
packages/sonicwall_firewall/docs/knowledge_base/service_info.md	198	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.

💡 Suggestions (11)

File	Line	Rule	Message
packages/sonicwall_firewall/docs/README.md	333	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	333	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	347	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	351	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	358	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	378	Elastic.Wordiness	Consider using 'all' instead of 'All of '.
packages/sonicwall_firewall/docs/README.md	407	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	407	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	422	Elastic.Wordiness	Consider using 'sometimes' instead of 'In some cases'.
packages/sonicwall_firewall/docs/README.md	422	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/sonicwall_firewall/docs/README.md	425	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.

[elasticmachine]

Pinging @elastic/integration-experience (Team:Integration-Experience)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: ed64de5

History

• 💚 Build #37851 succeeded ca8cefe