openspecs/oxocal: replace wrong example for PidTagSentRepresentingName value population strategy

[jengelh]

Pursuant to #3835 , I ask that MS-OXOCAL be updated. (cc @lindalu-MSFT )

In the section https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-oxocal/2bc03497-6c3b-48af-92ad-61a6a90d74fe , replace this:

The value of the PidTagSentRepresentingName property ([MS-OXOMSG] section 2.2.1.57) to the value of the PidTagMailboxOwnerName property ([MS-OXCSTOR] section 2.2.2.1) from the user's mailbox (for example, a delegate acting on behalf of the delegator would write the name of the delegate).

by this (emphasis added for issue description only):

The value of the PidTagSentRepresentingName property ([MS-OXOMSG] section 2.2.1.57) to the value of the PidTagMailboxOwnerName property ([MS-OXCSTOR] section 2.2.2.1) from the user's mailbox (for example, a delegate acting on behalf of the delegator would write the name of the delegator).

To show that the replacement is correct, one can, in the thought process, replace the latin names by practical job descriptions, and add a second subclause for context:

... for example, a secretary acting on behalf of the boss would write the name of the boss into the SentRepresenting field(s); …whereas the secretary's identity is placed in the Sender field(s).

[lindalu-MSFT]

@jengelh HI, I opened this PR https://github.com/MicrosoftDocs/open_specs_exchange/pull/114/files but don't have permission to merge it. I tried requesting permission via just-in-time (JIT) but don't have perms to do that, either. Try going to https://repos.opensource.microsoft.com/orgs/MicrosoftDocs/jit and requesting elevated perms, and you can merge the PR. If not, I'm not sure who to contact to merge this.

[CindySomer]

@jengelh I apologize for not seeing this sooner. The repos under the Open Specification site are different than most of the content on the learn.microsoft.com site and are not editable directly. I have made the update you requested. We will publish the changes soon. Thank you for your feedback.