Index: docs/manual/megatest_manual.html
==================================================================
--- docs/manual/megatest_manual.html
+++ docs/manual/megatest_manual.html
@@ -2382,10 +2382,29 @@
 <div class="listingblock">
 <div class="title">Propagate environment to next step</div>
 <div class="content monospaced">
 <pre>$MT_MEGATEST -env2file .ezsteps/${stepname}</pre>
 </div></div>
+</div>
+<div class="sect2">
+<h3 id="_scripts">Scripts</h3>
+<div class="listingblock">
+<div class="title">Specifying scripts inline (best used for only simple scripts)</div>
+<div class="content monospaced">
+<pre>[scripts]
+loaddb #!/bin/bash
+  sqlite3 $1 &lt;&lt;EOF
+  .mode tabs
+  .import $2 data
+  .q
+  EOF</pre>
+</div></div>
+<div class="paragraph"><p>The above snippet results in the creation of an executable script
+called "loaddb" in the test directory. NOTE: every line in the script
+must be prefixed with the exact same number of spaces. Lines beginning
+with a # will not work as expected. Currently you cannot indent
+intermediate lines.</p></div>
 <div class="listingblock">
 <div class="title">Full example with ezsteps, logpro rules, scripts etc.</div>
 <div class="content monospaced">
 <pre># You can include a common file
 #

Index: docs/manual/reference.txt
==================================================================
--- docs/manual/reference.txt
+++ docs/manual/reference.txt
@@ -464,14 +464,12 @@
 
 Complex mapping example
 ~~~~~~~~~~~~~~~~~~~~~~~
 
 
-
 // image::itemmap.png[]
 image::complex-itemmap.png[]
-
 
 We accomplish this by configuring the testconfigs of our tests C D and E as follows:
 
 .Testconfig for Test E has
 ----------------------
@@ -514,14 +512,10 @@
 
 
 itemstable
 ~~~~~~~~~~
 An alternative to defining items is the itemstable section.  This lets you define the itempath in a table format rather than specifying components and relying on getting all permutations of those components.
-
-
-
-
 
 Dynamic Flow Dependency Tree
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .Autogeneration waiton list for dynamic flow dependency trees
@@ -652,10 +646,30 @@
 .Propagate environment to next step
 ----------------------------
 $MT_MEGATEST -env2file .ezsteps/${stepname}	  
 ----------------------------
 
+Scripts
+~~~~~~~
+
+.Specifying scripts inline (best used for only simple scripts)
+----------------------------
+[scripts]
+loaddb #!/bin/bash
+  sqlite3 $1 <<EOF
+  .mode tabs
+  .import $2 data
+  .q
+  EOF
+----------------------------
+
+The above snippet results in the creation of an executable script
+called "loaddb" in the test directory. NOTE: every line in the script
+must be prefixed with the exact same number of spaces. Lines beginning
+with a # will not work as expected. Currently you cannot indent
+intermediate lines.
+
 .Full example with ezsteps, logpro rules, scripts etc.
 -----------------
 # You can include a common file
 #
 [include #{getenv MT_RUN_AREA_HOME}/global-testconfig.inc]