docs/docs/working-with-entity-manager/5-entity-manager-api.md (1)

199-200: Tighten the note & spell out the implicit behaviour

A quick wording/clarity win: explicitly name what “current values” means, so the reader doesn’t have to infer which values are written.

-**Note:** When an upsert operation results in an update (due to a conflict), special columns like `@UpdateDateColumn` and `@VersionColumn` are automatically updated to their current values.
+**Note:** When an upsert operation performs an update (due to a conflict), TypeORM automatically  
+· sets `@UpdateDateColumn` to the current timestamp, and  
+· increments `@VersionColumn`. 

docs/docs/help/3-decorator-reference.md (2)

283-284: Mirror wording used elsewhere for consistency

Minor stylistic tweak so the phrasing matches the other docs you touched (“performs an update” instead of “when an update occurs”) and keeps the “due to a conflict” qualifier that explains why an update happens.

-**Note:** This column is also automatically updated during `upsert` operations when an update occurs due to a conflict.
+**Note:** This column is also automatically updated during `upsert` operations that perform an update due to a conflict.

---

315-316: Apply the same phrasing to the VersionColumn section

Keeping the two notes identical helps downstream translators & avoids docs drift.

-**Note:** This column is also automatically updated during `upsert` operations when an update occurs due to a conflict.
+**Note:** This column is also automatically updated during `upsert` operations that perform an update due to a conflict.

docs/docs/entity/1-entities.md (2)

174-176: Small grammar & flow polish

Replace the comma splice with an em-dash and reuse the “performs an update” wording.

-each time you call `save` of entity manager or repository, or during `upsert` operations when an update occurs.
+— each time you call `save` on the entity manager or repository, **or** during `upsert` operations that perform an update.

---

179-181: Keep wording identical to UpdateDateColumn paragraph

Same reasoning as above; suggest mirroring exact wording.

-each time you call `save` of entity manager or repository, or during `upsert` operations when an update occurs.
+— each time you call `save` on the entity manager or repository, **or** during `upsert` operations that perform an update.

docs/docs/working-with-entity-manager/6-repository-api.md (2)

155-156: Spell out what “current values” means

Same micro-clarification as in the EntityManager docs.

-**Note:** When an upsert operation results in an update (due to a conflict), special columns like `@UpdateDateColumn` and `@VersionColumn` are automatically updated to their current values.
+**Note:** When an upsert operation performs an update (due to a conflict), TypeORM automatically sets `@UpdateDateColumn` to the current timestamp and increments `@VersionColumn`.

---

170-173: Nit: keep example SQL fully valid

In Postgres CURRENT_TIMESTAMP usually lives outside quotes; since this is a doc comment it’s fine, but adding a comma after the last SET line makes the example invalid SQL. Consider dropping the trailing comma so copy-paste works.

- *  SET firstName = EXCLUDED.firstName,
- *      updatedDate = CURRENT_TIMESTAMP,
- *      version = version + 1
+ *  SET firstName = EXCLUDED.firstName,
+ *      updatedDate = CURRENT_TIMESTAMP,
+ *      version = version + 1

(Only the final line should lack the trailing comma.)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro