diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md b/docs/05-administrator-guide/02-configuration/99-appendix.md
index 2ff2ed344f..1e2a1575cf 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -527,7 +527,7 @@ This page provides a comprehensive overview of the configuration keys available
 | `ozone.om.open.key.expire.threshold` | 7d | `OZONE`, `OM`, `PERFORMANCE` | Controls how long an open key operation is considered active. Specifically, if a key has been open longer than the value of this config entry, that open key is considered as expired (e.g. due to client crash). Unit could be defined with postfix (ns,ms,s,m,h,d) |
 | `ozone.om.open.mpu.cleanup.service.interval` | 24h | `OZONE`, `OM`, `PERFORMANCE` | A background job that periodically checks inactive multipart info send multipart upload abort requests for them. This entry controls the interval of this cleanup check. Unit could be defined with postfix (ns,ms,s,m,h,d) |
 | `ozone.om.open.mpu.cleanup.service.timeout` | 300s | `OZONE`, `OM`, `PERFORMANCE` | A timeout value of multipart upload cleanup service. If this is set greater than 0, the service will stop waiting for the multipart info abort completion after this time. If timeout happens to a large proportion of multipart aborts, this value needs to be increased or `ozone.om.open.key.cleanup.limit.per.task` should be decreased. Unit could be defined with postfix (ns,ms,s,m,h,d) |
-| `ozone.om.open.mpu.expire.threshold` | 30d | `OZONE`, `OM`, `PERFORMANCE` | Controls how long multipart upload is considered active. Specifically, if a multipart info has been ongoing longer than the value of this config entry, that multipart info is considered as expired (e.g. due to client crash). Unit could be defined with postfix (ns,ms,s,m,h,d) |
+| `ozone.om.open.mpu.expire.threshold` | 30d | `OZONE`, `OM`, `PERFORMANCE` | Controls how long a multipart upload is considered active before MultipartUploadCleanupService treats it as stale and aborts it. If a multipart upload has been ongoing longer than this threshold (e.g. due to a client crash), it will be cleaned up automatically. Unit can be specified with a postfix (ns, ms, s, m, h, d). Interaction with S3 lifecycle AbortIncompleteMultipartUpload rules: When a bucket lifecycle rule specifies an AbortIncompleteMultipartUpload action, its daysAfterInitiation value must be strictly less than this threshold. If daysAfterInitiation is greater than or equal to this threshold, MultipartUploadCleanupService will abort the upload before the lifecycle rule fires, silently making the rule ineffective. Ozone enforces this constraint at lifecycle configuration creation time and will reject configurations that violate it. To use a longer daysAfterInitiation value, increase this threshold accordingly. |
 | `ozone.om.open.mpu.parts.cleanup.limit.per.task` | 1000 | `OZONE`, `OM`, `PERFORMANCE` | The maximum number of parts, rounded up to the nearest number of expired multipart upload. This property is used to approximately throttle the number of MPU parts sent to the OM. |
 | `ozone.om.ratis.events.max.limit` | 100 | `OZONE`, `RATIS`, `OM` | The maximum number of events that can be pending in OM Ratis. |
 | `ozone.om.ratis.log.appender.queue.byte-limit` | 32MB | `OZONE`, `DEBUG`, `OM`, `RATIS` | Byte limit for Raft's Log Worker queue. |