[Imperva] update documentation

[haetamoudi]

Proposed commit message

[imperva] Documentation Update

generated new knowledge base file
generated new documentation

Please explain:

• WHAT: patterns used, algorithms implemented, design architecture, message processing, etc.
• WHY: the rationale/motivation for the changes

This text will be pasted into the squash dialog when the change is committed and will be
a long term historical record of the change to help future contributors understand the
change, please help them by making it clear and comprehensive, they may be you.

If the commit title is adequate to describe both of these things, The text here may be omitted
or replaced with "See title". The title of the PR will be used as the commit message title when
the merge is made and the "See title" marker will be removed if present.

The text here and the PR title will be subject to the PR review process.
-->

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

[elasticmachine]

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

[github-actions]

Vale Linting Results

Summary: 17 warnings, 6 suggestions found

⚠️ Warnings (17)

File	Line	Rule	Message
packages/imperva/_dev/build/docs/README.md	18	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/_dev/build/docs/README.md	65	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/README.md	18	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/README.md	65	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/README.md	207	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/README.md	220	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/README.md	242	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/imperva/docs/README.md	262	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	21	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	69	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	73	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	86	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	90	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	102	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	106	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/imperva/docs/knowledge_base/service_info.md	111	Elastic.EndPuntuaction	Don't end headings with punctuation.
packages/imperva/docs/knowledge_base/service_info.md	154	Elastic.EndPuntuaction	Don't end headings with punctuation.

💡 Suggestions (6)

File	Line	Rule	Message
packages/imperva/_dev/build/docs/README.md	20	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.
packages/imperva/_dev/build/docs/README.md	37	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/imperva/_dev/build/docs/README.md	55	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.
packages/imperva/docs/README.md	20	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.
packages/imperva/docs/README.md	37	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/imperva/docs/README.md	55	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.

---

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: cac5837

History

• 💔 Build #38075 failed b2fcb39
• 💚 Build #37986 succeeded cefde4c

[mjwolf]

This looks good to me, it just needs the list in the overview removed

[mjwolf]

This list can be deleted, it's duplicated by the supported use case section