summaryrefslogtreecommitdiff
path: root/doc/grammar.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2021-02-14 15:10:15 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2021-02-14 15:10:15 +0000
commit44be69112c71fe65784cc014995044c2a191a449 (patch)
tree774de7de5d75c202903080b74bc5eca87ed1d8d6 /doc/grammar.html
parent6ff749e62652103b3ab84ef145691602ed6e0fea (diff)
downloadexecline-44be69112c71fe65784cc014995044c2a191a449.tar.xz
Apply doc fixes by flexibeast and suggestions by Profpatsch&aranea
Diffstat (limited to 'doc/grammar.html')
-rw-r--r--doc/grammar.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/grammar.html b/doc/grammar.html
index 419c13e..74ee60f 100644
--- a/doc/grammar.html
+++ b/doc/grammar.html
@@ -69,10 +69,10 @@ and 128&nbsp;KB on Linux. </li>
<p>
Knowing that, and wanting lightweight and efficient scripts, I
wondered: "Why should the interpreter stay in memory while the script
-is executing&nbsp;? Why not parse the script once and for all, put
+is executing? Why not parse the script once and for all, put
it all into one <em>argv</em>, and just execute into that <em>argv</em>,
relying on external commands (which will be called from within the
-script) to control the execution flow&nbsp;?"
+script) to control the execution flow?"
</p>
<p> <tt>execline</tt> was born. </p>