commit: 9a7164477f77f5346e32d6073932018bdae70961
Author: Sebastian Engel <sighunter <AT> gmx <DOT> de>
AuthorDate: Mon Aug 12 20:35:40 2024 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Aug 23 15:16:25 2024 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=9a716447
tools-reference/echo: Improve wording in abuse chapter
"should be used as less as possible" is not a correct expression,
use "should be avoided" instead.
Signed-off-by: Sebastian Engel <sighunter <AT> gmx.de>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
tools-reference/echo/text.xml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tools-reference/echo/text.xml b/tools-reference/echo/text.xml
index f72d833..9bce77c 100644
--- a/tools-reference/echo/text.xml
+++ b/tools-reference/echo/text.xml
@@ -29,12 +29,12 @@ the same as the former, but they won't print the trailing
newline
<p>
All usage of the form <c>echo ${somevar} | grep substring</c> just to
-check if the content of the <c>${somevar}</c> variable
-contains <c>substring</c>, or more often, <c>echo ${somevar} |
-command</c>, is deprecated and should be (and in most cases, can be)
-used as less as possible: doing so involves for no reason an
-additional shell session and a pipe. The "here strings" section
-describes the preferred way of dealing with such cases.
+check if the content of the <c>${somevar}</c> variable contains
+<c>substring</c>, or more often, <c>echo ${somevar} | command</c>,
+is deprecated and should be (and in most cases, can be) avoided:
+doing so involves for no reason an additional shell session and a pipe.
+The "here strings" section describes the preferred way
+of dealing with such cases.
</p>
</body>
</section>
