diff --git a/docs/manual/intro.sgml b/docs/manual/intro.sgml
index 2e4f54bebe..208c25ee91 100644
--- a/docs/manual/intro.sgml
+++ b/docs/manual/intro.sgml
@@ -34,6 +34,12 @@
libraries can be made with a minimum of effort.
+
+ The GStreamer core function is to provide a framework for plugins, data flow
+ and media type handling/negotiation.
+ It also provides an API to write applications using the various plugins.
+
+
This book is about GStreamer from a developer's point of view; it describes
how to write a GStreamer application using the GStreamer libraries and tools.
diff --git a/docs/manual/motivation.sgml b/docs/manual/motivation.sgml
index cde5210b3d..1047f09be0 100644
--- a/docs/manual/motivation.sgml
+++ b/docs/manual/motivation.sgml
@@ -29,7 +29,7 @@
- 'One goal' media players
+ 'One goal' media players/libraries
Your typical MPEG player was designed to play MPEG video and audio. Most of
these players have implemented a complete infrastructure focused on
@@ -42,6 +42,13 @@
of the player and duplicate them into my own AVI encoder. These
algorithms cannot easily be shared accross applications.
+
+ Attempts have been made to create libraries for handling various media types.
+ Because they focus on a very specific media type (avifile, libmpeg2, ...),
+ significant work is needed to integrate them due to a lack of a common API.
+ GStreamer allows you to wrap these libraries with a common API, which
+ significantly simplifies integration and reuse.
+
@@ -58,7 +65,9 @@
While GStreamer also uses it own plugin system it offers a very rich
- framework for the plugin.
+ framework for the plugin developper and ensures the plugin can be used
+ in a wide range of applications, transparently interacting with other
+ plugins.