Update tmr-meeting-recording-change.md #10855
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I think that this copy is confusing. I edited some language to make it more concise, but I think the first paragraph in the 'Meetings and events' section could benefit from further simplification. I am editing this documentation because I leverage it for self-help solutions, which are provided to admins during the support ticket creation flow. Simple language is important to help admins understand their options, and therefore, empower them to administer Teams by themselves. This helps deflect support volume, which is a cost to Microsoft.
|
Learn Build status updates of commit dfaf102: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
hi @lesahill thank you for these suggestions. i've added them to another active PR that'll be published today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think that this copy is confusing. I edited some language to make it more concise, but I think the first paragraph in the 'Meetings and events' section could benefit from further simplification.
I am editing this documentation because I leverage it for self-help solutions, which are provided to admins during the support ticket creation flow. Simple language is important to help admins understand their options, and therefore, empower them to administer Teams by themselves. This helps deflect support volume, which is a cost to Microsoft.