[Excel, Word] (Bindings) Refresh the Bindings Common API Article #5306
Conversation
This file contains hidden or 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
|
Learn Build status updates of commit 0a16d89: ✅ Validation status: passed
For more details, please refer to the build report. |
lindalu-MSFT
requested changes
Jul 30, 2025
|
@AlexJerabek Over to you to accept my edits! Let me know if you have questions. |
Co-authored-by: Linda Cannon <[email protected]>
|
Learn Build status updates of commit 3364482: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Thanks @lindalu-MSFT! I've addressed your feedback and accepted your suggestions. |
|
Learn Build status updates of commit 36a6a9f: ✅ Validation status: passed
For more details, please refer to the build report. |
lindalu-MSFT
approved these changes
Jul 30, 2025
|
Approved and ready to merge. |
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.
This PR seeks to address the engagement issues with the Common API Bindings article. It makes the scenarios clearer and adds the note about Common API versus Application-specific API usage. It also tries to clean up the style across the article.