From: Andreas Schwab <schwab@linux-m68k.org>
Date: Mon, 14 Jun 1999 01:36:32 +0000 (+0000)
Subject: Fix typo.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=a53f781e5784a5de4a8bad116393f37bdceedbd8;p=binutils-gdb.git

Fix typo.
---

diff --git a/gprof/ChangeLog b/gprof/ChangeLog
index a41142dcff5..34f9e189bc1 100644
--- a/gprof/ChangeLog
+++ b/gprof/ChangeLog
@@ -1,3 +1,7 @@
+Mon Jun 14 10:35:28 1999  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>
+
+	* gprof.texi: Fix typo.
+
 1999-06-13  Ian Lance Taylor  <ian@zembu.com>
 
 	From Bob Byrnes <byrnes@curl.com>:
diff --git a/gprof/gprof.texi b/gprof/gprof.texi
index 43d8b9fc451..b4606b42f4b 100644
--- a/gprof/gprof.texi
+++ b/gprof/gprof.texi
@@ -687,7 +687,7 @@ because some of the definitions may be local (i.e., static).  Unless a
 function name is unique in a program, you must use the colon notation
 explained below to specify a function from a specific source file.
 
-Sometimes, function names contain dots.  In such cases, it is necessar
+Sometimes, function names contain dots.  In such cases, it is necessary
 to add a leading colon to the name.  For example, @samp{:.mul} selects
 function @samp{.mul}.