Clarification on updateMany

I need to use updateMany to put a new field (a date) into every document within a collection. This collection has a couple TB’s and I don’t want to block transactions from processing. Is this something that I need to even worry about? When I read the documentation, I didn’t 100% understand it:
When a single write operation (e.g. db.collection.updateMany) modifies multiple documents, the modification of each document is atomic, but the operation as a whole is not atomic. …so the way that I interpret this is that a document is modified (and committed?) then updateMany moves on and doesn’t block transactions.

With some quibbles about terminology, I believe your interpretation is correct.

Thanks Mr. Woehr, I appreciate it. I’ll give this a shot here in a few hours.