correcte typo and a few picky changes

docs/whats_new.qbk

@@ -17,13 +17,13 @@ anniversary of the first commit to our source code repository. Since then,
 we have seen over 12300 commits amounting to more than 220000 lines of C++ code.
 
 The major focus of this release was to improve the reliability of large scale
-runs. We believe to have achieved this goal as we now can reliably run __hpx__
+runs. We believe this goal has been achieved as we now can reliably run __hpx__
 applications on up to ~24k cores. We have also shown that HPX can be used with
 success for symmetric runs (applications using both, host cores and Intel
 Xeon/Phi coprocessors). This is a huge step forward in terms of
 the usability of __hpx__. The main focus of this work involed isolating
 the causes of the segmentation faults at start up and shut down.  Many of
-these issues were discovered to be the result of the suspention of threads
+these issues were discovered to be the result of the suspension of threads
 which hold locks.
 
 A very important improvement introduced with this release is the
@@ -48,8 +48,8 @@ invoke all of the algorithms asynchronously.
 This release adds a first implementation of `hpx::vector` which is a distributed
 data structure closely aligned to the functionality of `std::vector`. The
 difference is that `hpx::vector` stores the data in partitions where the
-partitions can be distributed over different localities. We started to work on
-allowing to use the parallel algorithms with `hpx::vector`. At this point we have
+partitions can be distributed over different localities. We started work on the
+ability to use the parallel algorithms with `hpx::vector`. At this point we have
 implemented only a few of the parallel algorithms to support distributed data
 structures (like `hpx::vector`) for testing purposes (see [issue 1338] for
 a documentation of our progress).
@@ -61,7 +61,7 @@ compatible to C++11. These changes have caused the following issues for
 backward compatiblility:
 
 * Move to Variadics- All of the API now uses variadic templates. However, this
-change required to modify the argument sequence for some of the exiting API
+change required modification of the argument sequence for some of the exiting API
 functions ([funcref hpx::async_continue `hpx::async_continue`],
 [funcref hpx::apply_continue `hpx::apply_continue`],
 [funcref hpx::when_each `hpx::when_each`],
@@ -236,5 +236,5 @@ Here is a list of the important tickets we closed for this release.
 [endsect] [/ What's New]
 
 [/Proofread by:]
-[/Adrian Serio 3-13-12]
-
+[/Adrian Serio 3-13-15]
+[/Patricia Grubel 3-20-15]