Use @key{} where it is missing in the manuals

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 2c757dd39d5..2b5f64827c4 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -941,10 +941,10 @@ The profiler report buffer shows, on each line, a function that was
 called, followed by how much resource (processor or memory) it used in
 absolute and percentage times since profiling started.  If a given
 line has a @samp{+} symbol at the left-hand side, you can expand that
-line by typing @key{RET}, in order to see the function(s) called by
-the higher-level function.  Use a prefix argument (@key{C-u RET}) to
-see the whole call tree below a function.  Pressing @key{RET} again
-will collapse back to the original state.
+line by typing @kbd{@key{RET}}, in order to see the function(s) called
+by the higher-level function.  Use a prefix argument (@kbd{C-u
+@key{RET}}) to see the whole call tree below a function.  Pressing
+@kbd{@key{RET}} again will collapse back to the original state.
 
 Press @kbd{j} or @kbd{mouse-2} to jump to the definition of a function.
 Press @kbd{d} to view a function's documentation.