diff --git a/docs/en/Customizing-Application-Modules-Extending-Entities.md b/docs/en/Customizing-Application-Modules-Extending-Entities.md
index c2bcd314d4..e1cb02e849 100644
--- a/docs/en/Customizing-Application-Modules-Extending-Entities.md
+++ b/docs/en/Customizing-Application-Modules-Extending-Entities.md
@@ -63,8 +63,6 @@ You can then use the same extra properties system defined in the previous sectio
 
 Another approach can be **creating your own entity** mapped to **the same database table** (or collection for a MongoDB database).
 
-`AppUser` entity in the [application startup template](Startup-Templates/Application.md) already implements this approach. [EF Core Migrations document](Entity-Framework-Core-Migrations.md) describes how to implement it and manage **EF Core database migrations** in such a case. It is also possible for MongoDB, while this time you won't deal with the database migration problems.
-
 ## Creating a New Entity with Its Own Database Table/Collection
 
 Mapping your entity to an **existing table** of a depended module has a few disadvantages;