deploy: 91886d6

print.html

@@ -5512,7 +5512,7 @@ <h2 id="usage--differences-with-dynamic-fields"><a class="header" href="#usage--
 }
 </code></pre>
 <h2 id="pricing-differences"><a class="header" href="#pricing-differences">Pricing Differences</a></h2>
-<p>Dynamic Object Fields come a little more exensive than dynamic fields. Because of their internal
+<p>Dynamic Object Fields come a little more expensive than dynamic fields. Because of their internal
 structure, they require 2 objects: the Wrapper for Name and the Value. Because of this, the cost of
 adding and accessing object fields (loading 2 objects compared to 1 for dynamic fields) is higher.</p>
 <h2 id="next-steps-7"><a class="header" href="#next-steps-7">Next Steps</a></h2>

programmability/dynamic-object-fields.html

@@ -294,7 +294,7 @@ <h2 id="usage--differences-with-dynamic-fields"><a class="header" href="#usage--
 }
 </code></pre>
 <h2 id="pricing-differences"><a class="header" href="#pricing-differences">Pricing Differences</a></h2>
-<p>Dynamic Object Fields come a little more exensive than dynamic fields. Because of their internal
+<p>Dynamic Object Fields come a little more expensive than dynamic fields. Because of their internal
 structure, they require 2 objects: the Wrapper for Name and the Value. Because of this, the cost of
 adding and accessing object fields (loading 2 objects compared to 1 for dynamic fields) is higher.</p>
 <h2 id="next-steps"><a class="header" href="#next-steps">Next Steps</a></h2>

reference/functions.html

@@ -266,7 +266,7 @@ <h3 id="entry-modifier"><a class="header" href="#entry-modifier"><code>entry</co
 <p>In addition to <code>public</code> functions, you might have some functions in your modules that you want to
 use as the entry point to execution. The <code>entry</code> modifier is designed to allow module functions to
 initiate execution, without having to expose the functionality to other modules.</p>
-<p>Essentially, the combination of <code>pbulic</code> and <code>entry</code> functions define the &quot;main&quot; functions of a
+<p>Essentially, the combination of <code>public</code> and <code>entry</code> functions define the &quot;main&quot; functions of a
 module, and they specify where Move programs can start executing.</p>
 <p>Keep in mind though, an <code>entry</code> function <em>can</em> still be called by other Move functions. So while
 they <em>can</em> serve as the start of a Move program, they aren't restricted to that case.</p>

reference/print.html

@@ -2703,7 +2703,7 @@ <h3 id="entry-modifier"><a class="header" href="#entry-modifier"><code>entry</co
 <p>In addition to <code>public</code> functions, you might have some functions in your modules that you want to
 use as the entry point to execution. The <code>entry</code> modifier is designed to allow module functions to
 initiate execution, without having to expose the functionality to other modules.</p>
-<p>Essentially, the combination of <code>pbulic</code> and <code>entry</code> functions define the &quot;main&quot; functions of a
+<p>Essentially, the combination of <code>public</code> and <code>entry</code> functions define the &quot;main&quot; functions of a
 module, and they specify where Move programs can start executing.</p>
 <p>Keep in mind though, an <code>entry</code> function <em>can</em> still be called by other Move functions. So while
 they <em>can</em> serve as the start of a Move program, they aren't restricted to that case.</p>