aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristian Kandeler <christian.kandeler@digia.com>2013-12-04 15:23:01 +0100
committerChristian Kandeler <christian.kandeler@digia.com>2013-12-04 16:52:32 +0100
commit34278f3d3a50183f8e9655735e9e06b5b1e49176 (patch)
tree527f5686798ca767444dd18098e6ec9e4135adc1
parentaa31e2dced97062552934271d186a43c3fd8e457 (diff)
Fix Export item documentation.
There were some references to "product module" left. Change-Id: I0217e375aa387298e0c32811608a33ffc7ee9a75 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
-rw-r--r--doc/reference/items/export.qdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/reference/items/export.qdoc b/doc/reference/items/export.qdoc
index 2c714c129..d37514dfa 100644
--- a/doc/reference/items/export.qdoc
+++ b/doc/reference/items/export.qdoc
@@ -37,7 +37,7 @@
\brief Exports dependencies and properties to other products.
An \c Export item can appear inside a \l{Product Item}. The properties attached to it will
- take effect in all products that depend on the product inside which the product module is defined.
+ take effect in all products that depend on the product inside which the Export item is defined.
As an example, consider these two products:
\code
Product {
@@ -56,8 +56,8 @@
The sources in product B will be able to use headers from product A without specifiying
the full path to them, because the include path has been made known to the compiler via
- A's product module.
+ A's Export item.
\note This relationship is transitive, so a product C depending on product B will also
- get the include paths via A's product module.
+ get the include paths via A's Export item.
*/