Docs.MS Release Updates for azure-communication-sms

[azure-sdk]

Update docs metadata and targeting for release of azure-communication-sms

[ghost]

Hello @azure-sdk!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[opbld33]

Docs Build status updates of commit 0767f49:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-ref-services/preview/communication-sms-readme.md	⚠️Warning		Details
ci-configs/packages-preview.json	✅Succeeded

docs-ref-services/preview/communication-sms-readme.md

• Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
• Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
• Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'communication'.
• Line 16, Column 1: [Warning-h1-not-first] Markdown content is not allowed before H1 'Azure Communication SMS Package client library for Python - Version 1.0.0b6'.
• Line 52, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#sending--zsms' in 'docs-ref-services/preview/communication-sms-readme.md'.
• Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[danieljurek]

Approving for auto merge