diff --git a/docs/en/release-info/migration-guides/abp-10-0.md b/docs/en/release-info/migration-guides/abp-10-0.md
index 4da20190a3..65c1be1d82 100644
--- a/docs/en/release-info/migration-guides/abp-10-0.md
+++ b/docs/en/release-info/migration-guides/abp-10-0.md
@@ -53,7 +53,7 @@ See the [C# 14 overload resolution with span parameters](https://learn.microsoft
 
 ### Failure Retry Policy for InboxProcessor
 
-In this version, we added a failure retry policy(`AbpEventBusBoxesOptions/InboxProcessorRetryBackoffFactor`) to the `AbpEventBusBoxesOptions`.
+We added a failure retry policy to `AbpEventBusBoxesOptions` (see `InboxProcessorFailurePolicy` and `InboxProcessorRetryBackoffFactor`). Because this change adds and removes fields in the `IncomingEventRecord` entity, you must create a new database migration if you use Inbox/Outbox with Entity Framework Core.
 
 * `InboxProcessorFailurePolicy`: The policy to handle the failure of the inbox processor. Default value is `Retry`. Possible values are:
     * `Retry`: The current exception and subsequent events will continue to be processed in order in the next cycle.