diff --git a/docs/draft.html b/docs/draft.html
index 650970e..10cdc7d 100644
--- a/docs/draft.html
+++ b/docs/draft.html
@@ -802,7 +802,7 @@ <h3 data-number="1.5.1" id="lifetime-safety"><span class="header-section-number"
 two mainstream lifetime safety technologies: garbage collection and
 borrow checking. Garbage collection is simple to implement and use, but
 moves object allocations to the heap, making it incompatible with manual
-memory manegement. It keeps objects initialized as long as there are
+memory management. It keeps objects initialized as long as there are
 live references to them, making it incompatible with C++’s RAII<span class="citation" data-cites="raii">[<a href="https://en.wikipedia.org/wiki/Resource_acquisition_is_initialization" role="doc-biblioref">raii</a>]</span> object model.</p>
 <p>Borrow checking is an advanced form of live analysis. It keeps track
 of the <em>live references</em> at every point in the function, and
@@ -4754,7 +4754,7 @@ <h1 data-number="3" id="implementation-guidance"><span class="header-section-num
 and <code class="sourceCode cpp"><span class="op">-</span>print<span class="op">-</span>mir<span class="op">-</span>drop</code>
 cmdline options, which print the MIR before and after drop elaboration,
 respectively.</p>
-<p>Once there is a MIR representation with adequete coverage, begin work
+<p>Once there is a MIR representation with adequate coverage, begin work
 on the MIR analysis. Borrow checking is a very intricate algorithm, but
 fortunately it’s easy to interrogate. Print the MIR and the lifetime and
 outlives constraints as you lower and check functions to know where