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

Learn Build status updates of commit 5c0bfd8:

⚠️ Validation status: warnings

articles/communication-services/concepts/voice-video-calling/real-time-text.md

• Line 5, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: 'Adam Hammer' is not a valid GitHub ID.
• Line 6, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'Azure Communication Services'.
• Line 9, Column 10: [Warning: ms-date-invalid - See documentation] Invalid date format for 'ms.date': '2024-11-25'. If specified, must be a date in format M/D/YYYY, no more than 30 days from today. If you don't specify ms.date, the date will be updated automatically.
• Line 55, Column 22: [Warning: file-not-found - See documentation] Invalid file link: '../../quickstarts/RTTQuickstart.md'.
• Line 56, Column 44: [Warning: file-not-found - See documentation] Invalid file link: '../accessible-communications/RTTIntegration.md'.
• Line 10, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ahammer' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions 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 learn.microsoft.com contributor guides
• Post your question in the Learn support channel

@ahammer - if you want to proceed from draft to article, you'll need to work with someone on the content team... I've assigned @sloanster, but they might not be the correct person.

@sloanster
When @ahammer is ready, can you review the proposed article or help determine who is the best reviewer?

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

Thanks, I'm just putting drafts in place and will probably hand off to the Product team, they can help coordinate.

https://github.com/MicrosoftDocs/azure-docs-pr/pull/291376

Moved here, closing.