diff --git a/html/TT_ug_editing.m b/html/TT_ug_editing.m
index b288ae46ba56e0f1a31d91863b99ef6f017ba7a0..112e09faa6a465e9d3fcb49b48672528290ecac1 100644
--- a/html/TT_ug_editing.m
+++ b/html/TT_ug_editing.m
@@ -1,8 +1,8 @@
 %% Editing a Tabular Expression
 %
-% The Tabular Expression Dialog allows users to graphically layout a
-% tabular expression, for which conditions and outputs can be filled in
-% using the embedded matlab subset of the Matlab languauge.
+% The Table Tool allows users to graphically layout a
+% tabular expression, for which conditions and outputs can be specified
+% using the embedded Matlab subset of the Matlab language.
 %% Layout
 % The Dialog interface allows for the creation of 1-Dimensional vertical
 % and horizontal tables, as well as 2-Dimensional tables. The tool supports
@@ -25,24 +25,24 @@
 % The input box labeled "Inputs" allows for the specification of inputs to
 % the table. There is no limit in the number of inputs supported. Inputs
 % are specified in a comma delimited list. names of inputs must conform to
-% the matlab syntax conventions.
+% the Matlab syntax conventions.
 %
 % *Typing*
 % 
-% typing information can be specified for each input declared. this allows
-% for users to input dependant types. The format for typing follows that of
+% Typing information can be specified for each input declared. This allows
+% for users to declare inputs as dependent types. The format for typing follows that of
 % PVS, some examples:
 %
 % * |x, y, z| - 3 inputs with the default type
 % * |x, y:bool| - 2 inputs, y with specified type, x has the default
 % type.
 % * |x:real, y:real, z:bool| - 2 inputs of type real and one of type bool
-% * |x:real, y:{t:real|t>x}| - 2 inputs of type real, y is dependant on x,
-% and is restricited to those value strictly greater than x
+% * |x:real, y:{t:real|t>x}| - 2 inputs of type real, y is dependent on x,
+% and is restricted to those value strictly greater than x
 %
 %% Expression Name
-% the expression name will be the name indentifying the block, it will also
-% be the function name for an generated matlab codes.
+% the expression name will be the name identifying the block, it will also
+% be the function name for generated Matlab code.
 %
 % *Typing*
 %
@@ -51,23 +51,23 @@
 % the same as that for inputs.
 % 
 %% Conditions
-% Text input for a condition box must be valid embedded matlab code.
-% Expressions in condition boxes will be evaulated with the assumed type of
-% boolean. Since embedded matlab is not typechecked this is a pottential
-% cause of errors. By running pvs on a table, each expression in a
+% Text input for a condition box must be valid embedded Matlab code.
+% Expressions in condition boxes will be evaluated with the assumed type of
+% boolean. Since embedded Matlab is not typechecked this is a potential
+% cause of errors. By running a syntax check on a table, each expression in a
 % condition box will be checked that it is of type boolean.
 %
 % For a table with multiple outputs, the horizontal condition boxes
-% represent different outputs, more detail about this in the output
+% represent different outputs, more detail about this in the following
 % section.
 %
 %% Outputs
-% The outputs of the function are specified in the Outputs grid. Outputs must be an expression that 
+% The outputs of the function are specified in the outputs grid. Outputs must be an expression that 
 % will evaluate to a definite value. Each output specified should be the same type, however since
-% matlab is not strongly typed, almost every possible value will be interpreted as a compatible type. 
+% Matlab is not strongly typed, almost every possible value will be interpreted as a compatible type. 
 % The tool supports 2 output modes: single output and multiple output.
 %
-% The output mode can be specifed from the edit menu as seen in the
+% The output mode can be specified from the edit menu as seen in the
 % following figure:
 %
 % <<ug_layout_4.png>>
@@ -75,32 +75,32 @@
 % *Single Output*
 %
 % For a single output table, the vertical grid can be used for another
-% dimension of conditons. Each output cell shall be a single expression
-% which will evaulate to the output under the interpreted conditions.
+% dimension of conditions. Each output cell shall be a single expression
+% which will evaluate to the output under the interpreted conditions.
 %
 % *Multiple Output*
 %
 % For a table with multiple outputs, the horizontal condition grid is used
 % to specify the outputs of the table. The same rules for typing apply as noted in the 
-% inputs and expression section of this documnet
+% inputs and expression section of this document.
 %
 % Each cell in the condition grid
 % specifies the name (and type) of an output. See the following figure for
 % an example. Each cell in the output grid specifies an output that
-% cooresponds to the output specified in the horizontal grid above it.
+% corresponds to the output specified in the horizontal grid above it.
 %
-% In the example bellow 
+% In the example below 
 % the table has 2
-% different outputs labeled, output1 and output2. the outputs have
-% different types, which allows for powerful function specification.
+% different outputs labeled, output1 and output2; the outputs have
+% different types. Multiple outputs facilitates robust function specification.
 %
 % <<ug_layout_5.png>>
 %
 %% Ports
 %
 % The "Ports" button will bring up the ports and data manager window (see
-% next figure.) From here you can define the datatypes of signals, as well
-% as anyother fuctionality as you would with another Simulink block.
+% next figure.) From here you can specify the datatypes of signals, as well
+% as any other functionality as you would with another Simulink block.
 %
 % <<ug_layout_6.png>>
 %
@@ -109,7 +109,7 @@
 % The edit button is a toggle button which allows for the user to hide the
 % editing buttons which include the new row, delete row, new subgrid, etc.
 % buttons. Hiding these buttons allows for cleaner looking table with fewer
-% distractions allowing the user to consentrate on the content in the
+% distractions allowing the user to concentrate on the content in the
 % table. see an example below.
 %
 % <<ug_layout_7.png>>
\ No newline at end of file
diff --git a/html/html/TT_ug_editing.html b/html/html/TT_ug_editing.html
index 32d9f0c23a3c6e21f8229e4153eebb1586932cba..e22707f99033856ee282725fef861ca3b8ddc95d 100644
--- a/html/html/TT_ug_editing.html
+++ b/html/html/TT_ug_editing.html
@@ -6,7 +6,7 @@
    <!--
 This HTML is auto-generated from an M-file.
 To make changes, update the M-file and republish this document.
-      --><title>Editing a Tabular Expression</title><meta name="generator" content="MATLAB 7.10"><meta name="date" content="2010-11-26"><meta name="m-file" content="TT_ug_editing"><style type="text/css">
+      --><title>Editing a Tabular Expression</title><meta name="generator" content="MATLAB 7.10"><meta name="date" content="2010-11-29"><meta name="m-file" content="TT_ug_editing"><style type="text/css">
 
 body {
   background-color: white;
@@ -62,14 +62,14 @@ p.footer {
   color: gray;
 }
 
-  </style></head><body><div class="content"><h1>Editing a Tabular Expression</h1><!--introduction--><p>The Tabular Expression Dialog allows users to graphically layout a tabular expression, for which conditions and outputs can be filled in using the embedded matlab subset of the Matlab languauge.</p><!--/introduction--><h2>Contents</h2><div><ul><li><a href="#1">Layout</a></li><li><a href="#2">Inputs</a></li><li><a href="#3">Expression Name</a></li><li><a href="#4">Conditions</a></li><li><a href="#5">Outputs</a></li><li><a href="#6">Ports</a></li><li><a href="#7">Edit Mode</a></li></ul></div><h2>Layout<a name="1"></a></h2><p>The Dialog interface allows for the creation of 1-Dimensional vertical and horizontal tables, as well as 2-Dimensional tables. The tool supports multiple outputs for 1-Dimensional vertical tables.</p><p>The figure below shows an example 2-Dimensional Table with the Vertical Conditions, Horizontal Conditions, and Outputs notated.</p><p><img vspace="5" hspace="5" src="ug_layout_2.png" alt=""> </p><p>The "new" button will create an additional condition box for a particular grid. The "delete" button will remove the last condition box in a grid. For each condition in the vertical conditions, a subgrid can be created. To create a subgrid for a condition click on the "+" button next to the intended box.</p><p>Whenever the configuration of the vertical and horizontal conditions is changed the corresponding output boxes will update as well.</p><h2>Inputs<a name="2"></a></h2><p>The input box labeled "Inputs" allows for the specification of inputs to the table. There is no limit in the number of inputs supported. Inputs are specified in a comma delimited list. names of inputs must conform to the matlab syntax conventions.</p><p><b>Typing</b></p><p>typing information can be specified for each input declared. this allows for users to input dependant types. The format for typing follows that of PVS, some examples:</p><div><ul><li><tt>x, y, z</tt> - 3 inputs with the default type</li><li><tt>x, y:bool</tt> - 2 inputs, y with specified type, x has the default type.</li><li><tt>x:real, y:real, z:bool</tt> - 2 inputs of type real and one of type bool</li><li><tt>x:real, y:{t:real|t&gt;x}</tt> - 2 inputs of type real, y is dependant on x, and is restricited to those value strictly greater than x</li></ul></div><h2>Expression Name<a name="3"></a></h2><p>the expression name will be the name indentifying the block, it will also be the function name for an generated matlab codes.</p><p><b>Typing</b></p><p>For single output tables, typing information for the output type of the function can be specified in this textbox. formatting for the typing is the same as that for inputs.</p><h2>Conditions<a name="4"></a></h2><p>Text input for a condition box must be valid embedded matlab code. Expressions in condition boxes will be evaulated with the assumed type of boolean. Since embedded matlab is not typechecked this is a pottential cause of errors. By running pvs on a table, each expression in a condition box will be checked that it is of type boolean.</p><p>For a table with multiple outputs, the horizontal condition boxes represent different outputs, more detail about this in the output section.</p><h2>Outputs<a name="5"></a></h2><p>The outputs of the function are specified in the Outputs grid. Outputs must be an expression that will evaluate to a definite value. Each output specified should be the same type, however since matlab is not strongly typed, almost every possible value will be interpreted as a compatible type. The tool supports 2 output modes: single output and multiple output.</p><p>The output mode can be specifed from the edit menu as seen in the following figure:</p><p><img vspace="5" hspace="5" src="ug_layout_4.png" alt=""> </p><p><b>Single Output</b></p><p>For a single output table, the vertical grid can be used for another dimension of conditons. Each output cell shall be a single expression which will evaulate to the output under the interpreted conditions.</p><p><b>Multiple Output</b></p><p>For a table with multiple outputs, the horizontal condition grid is used to specify the outputs of the table. The same rules for typing apply as noted in the inputs and expression section of this documnet</p><p>Each cell in the condition grid specifies the name (and type) of an output. See the following figure for an example. Each cell in the output grid specifies an output that cooresponds to the output specified in the horizontal grid above it.</p><p>In the example bellow the table has 2 different outputs labeled, output1 and output2. the outputs have different types, which allows for powerful function specification.</p><p><img vspace="5" hspace="5" src="ug_layout_5.png" alt=""> </p><h2>Ports<a name="6"></a></h2><p>The "Ports" button will bring up the ports and data manager window (see next figure.) From here you can define the datatypes of signals, as well as anyother fuctionality as you would with another Simulink block.</p><p><img vspace="5" hspace="5" src="ug_layout_6.png" alt=""> </p><h2>Edit Mode<a name="7"></a></h2><p>The edit button is a toggle button which allows for the user to hide the editing buttons which include the new row, delete row, new subgrid, etc. buttons. Hiding these buttons allows for cleaner looking table with fewer distractions allowing the user to consentrate on the content in the table. see an example below.</p><p><img vspace="5" hspace="5" src="ug_layout_7.png" alt=""> </p><p class="footer"><br>
+  </style></head><body><div class="content"><h1>Editing a Tabular Expression</h1><!--introduction--><p>The Table Tool allows users to graphically layout a tabular expression, for which conditions and outputs can be specified using the embedded Matlab subset of the Matlab language.</p><!--/introduction--><h2>Contents</h2><div><ul><li><a href="#1">Layout</a></li><li><a href="#2">Inputs</a></li><li><a href="#3">Expression Name</a></li><li><a href="#4">Conditions</a></li><li><a href="#5">Outputs</a></li><li><a href="#6">Ports</a></li><li><a href="#7">Edit Mode</a></li></ul></div><h2>Layout<a name="1"></a></h2><p>The Dialog interface allows for the creation of 1-Dimensional vertical and horizontal tables, as well as 2-Dimensional tables. The tool supports multiple outputs for 1-Dimensional vertical tables.</p><p>The figure below shows an example 2-Dimensional Table with the Vertical Conditions, Horizontal Conditions, and Outputs notated.</p><p><img vspace="5" hspace="5" src="ug_layout_2.png" alt=""> </p><p>The "new" button will create an additional condition box for a particular grid. The "delete" button will remove the last condition box in a grid. For each condition in the vertical conditions, a subgrid can be created. To create a subgrid for a condition click on the "+" button next to the intended box.</p><p>Whenever the configuration of the vertical and horizontal conditions is changed the corresponding output boxes will update as well.</p><h2>Inputs<a name="2"></a></h2><p>The input box labeled "Inputs" allows for the specification of inputs to the table. There is no limit in the number of inputs supported. Inputs are specified in a comma delimited list. names of inputs must conform to the Matlab syntax conventions.</p><p><b>Typing</b></p><p>Typing information can be specified for each input declared. This allows for users to declare inputs as dependent types. The format for typing follows that of PVS, some examples:</p><div><ul><li><tt>x, y, z</tt> - 3 inputs with the default type</li><li><tt>x, y:bool</tt> - 2 inputs, y with specified type, x has the default type.</li><li><tt>x:real, y:real, z:bool</tt> - 2 inputs of type real and one of type bool</li><li><tt>x:real, y:{t:real|t&gt;x}</tt> - 2 inputs of type real, y is dependent on x, and is restricted to those value strictly greater than x</li></ul></div><h2>Expression Name<a name="3"></a></h2><p>the expression name will be the name identifying the block, it will also be the function name for generated Matlab code.</p><p><b>Typing</b></p><p>For single output tables, typing information for the output type of the function can be specified in this textbox. formatting for the typing is the same as that for inputs.</p><h2>Conditions<a name="4"></a></h2><p>Text input for a condition box must be valid embedded Matlab code. Expressions in condition boxes will be evaluated with the assumed type of boolean. Since embedded Matlab is not typechecked this is a potential cause of errors. By running a syntax check on a table, each expression in a condition box will be checked that it is of type boolean.</p><p>For a table with multiple outputs, the horizontal condition boxes represent different outputs, more detail about this in the following section.</p><h2>Outputs<a name="5"></a></h2><p>The outputs of the function are specified in the outputs grid. Outputs must be an expression that will evaluate to a definite value. Each output specified should be the same type, however since Matlab is not strongly typed, almost every possible value will be interpreted as a compatible type. The tool supports 2 output modes: single output and multiple output.</p><p>The output mode can be specified from the edit menu as seen in the following figure:</p><p><img vspace="5" hspace="5" src="ug_layout_4.png" alt=""> </p><p><b>Single Output</b></p><p>For a single output table, the vertical grid can be used for another dimension of conditions. Each output cell shall be a single expression which will evaluate to the output under the interpreted conditions.</p><p><b>Multiple Output</b></p><p>For a table with multiple outputs, the horizontal condition grid is used to specify the outputs of the table. The same rules for typing apply as noted in the inputs and expression section of this document.</p><p>Each cell in the condition grid specifies the name (and type) of an output. See the following figure for an example. Each cell in the output grid specifies an output that corresponds to the output specified in the horizontal grid above it.</p><p>In the example below the table has 2 different outputs labeled, output1 and output2; the outputs have different types. Multiple outputs facilitates robust function specification.</p><p><img vspace="5" hspace="5" src="ug_layout_5.png" alt=""> </p><h2>Ports<a name="6"></a></h2><p>The "Ports" button will bring up the ports and data manager window (see next figure.) From here you can specify the datatypes of signals, as well as any other functionality as you would with another Simulink block.</p><p><img vspace="5" hspace="5" src="ug_layout_6.png" alt=""> </p><h2>Edit Mode<a name="7"></a></h2><p>The edit button is a toggle button which allows for the user to hide the editing buttons which include the new row, delete row, new subgrid, etc. buttons. Hiding these buttons allows for cleaner looking table with fewer distractions allowing the user to concentrate on the content in the table. see an example below.</p><p><img vspace="5" hspace="5" src="ug_layout_7.png" alt=""> </p><p class="footer"><br>
       Published with MATLAB&reg; 7.10<br></p></div><!--
 ##### SOURCE BEGIN #####
 %% Editing a Tabular Expression
 %
-% The Tabular Expression Dialog allows users to graphically layout a
-% tabular expression, for which conditions and outputs can be filled in
-% using the embedded matlab subset of the Matlab languauge.
+% The Table Tool allows users to graphically layout a
+% tabular expression, for which conditions and outputs can be specified
+% using the embedded Matlab subset of the Matlab language.
 %% Layout
 % The Dialog interface allows for the creation of 1-Dimensional vertical
 % and horizontal tables, as well as 2-Dimensional tables. The tool supports
@@ -92,24 +92,24 @@ p.footer {
 % The input box labeled "Inputs" allows for the specification of inputs to
 % the table. There is no limit in the number of inputs supported. Inputs
 % are specified in a comma delimited list. names of inputs must conform to
-% the matlab syntax conventions.
+% the Matlab syntax conventions.
 %
 % *Typing*
 % 
-% typing information can be specified for each input declared. this allows
-% for users to input dependant types. The format for typing follows that of
+% Typing information can be specified for each input declared. This allows
+% for users to declare inputs as dependent types. The format for typing follows that of
 % PVS, some examples:
 %
 % * |x, y, z| - 3 inputs with the default type
 % * |x, y:bool| - 2 inputs, y with specified type, x has the default
 % type.
 % * |x:real, y:real, z:bool| - 2 inputs of type real and one of type bool
-% * |x:real, y:{t:real|t>x}| - 2 inputs of type real, y is dependant on x,
-% and is restricited to those value strictly greater than x
+% * |x:real, y:{t:real|t>x}| - 2 inputs of type real, y is dependent on x,
+% and is restricted to those value strictly greater than x
 %
 %% Expression Name
-% the expression name will be the name indentifying the block, it will also
-% be the function name for an generated matlab codes.
+% the expression name will be the name identifying the block, it will also
+% be the function name for generated Matlab code.
 %
 % *Typing*
 %
@@ -118,23 +118,23 @@ p.footer {
 % the same as that for inputs.
 % 
 %% Conditions
-% Text input for a condition box must be valid embedded matlab code.
-% Expressions in condition boxes will be evaulated with the assumed type of
-% boolean. Since embedded matlab is not typechecked this is a pottential
-% cause of errors. By running pvs on a table, each expression in a
+% Text input for a condition box must be valid embedded Matlab code.
+% Expressions in condition boxes will be evaluated with the assumed type of
+% boolean. Since embedded Matlab is not typechecked this is a potential
+% cause of errors. By running a syntax check on a table, each expression in a
 % condition box will be checked that it is of type boolean.
 %
 % For a table with multiple outputs, the horizontal condition boxes
-% represent different outputs, more detail about this in the output
+% represent different outputs, more detail about this in the following
 % section.
 %
 %% Outputs
-% The outputs of the function are specified in the Outputs grid. Outputs must be an expression that 
+% The outputs of the function are specified in the outputs grid. Outputs must be an expression that 
 % will evaluate to a definite value. Each output specified should be the same type, however since
-% matlab is not strongly typed, almost every possible value will be interpreted as a compatible type. 
+% Matlab is not strongly typed, almost every possible value will be interpreted as a compatible type. 
 % The tool supports 2 output modes: single output and multiple output.
 %
-% The output mode can be specifed from the edit menu as seen in the
+% The output mode can be specified from the edit menu as seen in the
 % following figure:
 %
 % <<ug_layout_4.png>>
@@ -142,32 +142,32 @@ p.footer {
 % *Single Output*
 %
 % For a single output table, the vertical grid can be used for another
-% dimension of conditons. Each output cell shall be a single expression
-% which will evaulate to the output under the interpreted conditions.
+% dimension of conditions. Each output cell shall be a single expression
+% which will evaluate to the output under the interpreted conditions.
 %
 % *Multiple Output*
 %
 % For a table with multiple outputs, the horizontal condition grid is used
 % to specify the outputs of the table. The same rules for typing apply as noted in the 
-% inputs and expression section of this documnet
+% inputs and expression section of this document.
 %
 % Each cell in the condition grid
 % specifies the name (and type) of an output. See the following figure for
 % an example. Each cell in the output grid specifies an output that
-% cooresponds to the output specified in the horizontal grid above it.
+% corresponds to the output specified in the horizontal grid above it.
 %
-% In the example bellow 
+% In the example below 
 % the table has 2
-% different outputs labeled, output1 and output2. the outputs have
-% different types, which allows for powerful function specification.
+% different outputs labeled, output1 and output2; the outputs have
+% different types. Multiple outputs facilitates robust function specification.
 %
 % <<ug_layout_5.png>>
 %
 %% Ports
 %
 % The "Ports" button will bring up the ports and data manager window (see
-% next figure.) From here you can define the datatypes of signals, as well
-% as anyother fuctionality as you would with another Simulink block.
+% next figure.) From here you can specify the datatypes of signals, as well
+% as any other functionality as you would with another Simulink block.
 %
 % <<ug_layout_6.png>>
 %
@@ -176,7 +176,7 @@ p.footer {
 % The edit button is a toggle button which allows for the user to hide the
 % editing buttons which include the new row, delete row, new subgrid, etc.
 % buttons. Hiding these buttons allows for cleaner looking table with fewer
-% distractions allowing the user to consentrate on the content in the
+% distractions allowing the user to concentrate on the content in the
 % table. see an example below.
 %
 % <<ug_layout_7.png>>