diff --git a/doc/lazy_list.qbk b/doc/lazy_list.qbk index 7b85f27..8593a79 100644 --- a/doc/lazy_list.qbk +++ b/doc/lazy_list.qbk @@ -41,7 +41,7 @@ Progress is being made in implementing both the basic list and the functions [section Background] -The original code of __fcpp__ was developed by Brian McNamara and Yannis Smaragdakis between 2000 and 2003. One of the aims of their work was to implement as mich as possible of the Haskell prelude in C++. In the end they achieved a very large part of that and went on to implement other similar things not in the Haskell prelude. This was made up of a large amount of code written very carefully in a consistent style which made it easy to extend it to provide more facilities. +The original code of __fcpp__ was developed by Brian McNamara and Yannis Smaragdakis between 2000 and 2003. One of the aims of their work was to implement as much as possible of the Haskell prelude in C++. In the end they achieved a very large part of that and went on to implement other similar things not in the Haskell prelude. This was made up of a large amount of code written very carefully in a consistent style which made it easy to extend it to provide more facilities. At the end of that time, two versions of it existed, FC++ 1.5 and __boost_fcpp__ which was proposed for inclusion in Boost and rejected. Both are documented on __fcpp__. diff --git a/doc/modules/core.qbk b/doc/modules/core.qbk index 38b5586..9b5cc20 100644 --- a/doc/modules/core.qbk +++ b/doc/modules/core.qbk @@ -35,7 +35,7 @@ behind the scenes. This is also equivalent to `add(arg1, val(6))`. val(v) -generates an `expression::value::type` where `T` is the type of `x`. In most +generates an `expression::value::type` where `T` is the type of `v`. In most cases, there's no need to explicitly use `val`, but, as we'll see later on, there are situations where this is unavoidable. diff --git a/doc/preface.qbk b/doc/preface.qbk index 3230a7a..7ea8c17 100644 --- a/doc/preface.qbk +++ b/doc/preface.qbk @@ -45,7 +45,7 @@ step-wise manner. The user's guide is based on examples: lots of them. As much as possible, forward information (i.e. citing a specific piece of information that has not yet been discussed) is avoided in the user's manual portion of each module. In many cases, though, it is unavoidable that advanced -but related topics not be interspersed with the normal flow of discussion. To +but related topics be interspersed with the normal flow of discussion. To alleviate this problem, topics categorized as "advanced" may be skipped at first reading.