azure-docs Update api-management-howto-create-or-invite-developers.md

we need to be very clear as to which specific persona we are talking about in each of the articles. "developers" is an overloaded term, especially in API eco-system. you have developers who produce APIs, and producers who consume other people's APIs, and then there are consumers who do not publish anything but are interested in consuming someone else's APIs. Finally, there is the APIM back-office or admins. In my commit, i have tried to articulate how a producer can manage its own consumers, since they are the best people to know who they are writing the APIs for. It could be part of their own org, or outside the org, or outside the company.

Dec 14 '24 20:12 jishnath

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

Dec 14 '24 20:12 prmerger-automator[bot]

Learn Build status updates of commit f35f882:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/api-management/api-management-howto-create-or-invite-developers.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

Dec 14 '24 20:12 learn-build-service-prod[bot]

@dlepow

Can you review the proposed changes?

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