1 files changed, 7 insertions, 4 deletions

diff --git a/how_to_organize_your_lua_project.html b/how_to_organize_your_lua_project.html
index 013f712..63d952d 100644
--- a/how_to_organize_your_lua_project.html
+++ b/how_to_organize_your_lua_project.html
@@ -3,20 +3,23 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <meta name="author" content="aki">
-<meta name="tags" content="tutorial, structuring, organizing, lua, project, howto">
+<meta name="tags" content="tutorial, structure, organizing, lua, project, howto, guide">
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" href="style.css">
 
-<title>How To Organize Your Lua Project</title>
+<title>How to Organize Your Lua Project</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>How To Organize Your Lua Project</h1>
-<p class="subtitle">Published on 2021-01-07 15:45:00+01:00
+<h1>How to Organize Your Lua Project</h1>
+<p class="subtitle">Published on 2021-01-07 15:45:00+01:00, last modified on 2021-08-07 14:07:00+02:00
 <p>From time to time I hear complaints about how Lua handles modules. Here and there I see and even answer myself
 questions regarding <code>require</code> and adjusting the paths in <code>package</code> to allow some desired
 behaviour, with the most prominent issue of relative imports that always work.
+<p>This is a quite interesting and wide topic. In this article let's focus on the basics - organizing a simple project,
+putting it in a development environment, and preparing for the target environment by creating a known and absolute
+structure of requiring the modules, hopefully avoiding usually encountered problems entirely.
 <p>Before we hop into the explanation of how to organize files in your Lua projects, let's talk about default importing
 mechanism in Lua: <a href="https://www.lua.org/manual/5.4/manual.html#pdf-require"><code>require</code></a>.</p>