vsprintf articles update

[nikita-leontiev]

1. cd68e32
   vswprintf and _vswprintf_l functions return characters count that would be written to buffer when buffer=NULL and count=0. If only count is zero, then memory corruption occurs. "Return value" section updated.
2. 15f1aa3
   If buffer=NULL and count=0, functions return characters count that would be written to buffer. If buffer is valid and count/sizeInBytes is zero, then memory corruption occurs. "Return value"/"Remarks" sections updated.
3. 5fa9b33
   Functions return characters count that would be written to buffer when buffer=NULL and count=0. If count is zero, functions return -1. "Behavior summary" section updated.
4. 38e139c
   If buffer is valid, sizeOfBuffer is not zero and count=0, functions return -1. "Behavior summary" section updated.

Functions behavior was checked on Windows 7 SP1 x64 with Microsoft Visual C++ 2008.

[learn-build-service-prod]

Learn Build status updates of commit 38e139c:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/c-runtime-library/reference/vsnprintf-s-vsnprintf-s-vsnprintf-s-l-vsnwprintf-s-vsnwprintf-s-l.md	✅Succeeded
docs/c-runtime-library/reference/vsnprintf-vsnprintf-vsnprintf-l-vsnwprintf-vsnwprintf-l.md	✅Succeeded
docs/c-runtime-library/reference/vsprintf-p-vsprintf-p-l-vswprintf-p-vswprintf-p-l.md	✅Succeeded
docs/c-runtime-library/reference/vsprintf-vsprintf-l-vswprintf-vswprintf-l-vswprintf-l.md	✅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

[nikita-leontiev]

@microsoft-github-policy-service agree

[prmerger-automator]

@nikita-leontiev : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[prmerger-automator]

@nikita-leontiev : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[Court72]

@TylerMSFT

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

[TylerMSFT]

Thank you for this. I have several things in my queue at the moment but have marked this to come back to as soon as I'm able.