summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2010-05-20 10:56:14 (GMT)
committer Denys Vlasenko <vda.linux@googlemail.com>2010-05-20 10:56:14 (GMT)
commit131ed3bcc9c9eabcb4bd6a063c24c6f9922f1491 (patch)
treea1a8e82b1520f5fb0d5e4ce50ba3c2d30b591f51
parenta0ec4f500c7b8b2ac1c7e34c9a2ee7504c7f8914 (diff)
downloadbusybox-131ed3bcc9c9eabcb4bd6a063c24c6f9922f1491.tar.gz
busybox-131ed3bcc9c9eabcb4bd6a063c24c6f9922f1491.tar.bz2
update shell/README
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
-rw-r--r--shell/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/shell/README b/shell/README
index 550c712..6a9f5b6 100644
--- a/shell/README
+++ b/shell/README
@@ -34,7 +34,7 @@ Shell Command Language
It says that shell must implement special built-ins. Special built-ins
differ from regular ones by the fact that variable assignments
-done on special builtin is *PRESERVED*. That is,
+done on special builtin are *PRESERVED*. That is,
VAR=VAL special_builtin; echo $VAR
@@ -43,7 +43,7 @@ should print VAL.
(Another distinction is that an error in special built-in should
abort the shell, but this is not such a critical difference,
and moreover, at least bash's "set" does not follow this rule,
-which is even codified in autoconf now...).
+which is even codified in autoconf configure logic now...)
List of special builtins:
@@ -73,7 +73,7 @@ unset [-fv] name...
In practice, no one uses this obscure feature - none of these builtins
gives any special reasons to play such dirty tricks.
-However. This section says that *function invocation* should act
+However. This section also says that *function invocation* should act
similar to special built-in. That is, variable assignments
done on function invocation should be preserved after function invocation.