doc: fix typos

doc/doxygen/chapters/00introduction.doxy

@@ -91,14 +91,13 @@ fields that the application may use to give hints to the scheduler (such as
 priority levels).
 
 By default, task dependencies are inferred from data dependency (sequential
-coherence) by StarPU. The application can however disable sequential coherency
-for some data, and dependencies be expressed by hand.
+coherency) by StarPU. The application can however disable sequential coherency
+for some data, and dependencies can be specifically expressed.
 A task may be identified by a unique 64-bit number chosen by the application
 which we refer as a \b tag.
-Task dependencies can be enforced by hand either by the means of callback functions, by
+Task dependencies can be enforced either by the means of callback functions, by
 submitting other tasks, or by expressing dependencies
-between tags (which can thus correspond to tasks that have not been submitted
-yet).
+between tags (which can thus correspond to tasks that have not yet been submitted).
 
 // TODO insert illustration f(Ar, Brw, Cr) + ..
 // DSM
@@ -107,7 +106,7 @@ yet).
 
 Because StarPU schedules tasks at runtime, data transfers have to be
 done automatically and ``just-in-time'' between processing units,
-relieving the application programmer from explicit data transfers.
+relieving application programmers from explicit data transfers.
 Moreover, to avoid unnecessary transfers, StarPU keeps data
 where it was last needed, even if was modified there, and it
 allows multiple copies of the same data to reside at the same time on
@@ -134,8 +133,8 @@ A <b>memory node</b> can be either the main RAM, GPU-embedded memory or a disk m
 A \b bus is a link between memory nodes.
 
 A <b>data handle</b> keeps track of replicates of the same data (\b registered by the
-application) over various memory nodes. The data management library manages
-keeping them coherent.
+application) over various memory nodes. The data management library manages to
+keep them coherent.
 
 The \b home memory node of a data handle is the memory node from which the data
 was registered (usually the main memory node).

doc/doxygen/chapters/01building.doxy

@@ -18,7 +18,7 @@ available, simply type:
 $ apt-cache search starpu
 \endverbatim
 
-To install what you need, type:
+To install what you need, type for example:
 
 \verbatim
 $ sudo apt-get install libstarpu-1.2 libstarpu-dev
@@ -42,8 +42,7 @@ If <c>hwloc</c> is not available on your system, the option
 \ref without-hwloc "--without-hwloc" should be explicitely given when calling the
 <c>configure</c> script. If <c>hwloc</c> is installed with a <c>pkg-config</c> file,
 no option is required, it will be detected automatically, otherwise
-\ref with-hwloc "--with-hwloc" should be used to specify the location of
-<c>hwloc</c>.
+\ref with-hwloc "--with-hwloc" should be used to specify its location.
 
 \subsection GettingSources Getting Sources
 
@@ -78,7 +77,7 @@ $ svn checkout svn://scm.gforge.inria.fr/svn/starpu/trunk StarPU
 Running <c>autogen.sh</c> is not necessary when using the tarball
 releases of StarPU.  If you are using the source code from the svn
 repository, you first need to generate the configure scripts and the
-Makefiles. This requires the availability of <c>autoconf</c>,
+Makefiles. This requires the availability of <c>autoconf</c> and
 <c>automake</c> >= 2.60.
 
 \verbatim
@@ -97,7 +96,7 @@ make sure to post the content of <c>config.log</c> when reporting the issue.
 
 By default, the files produced during the compilation are placed in
 the source directory. As the compilation generates a lot of files, it
-is advised to to put them all in a separate directory. It is then
+is advised to put them all in a separate directory. It is then
 easier to cleanup, and this allows to compile several configurations
 out of the same source tree. For that, simply enter the directory
 where you want the compilation to produce its files, and invoke the
@@ -141,11 +140,10 @@ libraries names (<c>libstarpu-1.2.so</c>, <c>libstarpumpi-1.2.so</c> and
 
 \subsection SettingFlagsForCompilingLinkingAndRunningApplications Setting Flags for Compiling, Linking and Running Applications
 
-StarPU provides a pkg-config executable to obtain relevant compiler
-and linker flags.
-Compiling and linking an application against StarPU may require to use
-specific flags or libraries (for instance <c>CUDA</c> or <c>libspe2</c>).
-To this end, it is possible to use the tool <c>pkg-config</c>.
+StarPU provides a <c>pkg-config</c> executable to obtain relevant compiler
+and linker flags. As compiling and linking an application against
+StarPU may require to use specific flags or libraries (for instance
+<c>CUDA</c> or <c>libspe2</c>).
 
 If StarPU was not installed at some standard location, the path of StarPU's
 library must be specified in the environment variable <c>PKG_CONFIG_PATH</c> so
@@ -267,7 +265,8 @@ schedulers, for instance <c>STARPU_SCHED=dmda</c>.
 \subsection TaskSizeOverhead Task Size Overhead
 
 This benchmark gives a glimpse into how long a task should be (in µs) for StarPU overhead
-to be low enough to keep efficiency.  Run <c>tasks_size_overhead.sh</c>, it will generate a plot
+to be low enough to keep efficiency.  Running
+<c>tasks_size_overhead.sh</c> generates a plot
 of the speedup of tasks of various sizes, depending on the number of CPUs being
 used.