[binutils-gdb] gprofng: fix 32889 Typo in documentation

[Vladimir Mezentsev]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9567087349c6f33a437b071d1c6b6c04ad4debef

commit 9567087349c6f33a437b071d1c6b6c04ad4debef
Author: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Date:   Fri Apr 18 14:08:20 2025 -0700

    gprofng: fix 32889 Typo in documentation
    
    gprofng/ChangeLog
    2025-04-18  Vladimir Mezentsev  <vladimir.mezentsev@oracle.com>
    
            * doc/gprofng_ug.texi: Fix typo.

Diff:
---
 gprofng/doc/gprofng_ug.texi | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/gprofng/doc/gprofng_ug.texi b/gprofng/doc/gprofng_ug.texi
index 714709067d9..f23f7b379ee 100644
--- a/gprofng/doc/gprofng_ug.texi
+++ b/gprofng/doc/gprofng_ug.texi
@@ -310,9 +310,8 @@ Since there is no need to recompile, existing executables can be used
 and the profile measures the behaviour of exactly the same executable that is
 used in production runs.
 
-With sampling, one inherently profiles a different executable, because
-the calls to the instrumentation library may affect the compiler optimizations
-and run time behaviour.
+With tracing, one inherently profiles a different executable, because
+the calls to the instrumentation library may affect runtime behaviour.
 
 @item
 With sampling, there are very few restrictions on what can be profiled and