Fixing some more errors

1 files changed, 2 insertions, 2 deletions

diff --git a/posts/awk-with-kakoune.njk b/posts/awk-with-kakoune.njk
index 82428c6..ea854e1 100644
--- a/posts/awk-with-kakoune.njk
+++ b/posts/awk-with-kakoune.njk
@@ -21,9 +21,9 @@ class="sourceCode ocaml"><code class="sourceCode ocaml"><span id="cb1-1"><a href
 <span id="cb1-6"><a href="#cb1-6" aria-hidden="true" tabindex="-1"></a>      FROM users</span>
 <span id="cb1-7"><a href="#cb1-7" aria-hidden="true" tabindex="-1"></a>      WHERE username &lt;&gt; %<span class="dt">string</span>{wrong_user} AND id &gt; %<span class="dt">int</span>{min_id}</span>
 <span id="cb1-8"><a href="#cb1-8" aria-hidden="true" tabindex="-1"></a>      |sql}]</span></code></pre></div>
-<p><code>my_query</code> becomes a function that takes an
+<p><code>my_query</code> becomes a function that takes <code>string</code>,
 <code>int</code> and <code>sql_connection</code> and returns an n-tuple,
-<code>(int,string,bool,string)</code>. This can be hard to work with, especially a larger query can return many values of the same type and it becomes easy to mix them up. If you have a record type defined
+<code>(int,string,bool,string)</code>. Tuples can be hard to work with, especially a larger query can return many values of the same type, it becomes easy to mix them up. If you have a record type defined
 that looks exactly the same as the return type of the SQL statement, you
 can therefore add a <code>record_out</code> statement, which ppx_rapper will handle and 
 automatically return a record that matches its structure instead of a tuple:</p>