--- a/ldpatch.html	Thu Nov 20 23:25:47 2014 -0500
+++ b/ldpatch.html	Thu Nov 20 23:37:50 2014 -0500
@@ -492,14 +492,13 @@
         <section id="bind-statement">
           <h2><dfn>Bind</dfn></h2>
           <p>
-              The <a>Bind</a> operation is used to create a new variable by assigning an RDF Term to the variable. The process results in a variable being bound to exactly one node. The scope of the bound variable is the entire LD Patch document: uses of a given variable name anywhere in an LD Patch document identifies the same variable, although variables can be overriden in subsequent <a>Bind</a> statements. Following the example above, the <a>Bind</a> operation creates a new variable called <code>event</code>, starting from the RDF Term <code>&lt;#&gt;</code> and following the path expression <code>/schema:performerIn[/schema:url = &lt;https://www.w3.org/2012/ldp/wiki/F2F5&gt;]</code> in order to identify the RDF Term to which this variable will be bound to – i.e. <code>_:b2</code>.
-          <pre class='example'>
-Bind ?event &lt;#&gt; /schema:performerIn[/schema:url = &lt;https://www.w3.org/2012/ldp/wiki/F2F5&gt;] .
-          </pre>
+              The <a>Bind</a> operation is used to bind an RDF Term to a variable. The process results in the variable being bound to exactly one node. After being bound, the variable can be used in the subsequent statements. Another <a>Bind</a> can override the value of a previously bound variable.
           </p>
+
           <p>
               The <a>Bind</a> operation is defined by three components: <a>Var</a>, <a>Value</a> and <a title="path expression">Path</a>, the last component being optional (can be considered equivalent to the empty path).
           </p>
+
           <p>
               <dfn>Var</dfn> contains a unique name for the new variable. Variables are prefixed by the "<code>?</code>" character, which is not part of the variable name.
           </p>
@@ -509,6 +508,14 @@
           <p>
               <dfn>Path</dfn> is the expression that is used to identify the RDF Term to which the Variable will be bound. It is comprised of <a>Step</a>(s) and/or <a>Constraint</a>(s).
           </p>
+
+          <p>
+              Following the example above, the <a>Bind</a> operation creates a new variable called <code>event</code>, starting from the RDF Term <code>&lt;#&gt;</code> and following the path expression <code>/schema:performerIn[/schema:url = &lt;https://www.w3.org/2012/ldp/wiki/F2F5&gt;]</code> in order to identify the RDF Term to which this variable will be bound to – i.e. <code>_:b2</code>.
+          <pre class='example'>
+Bind ?event &lt;#&gt; /schema:performerIn[/schema:url = &lt;https://www.w3.org/2012/ldp/wiki/F2F5&gt;] .
+          </pre>
+          </p>
+
         </section>
 
         <section id="add-statement">
@@ -548,7 +555,7 @@
         <section id="cut-statement">
           <h2><dfn>Cut</dfn></h2>
           <p>
-              The <a>Cut</a> operation is used to remove one or more triples from the <a>target graph</a> connected to a specific node (either an <a>IRI</a>, or a previously bound variable). The triples being removed correspond to the <a href="http://en.wikipedia.org/wiki/Connectivity_%28graph_theory%29">connected graph</a> whose nodes were accessible from the given node, as well as the triples having this node in the object position.
+              The <a>Cut</a> operation is used to remove one or more triples from the <a>target graph</a> connected to a specific node (either an <a>IRI</a>, or a previously bound variable). The triples being removed correspond to the <a href="http://en.wikipedia.org/wiki/Connectivity_%28graph_theory%29">connected graph</a> whose nodes were accessible from the given node, as well as the triples having this node in the object position. @@ TODO @@
           <pre class='example'>
 Cut ?workLocation .
           </pre>