Clarifying Health Check Status metric behavior

[ffarinha-msft]

The aim of this PR is to help clarify the behavior of the Health Check Status metric to avoid confusion on what the metric represent by giving a particle example.

This is reference to the ICM 587874519

[prmerger-automator]

@ffarinha-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 002a7f1:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/app-service/monitor-instances-health-check.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Jak-MS]

@msangapu-msft
Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[learn-build-service-prod]

Learn Build status updates of commit 9d2278b:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/app-service/monitor-instances-health-check.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[jeffwmartinez]

Looks good on my end. Thanks for the clarification, Filipe.

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @msangapu-msft

[msangapu-msft]

#sign-off