use "object-oriented" instead of "object oriented"

xabbuh · Christian Flothmann · commit c09ba41e28f9 · 2014-12-22T14:56:04.000+01:00
diff --git a/book/propel.rst b/book/propel.rst
@@ -271,8 +271,8 @@ from cheapest to most expensive. From inside a controller, do the following::
         ->orderByPrice()
         ->find();
 
-In one line, you get your products in a powerful oriented object way. No need
-to waste your time with SQL or whatever, Symfony offers fully object oriented
+In one line, you get your products in a powerful object-oriented way. No need
+to waste your time with SQL or whatever, Symfony offers fully object-oriented
 programming and Propel respects the same philosophy by providing an awesome
 abstraction layer.
 
diff --git a/components/event_dispatcher/introduction.rst b/components/event_dispatcher/introduction.rst
@@ -12,7 +12,7 @@ The EventDispatcher Component
 Introduction
 ------------
 
-Object Oriented code has gone a long way to ensuring code extensibility. By
+Object-oriented code has gone a long way to ensuring code extensibility. By
 creating classes that have well defined responsibilities, your code becomes
 more flexible and a developer can extend them with subclasses to modify their
 behaviors. But if they want to share the changes with other developers who have
