Minor updates to tutorials

7 files changed, 27 insertions, 22 deletions

diff --git a/how_to_archive_with_posix_ar.html b/how_to_archive_with_posix_ar.html
index 77dd77c..8f39a1d 100644
--- a/how_to_archive_with_posix_ar.html
+++ b/how_to_archive_with_posix_ar.html
@@ -7,12 +7,12 @@
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" href="style.css">
 
-<title>How To Archive With POSIX ar</title>
+<title>How to Archive With POSIX ar</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>How To Archive With POSIX ar</h1>
+<h1>How to Archive With POSIX ar</h1>
 <p class="subtitle">Published on 2021-07-26 00:47:00+02:00, last modified on 2021-07-26 17:09:00+02:00
 <p>Let's continue <a href="how_to_archive_with_posix_tar_cpio_and_pax.html">last POSIX archiving guide</a> from the
 very spot we finished. Today, we'll deal with just one tool. Very peculiar one, because it's more of a development
diff --git a/how_to_archive_with_posix_tar_cpio_and_pax.html b/how_to_archive_with_posix_tar_cpio_and_pax.html
index cd53a4b..28c3878 100644
--- a/how_to_archive_with_posix_tar_cpio_and_pax.html
+++ b/how_to_archive_with_posix_tar_cpio_and_pax.html
@@ -7,12 +7,12 @@
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>How To Archive With POSIX tar, cpio and pax</title>
+<title>How to Archive With POSIX tar, cpio and pax</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>How To Archive With POSIX tar, cpio and pax</h1>
+<h1>How to Archive With POSIX tar, cpio and pax</h1>
 <p class="subtitle">Published on 2020-07-22 22:30:00+02:00, last modified on 2021-08-11 21:35:00+02:00
 <p>The usual answer to archive anything is <a href="https://www.gnu.org/software/tar/">tar</a>. As you may see I
 intentionally linked to the GNU Tar. If you are a *BSD user then you use some other implementation. Both of them follow
diff --git a/how_to_create_templates_with_shell_cat_and_envsubst.html b/how_to_create_templates_with_shell_cat_and_envsubst.html
index 99a9c7c..97866e2 100644
--- a/how_to_create_templates_with_shell_cat_and_envsubst.html
+++ b/how_to_create_templates_with_shell_cat_and_envsubst.html
@@ -7,12 +7,12 @@
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>How To Create Templates With Shell, cat and envsubst</title>
+<title>How to Create Templates With Shell, cat and envsubst</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>How To Create Templates With Shell, cat and envsubst</h1>
+<h1>How to Create Templates With Shell, cat and envsubst</h1>
 <p class="subtitle">Published on 2020-07-14 20:26:00+02:00
 <p>Now something trivial and fun. Creating templates of documents or configurations in shell. There are two reasons why
 I considered doing that instead of using some more verbose utilities. First off, availability - I have POSIX compliant
diff --git a/how_to_flash_lolin_nodemcu_v3.html b/how_to_flash_lolin_nodemcu_v3.html
index 39760d0..0d4d802 100644
--- a/how_to_flash_lolin_nodemcu_v3.html
+++ b/how_to_flash_lolin_nodemcu_v3.html
@@ -6,12 +6,12 @@
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>How To Flash LOLin NodeMCU v3</title>
+<title>How to Flash LOLin NodeMCU v3</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>How To Flash LOLin NodeMCU v3</h1>
+<h1>How to Flash LOLin NodeMCU v3</h1>
 <p class="subtitle">Published on 2020-06-29 17:58:00+02:00
 <p>Republishing old content. This is from when I bought and flashed my first NodeMCU clone (perhaps "loose
 implementation"?) of NodeMCU v3 called LOLin v3.
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>
 
diff --git a/how_to_write_a_minimal_html5_document.html b/how_to_write_a_minimal_html5_document.html
index 6a70c3b..641c2fc 100644
--- a/how_to_write_a_minimal_html5_document.html
+++ b/how_to_write_a_minimal_html5_document.html
@@ -7,12 +7,12 @@
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>How To Write a Minimal HTML5 Document</title>
+<title>How to Write a Minimal HTML5 Document</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>How To Write a Minimal HTML5 Document</h1>
+<h1>How to Write a Minimal HTML5 Document</h1>
 <p class="subtitle">Published on 2020-08-03 18:18:00+02:00
 <p>Yes, I know how it sounds to have both "HTML" and "minimal" in one sentence. I think it's possible to accomplish
 that and I'll show you how. Before we start, let's set some rules:</p>
diff --git a/index.html b/index.html
index 1e15407..8d68b41 100644
--- a/index.html
+++ b/index.html
@@ -45,11 +45,11 @@ completely discard the concept of a keyboard.
 <li>Guides that I keep rewriting
 	<ul>
 		<li><a href="dear_imgui_and_love.html">Dear ImGui and LÖVE,</a>
-		<li><a href="how_to_archive_with_posix_ar.html">How To Archive With POSIX ar</a>
-		<li><a href="how_to_archive_with_posix_tar_cpio_and_pax.html">How To Archive With POSIX tar, cpio and pax</a>
-		<li><a href="how_to_create_templates_with_shell_cat_and_envsubst.html">How To Create Templates With Shell, cat and envsubst</a>
-		<li><a href="how_to_flash_lolin_nodemcu_v3.html">How To Flash LOLin NodeMCU v3</a>
-		<li><a href="how_to_organize_your_lua_project.html">How To Organize Your Lua Project</a>
+		<li><a href="how_to_archive_with_posix_ar.html">How to Archive With POSIX ar</a>
+		<li><a href="how_to_archive_with_posix_tar_cpio_and_pax.html">How to Archive With POSIX tar, cpio and pax</a>
+		<li><a href="how_to_create_templates_with_shell_cat_and_envsubst.html">How to Create Templates With Shell, cat and envsubst</a>
+		<li><a href="how_to_flash_lolin_nodemcu_v3.html">How to Flash LOLin NodeMCU v3</a>
+		<li><a href="how_to_organize_your_lua_project.html">How to Organize Your Lua Project</a>
 		<li><a href="how_to_write_a_minimal_html5_document.html">How to Write a Minimal HTML5 Document</a>
 		<li><a href="journey_home_application_deployment.html">Journey /home - Application Deployment</a>
 		<li><a href="the_gentlest_introduction_to_building_with_makefiles.html">The Gentlest Introduction to Building With Makefiles</a>
@@ -65,14 +65,16 @@ completely discard the concept of a keyboard.
 </nav>
 <section id="news">
 <h2>Short Updates</h2>
+<p><strong><time>2021-08-14</time></strong>
+Minor updates to tutorials including a new paragraph in <a href="how_to_organize_your_lua_project.html">Lua Project</a>.
 <p><strong><time>2021-08-11</time></strong>
-Minor updates to <a href="how_to_archive_with_posix_tar_cpio_and_pax.html">How To Archive With POSIX tar, cpio and pax</a>.
+Minor updates to <a href="how_to_archive_with_posix_tar_cpio_and_pax.html">How to Archive With POSIX tar, cpio and pax</a>.
 <p><strong><time>2021-07-26</time></strong>
 Once again restructured index hierarchy.
 <p><strong><time>2021-07-26</time></strong>
-Published <a href="how_to_archive_with_posix_ar.html">How To Archive With POSIX ar</a>.
+Published <a href="how_to_archive_with_posix_ar.html">How to Archive With POSIX ar</a>.
 <p><strong><time>2021-07-25</time></strong>
-Renamed most of the guides to include "How To" in their name to make them more visible. I'm thinking about doing another
+Renamed most of the guides to include "How to" in their name to make them more visible. I'm thinking about doing another
 round of website restructurization.
 <p><strong><time>2021-07-25</time></strong>
 Published <a href="deconstructing_web_browsers.html">Deconstructing Web Browsers<a>, summary of now-removed <i>Plumbing