Update sql-server-2022-database-engine-events-and-errors-14000-14999.md

[VladDBA]

Hi SQL Server Docs Team,

I've fixed the incomplete Description for message_id 14852 so that it matches the text in sys.messages in SQL Server 2022-2016.

Thank you,

Vlad

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 8a4d7e0:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-14000-14999.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

[learn-build-service-prod]

Learn Build status updates of commit b777856:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/relational-databases/errors-events/includes/sql-server-2016-database-engine-events-and-errors-14000-14999.md	✅Succeeded
docs/relational-databases/errors-events/includes/sql-server-2017-database-engine-events-and-errors-14000-14999.md	✅Succeeded
docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-14000-14999.md	✅Succeeded
docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-14000-14999.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

[Jak-MS]

@MashaMSFT

• Can you review this PR?
• IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[rwestMSFT]

@VladDBA Thank you! This change will not be approved, because the articles are published directly from the source code.

However, you have revealed a bug in the generator, so when we do a regular publish from the source again, it will include this change.