fix some typos.

[ardour-manual-diverged] / _manual / 24_lua-scripting / 01_brain_dump.html

diff --git a/_manual/24_lua-scripting/01_brain_dump.html b/_manual/24_lua-scripting/01_brain_dump.html
index 2a8be189e77871949b6ad8ca321e58c91eaba526..c73fa4de9b8411814d618803d08c6e799fe0275f 100644 (file)
--- a/_manual/24_lua-scripting/01_brain_dump.html
+++ b/_manual/24_lua-scripting/01_brain_dump.html
@@ -15,13 +15,13 @@ Examples for these include voice-activate (record-arm specific tracks and roll t
 rename all regions after a specific timecode, launch an external application when a certain track is soloed, generate automation curves
 or simply provide a quick shortcut for a custom batch operation.
 </p><p>
-Cases like this call for means to extend the DAW without actually changing the DAW itself. This is here scripting comes in.
+Cases like this call for means to extend the DAW without actually changing the DAW itself. This is where scripting comes in.
 </p><p>
 "Scripting" refers to tasks that could alternatively be executed step-by-step by a human operator.
 </p><p>
 Lua is a tiny and simple language which is easy to learn, yet allows for comprehensive solutions.
 Lua is also a glue language it allows to tie existing component in Ardour together in unprecedented ways,
-and most importantly Lua is one of the few scripting-languages which be safely used in a real-time environment.
+and most importantly Lua is one of the few scripting-languages which can be safely used in a real-time environment.
 </p><p>
 A good introduction to Lua is the book <a href="http://www.lua.org/pil/">Programming in Lua</a>. The first edition is available online,
 but if you have the means buy a copy of the book, it not only helps to support the Lua project,
@@ -142,7 +142,7 @@ The common part for all scripts is the "Descriptor". It's a Lua function which r
 <dl>
        <dt>type [required]</dt><dd>one of "<code>DSP</code>", "<code>Session</code>", "<code>EditorHook</code>", "<code>EditorAction</code>" (the type is not case-sensitive)</dd>
        <dt>name [required]</dt><dd>Name/Title of the script</dd>
-       <dt>author</dt<dd>Your Name</dd>
+       <dt>author</dt><dd>Your Name</dd>
        <dt>license</dt><dd>The license of the script (e.g. "GPL" or "MIT")</dd>
        <dt>description</dt><dd>A longer text explaining to the user what the script does</dd>
 </dl>