X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=doc%2Fapi%2Fdox%2Fincludes-build.dox;h=f7b42c1a45145d5f8ad81e8977d948623144101c;hb=1cda4ff4025e4b3f7bd2a861baa51d2113c4cbf9;hp=78c880fc273519f955e61a68fe3adb9a43acc50a;hpb=3fadfbc0c91f82c46bd36e6e0657ea93570c9db1;p=babeltrace.git
diff --git a/doc/api/dox/includes-build.dox b/doc/api/dox/includes-build.dox
index 78c880fc..f7b42c1a 100644
--- a/doc/api/dox/includes-build.dox
+++ b/doc/api/dox/includes-build.dox
@@ -4,7 +4,7 @@
@section includefiles Include files
You can find all the Babeltrace library include files (C headers) in the
-\c babeltrace directory under the include files directory chosen when
+\c babeltrace2 directory under the include files directory chosen when
installing Babeltrace. By default, this is /usr/include
.
If you build Babeltrace from source without specifying an installation
prefix, this is /usr/local/include
.
@@ -23,14 +23,14 @@ but which necessarily makes the compilation slower:
Multiple types of applications can use the Babeltrace library:
-- A user plugin (shared object) to be loaded by the \c babeltrace
+- A user plugin (shared object) to be loaded by the \c babeltrace2
converter program or by another application.
- A user application or library which loads plugins to manually connect
existing components in a specific way.
- A user application or library which creates its own component classes
and manually connects them.
-In any way, the only library to link to is `libbabeltrace`.
+In any way, the only library to link to is `libbabeltrace2`.
@subsection howtobuildplugin Build a plugin
@@ -47,7 +47,7 @@ cc -c -fpic my-plugin.c