Skip to content

Conversation

@HeranGa0
Copy link
Contributor

@HeranGa0 HeranGa0 commented Dec 5, 2025

Summary

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

@github-actions
Copy link

github-actions bot commented Dec 5, 2025

Vale Linting Results

Summary: 2 warnings, 26 suggestions found

⚠️ Warnings (2)
File Line Rule Message
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 177 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 222 Elastic.DontUse Don't use 'Note that'.
💡 Suggestions (26)
File Line Rule Message
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 132 Elastic.FirstPerson Avoid first-person pronouns such as 'my'.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 149 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.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 163 Elastic.Wordiness Consider using 'sometimes' instead of 'In some cases'.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 163 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 177 Elastic.FutureTense 'will not' might be in future tense. Write in the present tense to describe the state of the product as it is now.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 177 Elastic.FutureTense 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 222 Elastic.FutureTense 'will not' might be in future tense. Write in the present tense to describe the state of the product as it is now.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 364 Elastic.FutureTense 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 384 Elastic.WordChoice Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 397 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 401 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 407 Elastic.Wordiness Consider using 'impossible' instead of 'not possible'.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 411 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 428 Elastic.Capitalization 'Resolution steps:' should use sentence-style capitalization.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 437 Elastic.WordChoice Consider using 'deactivate, deselect, hide, turn off' instead of 'Disable', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 448 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 456 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.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 471 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 476 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.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 476 Elastic.FirstPerson Avoid first-person pronouns such as ' I '.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 476 Elastic.FirstPerson Avoid first-person pronouns such as 'my'.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 497 Elastic.Acronyms 'IMAGE' has no definition.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 499 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 508 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.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 509 Elastic.FirstPerson Avoid first-person pronouns such as ' I '.
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md 509 Elastic.FirstPerson Avoid first-person pronouns such as 'my'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants