Jira issue originally created by user ralfas:
The benefit of Doctrine for the programmer is the possibility -can- to focus -soley- solely on the business and worry about persistence only as a secondary task. This doesn't mean persistence is not important to Doctrine 2, however it is our belief that there are considerable benefits for object-oriented programming, if persistence and entities are kept perfectly -seperated- separated.
Entities are -leightweight- lightweight PHP Objects that don't need to extend any abstract base class or interface. An entity class must not be final or contain final methods. Additionally it must not implement _clone nor _wakeup or it should do so safely.
What would be the best way to note other errors?
Comment created by @beberlei:
The best way for us would be if you fork the docs on github, change the stuff and commit it. Then issue a pull request. It sounds complicated, but should be minimal overhead of ~5 minutesn on your end, but then we can merge it with a mouse-click, so we dont need to duplicate the whole correction effort on our end.
Comment created by jclermont:
I have fixed the typos from this ticket that were still present in the docs and issued a pull request on Github.
Comment created by mridgway:
This issue should be closed: doctrine/orm-documentation#17
Comment created by @guilhermeblanco:
Issue got fixed somehow in the past
Issue was closed with resolution "Fixed"