microsoft-365-docs
microsoft-365-docs copied to clipboard
MicrosoftDocs
Poor Grammar
Early on this page, we read that "When these intermediary services, perform such actions, they can use ARC can be used to provide details of the original authentication before the modifications occurred, which your organization can then trust to help with authenticating the message." Beyond being a very long sentence, it is grammatically ambiguous. The phrase "they can use ARC can be used to provide details" specifically is bad. They can use ARC, or ARC can be used? Is there a difference between the two somehow?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 36f9293f-c337-7af6-e994-336531d62f35
- Version Independent ID: 36f9293f-c337-7af6-e994-336531d62f35
- Content: Use Trusted ARC senders for legitimate devices and services between the sender and receiver - Office 365
- Content Source: microsoft-365/security/office-365-security/use-arc-exceptions-to-mark-trusted-arc-senders.md
- Product: m365-security
- Technology: mdo
- GitHub Login: @MSFTTracyP
- Microsoft Alias: tracyp
@WillMartin58 Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/9383
Once the author approves, the changes will be live.
Thanks Sri
@msbemba Thank you very much for the contribution and updating the documentation with PR. @WillMartin58 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.
Thanks, this is much more understandable now.
From: Yogesh Kumar @.> Sent: Wednesday, August 24, 2022 2:21 AM To: MicrosoftDocs/microsoft-365-docs @.> Cc: Will Martin @.>; Mention @.> Subject: Re: [MicrosoftDocs/microsoft-365-docs] Poor Grammar (Issue #9356)
@msbembahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmsbemba&data=05%7C01%7Cwillmart%40microsoft.com%7Cc23946b96cfc4fe8ee2608da8598d24e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637969188658257039%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tTM4rMb48riAjXG4YiUB7wWwzDUJiVqjH7jFQukHYj8%3D&reserved=0 Thank you very much for the contribution and updating the documentation with PR. @WillMartin58https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWillMartin58&data=05%7C01%7Cwillmart%40microsoft.com%7Cc23946b96cfc4fe8ee2608da8598d24e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637969188658257039%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uXBcD3dLVgfzMv5CeV%2FCNxJKC1Iyb3Be7FTB4x5d1KY%3D&reserved=0 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F9356%23issuecomment-1225251022&data=05%7C01%7Cwillmart%40microsoft.com%7Cc23946b96cfc4fe8ee2608da8598d24e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637969188658257039%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VTNP8rLGpm2kcuPwYO6TQuObWTy5ACFSZHjSZQgX%2B6g%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKO2QUHZNMF3JLPXTA7SYGDV2W5M7ANCNFSM5543DOXA&data=05%7C01%7Cwillmart%40microsoft.com%7Cc23946b96cfc4fe8ee2608da8598d24e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637969188658257039%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Qqo0Jsjbzpujbb%2FbG9bGYyf7jLLVdkwPh2PUK7XwSIU%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>