Documentation for delete behaviour in EF Core 3.1

[stevendarby]

Can I ask for clarity over delete behaviour in EF Core 3.1 please.

This documentation for Restrict states None for effect on dependent entities in memory.

But the enum documentation for Restrict says "For entities being tracked by the DbContext, the values of foreign key properties independent entities are set to null when the related principal is deleted."

Can I correctly assume that the first documentation is correct and the enum one wrong?

As a side note, NoAction also has the same enum comment as Restrict, but doesn't feature in the first documentation. I'm making an assumption that they have the same behaviour client side and both exist just to match different database options among different providers. But it'd be nice not to have to make assumptions about any of this.

Originally posted by @Snappyfoo in #21252 (comment)

[ajcvickers]

Answered in #21252. Cascade delete docs tracked by dotnet/EntityFramework.Docs#473