aboutsummaryrefslogtreecommitdiff
path: root/gprof
diff options
context:
space:
mode:
Diffstat (limited to 'gprof')
-rw-r--r--gprof/ChangeLog5
-rw-r--r--gprof/README2
-rw-r--r--gprof/gprof.texi2
3 files changed, 7 insertions, 2 deletions
diff --git a/gprof/ChangeLog b/gprof/ChangeLog
index 199f89b..13a5b96 100644
--- a/gprof/ChangeLog
+++ b/gprof/ChangeLog
@@ -1,3 +1,8 @@
+2021-01-01 Nicolas Boulenguez <nicolas@debian.org>
+
+ * README: Correct grammar.
+ * gprof.texi: Likewise.
+
2021-01-01 Alan Modra <amodra@gmail.com>
Update year range in copyright notice of all files.
diff --git a/gprof/README b/gprof/README
index e8df4a4..0a47955 100644
--- a/gprof/README
+++ b/gprof/README
@@ -358,7 +358,7 @@ Short Form: Long Form:
** File Format Changes
The old BSD-derived format used for profile data does not contain a
-magic cookie that allows to check whether a data file really is a
+magic cookie that allows one to check whether a data file really is a
gprof file. Furthermore, it does not provide a version number, thus
rendering changes to the file format almost impossible. GNU gprof
uses a new file format that provides these features. For backward
diff --git a/gprof/gprof.texi b/gprof/gprof.texi
index a589a1a..b2b2048 100644
--- a/gprof/gprof.texi
+++ b/gprof/gprof.texi
@@ -1931,7 +1931,7 @@ load due to other users won't directly affect the output you get.
@section Profiling Data File Format
The old BSD-derived file format used for profile data does not contain a
-magic cookie that allows to check whether a data file really is a
+magic cookie that allows one to check whether a data file really is a
@code{gprof} file. Furthermore, it does not provide a version number, thus
rendering changes to the file format almost impossible. @sc{gnu} @code{gprof}
uses a new file format that provides these features. For backward