Mistake in the mongoose's documentation for transactions?

[booziyaada]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the issue has not already been raised

Issue

In the mongoose documentation for transactions it says:
Mongoose's Connection#transaction() function is a wrapper around withTransaction() that integrates Mongoose change tracking with transactions. For example, suppose you save() a document in a transaction that later fails. The changes in that document are not persisted to MongoDB. The Connection#transaction() function informs Mongoose change tracking that the save() was rolled back, and marks all fields that were changed in the transaction as modified. [End quote]

If the transaction fails, Mongoose' change tracking marks all fields that were changed in the transaction as unmodified right?

[Sagar-Kumar01]

The wording in the documentation seems misleading.

When a transaction is aborted, MongoDB rolls back the write and Mongoose clears its internal change tracking for the document. Paths modified inside the failed transaction are marked as unmodified, so the document state reflects what is actually persisted.

It would be clearer if the docs explicitly said that Mongoose resets modified paths after a failed transaction, rather than saying they are marked as modified.