Subject: [Boost-commit] svn:boost r52660 - trunk/libs/spirit/doc
From: hartmut.kaiser_at_[hidden]
Date: 2009-04-29 11:21:25
Author: hkaiser
Date: 2009-04-29 11:21:24 EDT (Wed, 29 Apr 2009)
New Revision: 52660
URL: http://svn.boost.org/trac/boost/changeset/52660
Log:
Minor documentation fix (ticket #2974)
Text files modified:
trunk/libs/spirit/doc/introduction.qbk | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
Modified: trunk/libs/spirit/doc/introduction.qbk
==============================================================================
--- trunk/libs/spirit/doc/introduction.qbk (original)
+++ trunk/libs/spirit/doc/introduction.qbk 2009-04-29 11:21:24 EDT (Wed, 29 Apr 2009)
@@ -58,7 +58,7 @@
The separate sublibraries __qi__, __karma__ and __lex__ are well integrated
with any of the other parts. Because of their similar structure and identical
-underlying technology these are usable either separately or together at the
+underlying technology they are usable either separately or together at the
same time. For instance is it possible to directly feed the hierarchical data
structures generated by __qi__ into output generators created using __karma__;
or to use the token sequence generated by __lex__ as the input for a parser
@@ -178,7 +178,7 @@
]
The syntax is similar to /Qi/ with the exception that we use the `<<`
-operator for output concatenation. This should be easy to understand as it
+operator for output concatenation. This should be easy to remember as it
follows the conventions used in the Standard's I/O streams.
Another important feature of /karma/ allows you to fully decouple the data
@@ -186,7 +186,7 @@
data types as long as these conform conceptually. The next table gives some
related examples.
-[table Different data types usable with the output format `(*int_ << eol)`
+[table Different data types usable with the output format `*(int_ << eol)`
[ [Data type] ]
[ [`int i[4]`] [C style arrays] ]
[ [`std::vector<int>`] [Standard vector] ]