summaryrefslogtreecommitdiff
path: root/man/building.texi
diff options
context:
space:
mode:
authorJuri Linkov <juri@jurta.org>2005-08-09 21:48:12 +0000
committerJuri Linkov <juri@jurta.org>2005-08-09 21:48:12 +0000
commit869d986e167c4b1dfca50036db22a1746dfa4006 (patch)
treed0ddcd88a70c2c008fddc1f04d5c03810fe9db0e /man/building.texi
parent87737bc2a19eca86a48948a44c28d345bd4bcdc1 (diff)
downloademacs-869d986e167c4b1dfca50036db22a1746dfa4006.tar.gz
(Compilation): Use `itemx' instead of `item'.
(Grep Searching): Simplify phrase.
Diffstat (limited to 'man/building.texi')
-rw-r--r--man/building.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/man/building.texi b/man/building.texi
index 69b56f467f5..69ca71b0fdc 100644
--- a/man/building.texi
+++ b/man/building.texi
@@ -52,7 +52,7 @@ Invoke a compiler with the same command as in the last invocation of
Run @code{grep} asynchronously under Emacs, with matching lines
listed in the buffer named @samp{*grep*}.
@item M-x grep-find
-@item M-x find-grep
+@itemx M-x find-grep
Run @code{grep} via @code{find}, with user-specified arguments, and
collect output in the buffer named @samp{*grep*}.
@item M-x kill-compilation
@@ -325,7 +325,7 @@ Emacs. @xref{MS-DOS}.
@findex grep
Just as you can run a compiler from Emacs and then visit the lines
-where there were compilation errors, you can also run @code{grep} and
+with compilation errors, you can also run @code{grep} and
then visit the lines on which matches were found. This works by
treating the matches reported by @code{grep} as if they were ``errors.''