Fix docs for sourceString param in WindowsCreateString

[Sergio0694]

This doesn't actually require to be null-terminated, and it was quite confusing.

See https://devblogs.microsoft.com/oldnewthing/20160615-00/?p=93675:

"WindowsCreateString creates an HSTRING from a UTF-16LE-encoded buffer and a specified length. The buffer does not require a terminating null."

[prmerger-automator]

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

[Copilot]

Pull Request Overview

This PR fixes the documentation for the sourceString parameter in the WindowsCreateString function to clarify that the input buffer does not need to be null-terminated, addressing confusion in the original documentation.

• Corrects misleading documentation that implied the input string must be null-terminated
• Adds clarification about UTF-16LE encoding and the function's behavior regarding null termination
• References Microsoft documentation to support the correction

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}