Updated to CL 22627414:

* docs updates
* authoring fixes
* stress solver crash fixes

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/api_docs/files/pageintroduction.html b/docs/api_docs/files/pageintroduction.html
index 9016338..e38a444 100644
--- a/docs/api_docs/files/pageintroduction.html
+++ b/docs/api_docs/files/pageintroduction.html
@@ -28,7 +28,7 @@ The static data associated with a destructible is stored in an <em>asset</em>. A
 Chunks are defined hierarchically, so that when a chunk is fractured its child chunks are created. The user may tag any chunk in this hierarchy as a <em>support</em> chunk. This is covered in more detail in the <a class="el" href="pageintroduction.html#support_model">Support Model</a> section. The user also supplies a description of the connections between support chunks. A <em>bond</em> represents the surface joining neighboring chunks. A bond is represented by a surface centroid, an average surface normal, and the surface area. These quantities don't need to be exact for Blast&trade; to operate effectively.<p>
 Multiple chunk hierarchies may exist in a single asset. The <em>root chunks</em> (see <a class="el" href="pagedefinitions.html">Definitions</a>) will be visible when the asset is initially instanced. Subsequent fracturing has the effect of breaking the root chunks into their hierarchical descendants.<h2><a class="anchor" name="support_model">
 Support Model</a></h2>
-Blast&trade; requires that support chunks form an <em>exact cover</em> (see the definition of exact coverage in <a class="el" href="pagedefinitions.html">Definitions</a>). The geometric interpretation of exact coverage is that the support chunks fill the space of the root (unfractured) chunk, without any volume being covered by more than one chunk. A helper function are provided to modify a set of chunk descriptors so that they have exact coverage. This function fills in missing coverage by assigning support to chunks at the highest place possible (closest to root) in the hierarchy, and redundant support is removed: if a chunk and one of its descendant chunks are both marked as support, the function will remove support from the descendant chunk.<p>
+Blast&trade; requires that support chunks form an <em>exact cover</em> (see the definition of exact coverage in <a class="el" href="pagedefinitions.html">Definitions</a>). The geometric interpretation of exact coverage is that the support chunks fill the space of the root (unfractured) chunk, without any volume being covered by more than one chunk. A helper function is provided to modify a set of chunk descriptors so that they have exact coverage. This function fills in missing coverage by assigning support to chunks at the highest place possible (closest to root) in the hierarchy, and redundant support is removed: if a chunk and one of its descendant chunks are both marked as support, the function will remove support from the descendant chunk.<p>
 Support chunks that are joined by bonds will be grouped together in the same actor when fracturing occurs. Bonds may be defined between any two support chunks, or between a support chunk and "the world." There is no corresponding "world chunk," but the bond represents a connection between the chunk and its external environment. All chunks with a support graph connected to the world will be put into the same actor. An expected use case is to make this actor static (or kinematic). Actors may be queried to determine if they are "world-bound."<p>
 In order to take advantage of the chunk hieararchy to reduce the number of chunks which represent an actor physically and graphically, Blast&trade; calculates a list of <em>visible chunks</em> from the support chunks in an actor. These may be the support chunks, or they may be ancestors of support chunks if all descendant support chunks are in the actor.<p>
 Support chunks do not have to be leaves in the chunk hierarchy, nor do they have to be at the same depth in the hierarchy. Children of support chunks will always be the sole chunk in their actor, since there are no bonds defined between them. If an actor consists of a <em>subsupport chunk</em> (see <a class="el" href="pagedefinitions.html">Definitions</a>), the visible chunk is the same chunk. The same is true if an actor consists of a <em>single</em> support chunk.<h2><a class="anchor" name="damage_model">