GITBOOK-72: tidying up workflow & UI

Author: juney-lee

gitbook/manual/fitting.md

@@ -17,3 +17,7 @@ A `ThrustDiagram` is represented by the mesh datastructure. 
 Once the Form and Force Diagrams have been created and horizontal equilibrium has been established through parallelisation, the distribution of horizontal forces in the system is fixed. The actual magnitude of the horizontal forces depends on a _scale factor_ and will determine the _target height_ of the final thrust diagram. A higher scale factor results in higher horizontal forces and therefore a shallower three-dimensional shape. Vice versa, a lower scale factor results in lower horizontal thrust and thus a deeper solution.
 
 The meaning of the scale factor and the magnitude of horizontal forces is related to the magnitude of the loads, which in turn are related to the self-weight of the resulting three-dimensional geometry. Rather than asking you to "guess" the scale factor to get the three-dimensional shape you want, RhinoVAULT will determine the scale for you based on the desired height of the final solution. The default value for the target height is 25% of the length of the diagonal of the bounding box of the Form Diagram (essentially of the bounding box of the footprint of your shell). This value tends to produce well-proportioned geometries.
+
+
+
+note on max heigh

gitbook/manual/user-interface.md

@@ -18,7 +18,7 @@ The workflow of RhinoVAULT is based on the theoretical framework and workflow of
 {% step %}
 ### 1. Create and Modify Pattern
 
-A `Pattern` describes the topology of the `formdiagram`. A `pattern` is a collection of vertices interconnected by lines or "edges".  RhinoVAULT provides several methods for generating a `Pattern` and various mechanisms to modify and refine its geometry.
+A `Pattern` describes the topology of the `FormDiagram`. A `Pattern` is a collection of vertices interconnected by lines or "edges".  RhinoVAULT provides several methods for generating a `Pattern` and various mechanisms to modify and refine its geometry.
 {% endstep %}
 
 {% step %}
@@ -30,33 +30,33 @@ In this step, additional information is added to the `Pattern`, such as identifi
 {% step %}
 ### Create Form Diagram
 
-Once the support vertices have been defined and the boundaries have been properly modified, the `FormDiagram` can be created from the `pattern`.
+Once the support vertices have been defined and the boundaries have been properly modified, the `FormDiagram` can be created from the `Pattern`.
 {% endstep %}
 
 {% step %}
 ### Create Force Diagram
 
-Once the `FormDiagram` has been successfully created, the `ForceDiagram` can be created. In its initial state, the `ForceDiagram` is the topological dual of the `FormDiagram`; the two diagrams are not yet reciprocal.  
+Once the `FormDiagram` has been successfully created, the `ForceDiagram` can be created. In its initial state, the `ForceDiagram` is the topological dual of the `FormDiagram`; the two diagrams are not yet reciprocal (in horizontal equilibrium).  
 {% endstep %}
 
 {% step %}
 ### Horizontal Equilibrium
 
-In order for the `FormDiagram` and the `ForceDiagram` to be reciprocal, the edges of one diagram needs to be perpendicular to the corresponding edge in the other diagram. Horizontal equilibrium solver iteratively repositions the vertices of the `FormDiagram` and/or `ForceDiagram` until the perpendicularity criteria (within desired angle tolerance) is met.
+In order for the `FormDiagram` and the `ForceDiagram` to be reciprocal, the edges of one diagram needs to be perpendicular to the corresponding edge in the other diagram. `RV_tna_horizontal` iteratively repositions the vertices of the `FormDiagram` and/or `ForceDiagram` until the perpendicularity criteria (within desired angle tolerance) is met.
 {% endstep %}
 
 {% step %}
 ### Vertical Equilibrium
 
-Once the `FormDiagram` and `ForceDiagram` are reciprocal (in other words, in horizontal equilibrium), the geometry of the `ThrustDiagram` can be computed. The `ThrustDiagram` is equivalent to the `FormDiagram` with the updated z coordinates of its vertices (therefore updated self-weight at each vertex). 
+Once the `FormDiagram` and `ForceDiagram` are reciprocal, the geometry of the `ThrustDiagram` can be computed. The `ThrustDiagram` is equivalent to the `FormDiagram` with the updated z coordinates of its vertices (therefore updated self-weight at each vertex). 
 
-Given a desired target height of the eventual `ThrustDiagram`, vertical equilibrium solver iteratively re-scales the `ThrustDiagram` in the z-axis, until the highest vertex of the `ThrustDigram` lies at the desired target height.
+Given a desired target height, `RV_tna_vertical` iteratively re-scales the `ThrustDiagram` in the z-axis, until the highest vertex of the `ThrustDigram` lies at the desired target height.
 {% endstep %}
 
 {% step %}
 ### Modify Diagrams
 
-Once the vertical equilibrium has been computed, the three diagrams can be interactively modified by the user to continue form finding explorations.
+Once the vertical equilibrium has been computed, the three diagrams can be interactively modified by the user to continue form-finding explorations.
 {% endstep %}
 
 {% step %}
@@ -81,9 +81,9 @@ There are two ways of accessing the functions and features of RhinoVAULT:
 * Using the Rhino command lines
 * RhionVAULT toolbar
 
-### Command
+### Rhino command line
 
-COMPAS RhinoVAULT includes the following Rhino commands:
+RhinoVAULT includes the following Rhino commands, which can be executed from the Rhino Command Prompt (simply start typing the command name).
 
 * `RV`
 * `RV_pattern`
@@ -106,12 +106,10 @@ COMPAS RhinoVAULT includes the following Rhino commands:
 * `RV_session_save`
 * `RV_settings`
 
-These commands can be executed at the Rhino Command Prompt (simply start typing the command name), or using the RhinoVAULT toolbar.
-
 <figure><img src="../.gitbook/assets/RV_command-line.png" alt=""><figcaption><p>Accessing RhinoVAULT commands from the command line.</p></figcaption></figure>
 
 ### Toolbar
 
-The RhinoVAULT toolbar is organized in the sequential order (0, 1, 2, 3... 9, from left to right) of the steps of the [RhinoVAULT workflow](user-interface.md#rhinovault-workflow). The RhinoVAULT toolbar gives the user a quick access to all the key features of RV2.
+All of the functionalities of RhinoVAULT are accessible through the toolbar. The toolbar is organized in the sequential order (0, 1, 2, 3... to 9 from left to right) of the steps of the [RhinoVAULT workflow](user-interface.md#rhinovault-workflow).&#x20;
 
-<figure><img src="../.gitbook/assets/RV_toolbar-numbered.jpg" alt=""><figcaption><p>RhinoVAULT toolbar</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/RV_toolbar-numbered.jpg" alt=""><figcaption><p>The arrangement of the RhinoVAULT toolbar according to the TNA workflow.</p></figcaption></figure>