[PATCH obv] Fix typo in lookup_cmd_1 comment

[Simon Marchi <simon dot marchi at ericsson dot com>]

FYI, I pushed this as obvious.

gdb/ChangeLog:

	* cli/cli-decode.c (lookup_cmd_1): Fix typo in comment.
---
 gdb/ChangeLog        | 4 ++++
 gdb/cli/cli-decode.c | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 90d25cf4a1..89bbb8fbaf 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2017-01-11  Simon Marchi  <simon.marchi@ericsson.com>
+
+	* cli/cli-decode.c (lookup_cmd_1): Fix typo in comment.
+
 2017-01-10  Tom Tromey  <tom@tromey.com>
 
 	* python/py-type.c (typy_legacy_template_argument): Update.
diff --git a/gdb/cli/cli-decode.c b/gdb/cli/cli-decode.c
index d3be93c4b8..436a7ed4ca 100644
--- a/gdb/cli/cli-decode.c
+++ b/gdb/cli/cli-decode.c
@@ -1331,7 +1331,7 @@ valid_user_defined_cmd_name_p (const char *name)
    if no prefix command was ever found.  For example, in the case of "info a",
    "info" matches without ambiguity, but "a" could be "args" or "address", so
    *RESULT_LIST is set to the cmd_list_element for "info".  So in this case
-   RESULT_LIST should not be interpeted as a pointer to the beginning of a
+   RESULT_LIST should not be interpreted as a pointer to the beginning of a
    list; it simply points to a specific command.  In the case of an ambiguous
    return *TEXT is advanced past the last non-ambiguous prefix (e.g.
    "info t" can be "info types" or "info target"; upon return *TEXT has been
-- 
2.11.0