diff --git a/docs/manual.qbk b/docs/manual.qbk
index 6f5ef5602fc22c2c2fc34fb970265cf80f16d646..587c2b42596064f4a2f84173e8abdfc3a29fb8e3 100644
--- a/docs/manual.qbk
+++ b/docs/manual.qbk
@@ -1824,7 +1824,7 @@ This is an example of XPath error handling ([@samples/xpath_error.cpp]):
 
 Because of the differences in document object models, performance considerations and implementation complexity, pugixml does not provide a fully conformant XPath 1.0 implementation. This is the current list of incompatibilities:
 
-* Consecutive text nodes sharing the same parent are not merged, i.e. in `<node>text1 <![CDATA[data]]> text2</node>` node should have one text node children, but instead has three.
+* Consecutive text nodes sharing the same parent are not merged, i.e. in `<node>text1 <![CDATA[data]]> text2</node>` node should have one text node child, but instead has three.
 * Since the document type declaration is not used for parsing, `id()` function always returns an empty node set.
 * Namespace nodes are not supported (affects namespace:: axis).
 * Name tests are performed on QNames in XML document instead of expanded names; for `<foo xmlns:ns1='uri' xmlns:ns2='uri'><ns1:child/><ns2:child/></foo>`, query `foo/ns1:*` will return only the first child, not both of them. Compliant XPath implementations can return both nodes if the user provides appropriate namespace declarations.