Fix typos

[omahs]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[github-actions]

Thank you for your contribution @omahs! We will review the pull request and get back to you soon.

[azure-sdk]

API change check

API changes are not detected in this pull request.

[FabianMeiswinkel]

LGTM from /sdk/cosmos perspective. Thanks!

[joshfree]

@danieljurek @jairmyree - please double check why cspell didn't catch these.

@JimSuplizio please give this a quick 2nd review since it's updating some of your parts of contributing.md

[jairmyree]

[like] Jair Myree reacted to your message:

________________________________ From: Josh Free ***@***.***> Sent: Friday, May 9, 2025 4:08:01 AM To: Azure/azure-sdk-for-java ***@***.***> Cc: Jair Myree ***@***.***>; Mention ***@***.***> Subject: Re: [Azure/azure-sdk-for-java] Fix typos (PR #45238) @joshfree approved this pull request. @danieljurek<https://github.com/danieljurek> @jairmyree<https://github.com/jairmyree> - please double check why cspell didn't catch these. @JimSuplizio<https://github.com/JimSuplizio> please give this a quick 2nd review since it's updating some of your parts of contributing.md

________________________________ In sdk/communication/azure-communication-callautomation/README.md<#45238 (comment)>:

@@ -98,7 +98,7 @@ If timeout was not set when calling "waitForEventProcessorAsync", the default ti

## Troubleshooting

-If you recieve a CommunicationErrorException with the messagae: "Action is invalid when call is not in Established state." This usually means the call has ended. This can occur if the participants all leave +If you receive a CommunicationErrorException with the messagae: "Action is invalid when call is not in Established state." This usually means the call has ended. This can occur if the participants all leave Message is still spelled wrong in the same line. @danieljurek<https://github.com/danieljurek> @jairmyree<https://github.com/jairmyree> - is cspell not working properly at the moment?

________________________________ In sdk/communication/azure-communication-callingserver/README.md<#45238 (comment)>:

@@ -45,7 +45,7 @@ To be determined.

## Troubleshooting

…

-If you recieve a CommunicationErrorException with the messagae: "Action is invalid when call is not in Established state." This usually means the call has ended. This can occur if the participants all leave +If you receive a CommunicationErrorException with the messagae: "Action is invalid when call is not in Established state." This usually means the call has ended. This can occur if the participants all leave Should be message — Reply to this email directly, view it on GitHub<#45238 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQC3WGF7F77GPAKEFJRULM325QS2DAVCNFSM6AAAAAB4TH5UN6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDQMRWHEZTOOJQGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>