ZIP guide: regenerate HTML.

Signed-off-by: Daira Hopwood <daira@jacaranda.org>

zip-guide.html

@@ -68,7 +68,7 @@
                 </section>
             </section>
             <section id="comparison-of-zips-to-rfcs"><h3><span class="section-heading">Comparison of ZIPs to RFCs</span><span class="section-anchor"> <a rel="bookmark" href="#comparison-of-zips-to-rfcs"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h3>
-                <p>Like RFCs, ZIPs are precise technical documents that SHOULD give enough implementation to implement part of a Zcash-related protocol or follow a Zcash-related process.</p>
+                <p>Like RFCs, ZIPs are precise technical documents that SHOULD give enough implementation information to implement part of a Zcash-related protocol or follow a Zcash-related process.</p>
                 <p>ZIPs are different from RFCs in the following ways:</p>
                 <ul>
                     <li>Many (but not all) ZIPs are "living documents"; they are updated in-place as the relevant areas of the protocol or process change. Unlike in the RFC process, making a change in an area described by a published ZIP does not <em>necessarily</em> require creating a new ZIP, although that is an option if the change is extensive enough to warrant it.</li>