The Entity Framework is pretty big, so when the Entity Framework team talks about things internally we tend to use jargon to increase communication 'bandwidth'.
Unfortunately sometimes we let this Jargon slip into our APIs and communication.
Now jargon is fine if you are in on the secret, but if not, its just straight out confusing.
So lets outline some of the more common pieces of Entity Framework Jargon and what they mean:
One of the things I've learned since joining Microsoft, is that if you have lots of people talking to customers, you have to be very explicit about the terms you introduce. If you don't ill-thought and confusing internal jargon has a habit of gaining a foot hold with customers, and misunderstanding will often ensue!
That said let me know if you can think of anymore Jargon and I'll add it to this list.