[fortinet_fortiedr] Update documentation

[taylor-swanson]

Proposed commit message

• Update documentation
• Generate knowledge base file
• Fix typo in manifest

Assisted by Google Gemini and Claude Opus.

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

Related issues

• Closes elastic/integration-experience#446

[github-actions]

Vale Linting Results

Summary: 17 warnings, 14 suggestions found

⚠️ Warnings (17)

File	Line	Rule	Message
packages/fortinet_fortiedr/docs/README.md	232	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortiedr/docs/README.md	247	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortiedr/docs/README.md	269	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/README.md	289	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortiedr/docs/README.md	338	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/README.md	338	Elastic.DontUse	Don't use 'please'.
packages/fortinet_fortiedr/docs/README.md	339	Elastic.DontUse	Don't use 'Note that'.
packages/fortinet_fortiedr/docs/README.md	339	Elastic.DontUse	Don't use 'note that'.
packages/fortinet_fortiedr/docs/README.md	339	Elastic.DontUse	Don't use 'note that'.
packages/fortinet_fortiedr/docs/README.md	340	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/README.md	340	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/README.md	340	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/README.md	340	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/README.md	393	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/fortinet_fortiedr/docs/README.md	393	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/knowledge_base/service_info.md	82	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/fortinet_fortiedr/docs/knowledge_base/service_info.md	157	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.

💡 Suggestions (14)

File	Line	Rule	Message
packages/fortinet_fortiedr/_dev/build/docs/README.md	3	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortiedr/_dev/build/docs/README.md	20	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	3	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	20	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	331	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	338	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	338	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	339	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	339	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	389	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/fortinet_fortiedr/docs/README.md	404	Elastic.Wordiness	Consider using 'all' instead of 'All of '.
packages/fortinet_fortiedr/docs/knowledge_base/service_info.md	95	Elastic.HeadingColons	Capitalize ': l'.
packages/fortinet_fortiedr/docs/knowledge_base/service_info.md	108	Elastic.HeadingColons	Capitalize ': t'.
packages/fortinet_fortiedr/docs/knowledge_base/service_info.md	124	Elastic.HeadingColons	Capitalize ': u'.

---

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]

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

[mjwolf]

Thanks for working on this. It looks good to me, there are just some small changes needed. There's also some suggested linter changes (you don't need to make changes on the ECS fields or other generated text)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 70f2254

History

• 💚 Build #38114 succeeded 7dfba35
• 💚 Build #38105 succeeded 4c53193

cc @taylor-swanson