temporarily fixed image links.

manual/docs/en/introduction/the-big-picture.txt

 +++ Overview
 Doctrine is a tool for object-relational mapping in PHP. It sits on top of PDO and is itself divided into two main layers, The DBAL and the ORM. See the picture below.
 
-[http://localhost/graphics/doctrine-layers.jpg]
+[http://code-factory.org/doctrine-manual-images/doctrine-layers.jpg]
 
 The DBAL layer completes and extends the basic database abstraction/independance that is already provided by PDO. The DBAL library can be used standalone, if all you want is a powerful database abstraction layer on top of PDO. [Link to DBAL download here].
 The ORM layer depends on the DBAL and therefore, when you load the ORM package the DBAL is already included.

manual/docs/en/introduction/what-it-is-and-what-not.txt

@@ -9,7 +9,7 @@ However, it's currently not possible to ditch the ActiveRecord approach complete
 The ActiveRecord approach comes with it's typical limitations. The most obvious is the enforcement for a class to extend a specific base class in order to be persistent (an Entity). In general, the design of your domain model is pretty much restricted by the design of your relational model. There is an exception though. When dealing with inheritance structures, Doctrine provides some sophisticated mapping strategies which allow your domain model to diverge a bit from the relational model and therefore give you a bit more freedom. Doctrine is in a continous development process and we always try to add new features that provide more freedom in the modeling of the domain. However, as long as Doctrine remains mainly an ActiveRecord approach, there will always be a pretty large, (forced) similarity of these two models.
 The current situation is depicted in the following picture.
 
-[http://localhost/graphics/relational-bounds.jpg]
+[http://code-factory.org/doctrine-manual-images/relational-bounds.jpg]
 
 As you see in the picture, the domain model can't drift far away from the bounds of the relational model.