fix: update the tutorial to work with the latest Lux changes

Author: vhyrro

docs/tutorial/03-creating-a-project.md

@@ -4,7 +4,7 @@ title: Creating a Project
 ---
 
 In the next chapters we will learn how to create, manage and publish a small Lua CLI
-that checks whether the entered words contain "hello" or not.
+that checks whether a sentence provided to the program contains the string "hello".
 We will cover dependencies, the `lux.toml` format and more all the way up to API keys!
 
 To start writing Lua, we must initialize a project where we will store our code.
@@ -44,26 +44,35 @@ can be safely ignored.
 You'll see that our `my-lua-project/` directory was created. Let's enter the directory
 and get to work!
 
-Inside of our project, you should see that a single file was generated:
+Inside of our project, you should see that a basic project skeleton was created:
 
 ```bash title="tree $(pwd)"
 /home/your-username/my-lua-project
-└── lux.toml
+├── lux.toml
+└── src
+    └── main.lua
 ```
 
 The `lux.toml` file describes instructions on how to build and ship your Lua code.
 Let's enter the file. You should see contents similar to the following:
 
-```lua title="lux.toml"
+```toml title="lux.toml"
 package = "my-lua-project"
 version = "0.1.0"
-lua = ">= 5.1"
+lua = ">=5.1"
 
 [description]
 summary = "A sample project."
 maintainer = "vhyrro"
+labels = [ "learning" ]
 license = "MIT"
-labels = ["learning"]
+
+[dependencies]
+# Add your dependencies here
+# `busted = ">=2.0"`
+
+[run]
+args = [ "src/main.lua" ]
 
 [build]
 type = "builtin"

docs/tutorial/04-adding-dependencies.md

@@ -19,7 +19,7 @@ This may take a while depending on your internet connection!
 
 ## Testing Our Changes
 
-To check whether `argparse` is loaded we can enter a Lua REPL and play around
+To check whether `argparse` is loaded, we can enter a Lua REPL and play around
 with our code. However, just running `lua` will not work. To enter a
 `lua` REPL with our dependencies loaded, we need to run the following command instead:
 

docs/tutorial/05-making-the-application.md

@@ -3,25 +3,10 @@ id: making-the-application
 title: Making the CLI Application
 ---
 
-Lux expects to find code under either a `src/` or `lua/` directory.
-For this series, we'll store our code under `src/`.
+## Creating the Skeleton
 
-Inside the project directory (where your `lux.toml` resides) create a `src/main.lua` file.
-This acts as the main file Lux will execute.
-
-Here's what your project directory should look like after creating the file:
-```sh title="tree ."
-.
-├── lux.toml
-└── src
-    └── main.lua
-
-2 directories, 2 files
-```
-
-## Ensuring the Project Runs
-
-Let us add the following boilerplate code to `src/main.lua`:
+Let's add some simple boilerplate using `argparse`. This program will print back anything
+we pass as arguments back into the console:
 
 ```lua title="src/main.lua"
 local argparse = require("argparse")
@@ -36,10 +21,10 @@ local args = parser:parse()
 print(args.input)
 ```
 
-We're now ready to see if our code works! Run the following command to see your code in action:
+Run the following command to see your code in action:
 
 ```sh
-lux run "Testing our code!"
+lx run "Testing our code!"
 ```
 
 You should see `Testing our code!` printed right back at you in the console!

docs/tutorial/06-testing.md

@@ -52,6 +52,8 @@ else
 end
 ```
 
+Noticed how we replaced the function with a `require` call to the new file.
+
 ## Writing our First Test
 
 Now that we have our code structured, let's write our first test. Tests are usually stored in
@@ -81,7 +83,7 @@ end)
 ## Running the Tests
 
 We're now ready to run our tests! `lx test` will run all the tests in your
-project. After the automatic installation of `busted` you should see the following output:
+project. After taking a moment to install `busted`, Lux should show you the following output:
 
 ```sh title="lx test"
 ●●