Description: Fix spelling-error-in-manpage found by lintian Origin: vendor Author: Alessandro Ghedini Reviewed-by: Alessandro Ghedini Last-Update: 2012-05-10 --- a/docs/valgrind.1 +++ b/docs/valgrind.1 @@ -1174,7 +1174,7 @@ .PP \fB\-\-join\-list\-vol= [default: 10]\fR .RS 4 -Data races that occur between a statement at the end of one thread and another thread can be missed if memory access information is discarded immediately after a thread has been joined\&. This option allows to specify for how many joined threads memory access information should be retained\&. +Data races that occur between a statement at the end of one thread and another thread can be missed if memory access information is discarded immediately after a thread has been joined\&. This option allows one to specify for how many joined threads memory access information should be retained\&. .RE .PP \fB \-\-first\-race\-only= [default: no] \fR @@ -1237,7 +1237,7 @@ .PP \fB\-\-segment\-merging\-interval= [default: 10]\fR .RS 4 -Perform segment merging only after the specified number of new segments have been created\&. This is an advanced configuration option that allows to choose whether to minimize DRD\*(Aqs memory usage by choosing a low value or to let DRD run faster by choosing a slightly higher value\&. The optimal value for this parameter depends on the program being analyzed\&. The default value works well for most programs\&. +Perform segment merging only after the specified number of new segments have been created\&. This is an advanced configuration option that allows one to choose whether to minimize DRD\*(Aqs memory usage by choosing a low value or to let DRD run faster by choosing a slightly higher value\&. The optimal value for this parameter depends on the program being analyzed\&. The default value works well for most programs\&. .RE .PP \fB\-\-shared\-threshold= [default: off]\fR --- a/drd/docs/drd-manual.xml +++ b/drd/docs/drd-manual.xml @@ -356,7 +356,7 @@ Data races that occur between a statement at the end of one thread and another thread can be missed if memory access information is discarded immediately after a thread has been joined. This option - allows to specify for how many joined threads memory access information + allows one to specify for how many joined threads memory access information should be retained. @@ -456,7 +456,7 @@ Perform segment merging only after the specified number of new segments have been created. This is an advanced configuration option - that allows to choose whether to minimize DRD's memory usage by + that allows one to choose whether to minimize DRD's memory usage by choosing a low value or to let DRD run faster by choosing a slightly higher value. The optimal value for this parameter depends on the program being analyzed. The default value works well for most programs. @@ -981,7 +981,7 @@ applications contain intentional races. There exist e.g. applications where the same value is assigned to a shared variable from two different threads. It may be more convenient to suppress such races than to solve - these. This client request allows to suppress such races. + these. This client request allows one to suppress such races. @@ -1014,7 +1014,7 @@ The client request VG_USERREQ__DRD_START_TRACE_ADDR, - which allows to trace all load and store activity for the specified + which allows one to trace all load and store activity for the specified address range. @@ -1304,7 +1304,7 @@ OpenMP stands for Open Multi-Processing. The OpenMP standard consists of a set of compiler directives for C, C++ and Fortran programs that allows a compiler to transform a sequential program into a -parallel program. OpenMP is well suited for HPC applications and allows to +parallel program. OpenMP is well suited for HPC applications and allows one to work at a higher level compared to direct use of the POSIX threads API. While OpenMP ensures that the POSIX API is used correctly, OpenMP programs can still contain data races. So it definitely makes sense to verify OpenMP programs