[binutils-gdb] Fix typo in previous gdb/doc/ commit

[Pedro Alves]

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

commit 2a60e18f8fe3bf9512671e02b39acacb484bb8c6
Author: Pedro Alves <palves@redhat.com>
Date:   Tue Mar 15 11:29:03 2016 +0000

    Fix typo in previous gdb/doc/ commit
    
    Should be s/reliability/reliably/.
    
    gdb/doc/ChangeLog:
    2016-03-15  Pedro Alves  <palves@redhat.com>
    
    	* gdb.texinfo (Tracepoint Actions): Fix typo.

Diff:
---
 gdb/doc/ChangeLog   | 4 ++++
 gdb/doc/gdb.texinfo | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 0606d9d..a48d1c4 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,4 +1,8 @@
 2016-03-15  Pedro Alves  <palves@redhat.com>
+
+	* gdb.texinfo (Tracepoint Actions): Fix typo.
+
+2016-03-15  Pedro Alves  <palves@redhat.com>
 	    Andreas Arnez  <arnez@linux.vnet.ibm.com>
 	    Marcin Kościelnicki  <koriakin@0x04.net>
 
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 5f88335..71657b0 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -12878,7 +12878,7 @@ Collect all local variables.
 Collect the return address.  This is helpful if you want to see more
 of a backtrace.
 
-@emph{Note:} The return address location can not always be reliability
+@emph{Note:} The return address location can not always be reliably
 determined up front, and the wrong address / registers may end up
 collected instead.  On some architectures the reliability is higher
 for tracepoints at function entry, while on others it's the opposite.