diff --git a/docs/courses/level-one/chapter-2.md b/docs/courses/level-one/chapter-2.md
index 5f079bcbd..9d5e5737f 100644
--- a/docs/courses/level-one/chapter-2.md
+++ b/docs/courses/level-one/chapter-2.md
@@ -6,119 +6,147 @@ contentType: tutorial
In this lesson, you will build a small workflow that gets 10 articles about automation from Hacker News. The workflow consists of four steps:
-[1. Add the Hacker News node](#1-add-the-hacker-news-node)
-[2. Configure the Hacker News node](#2-configure-the-hacker-news-node)
-[3. Save the workflow](#3-save-the-workflow)
-[4. Execute the node](#4-execute-the-node)
+1. [Add the Hacker News node](#1-add-the-hacker-news-node)
+2. [Configure the Hacker News node](#2-configure-the-hacker-news-node)
+3. [Execute the node](#3-execute-the-node)
+4. [Save the workflow](#4-save-the-workflow)
## 1. Add the Hacker News node
-Open the nodes panel, search for the *Hacker News* node, and click on it to add it to the Editor UI. Connect the *Hacker News node* to the *Manual Trigger node*.
+Open the nodes panel (reminder: you can open this by selecting the **+** icon in the top right corner of the canvas or selecting Tab on your keyboard).
+
+Then:
+
+1. Search for the **Hacker News** node.
+2. Click on it when it appears in the search.
+3. In the **Actions** section, select **Get many items**.
+
+/// note | Adding a node without an explicit trigger
+Adding the node this way sets it up to use a manual trigger for "When clicking 'Test workflow'." This will work for our purposes and can be a good way to test nodes.
+
+In a real-world scenario, you would likely want to set up a schedule or some other trigger to run the workflow.
+///
+
+The node is added to your canvas and the node window opens to display its configuration details.
## 2. Configure the Hacker News node
-When you add a new node to the Editor UI, the node will be automatically activated and open a window with two tabs on the left side: ***Parameters*** and ***Settings***.
+When you add a new node to the Editor UI, the node is automatically activated. The node details will open in a window with several options:
+
+- **Parameters**: Adjust parameters to refine and control the node's functionality.
+- **Docs**: Open the n8n documentation on this node type in a new window.
+- **Settings** (gear cog icon): Adjust settings to control the node's design and executions.
/// note | Parameters vs Settings
-*Parameters* are different for each node, depending on its functionality.
-*Settings* are the same for all nodes.
+**Parameters** are different for each node, depending on its functionality.
+**Settings** are the same for all nodes.
///
### Parameters
-The *Hacker News node* has several parameters that need to be configured in order to make it work:
+We need to configure several parameters for the **Hacker News node** to make it work:
-- *Resource:* All
+- **Resource**: All
This resource selects all data records (articles).
-- *Operation:* Get Many
+- **Operation**: Get Many
This operation fetches all the selected articles.
-- *Limit:* 10
+- **Limit**: 10
This parameter sets a limit to how many results are returned by the Get Many operation.
-- *Additional fields > Add Field > Keyword:* automation
-Additional fields are options that you can add to certain nodes to make your request more specific or filter the results. In our case, we want to get only articles that include the keyword “automation.”
+- **Additional Fields > Add Field > Keyword**: automation
+Additional fields are options that you can add to certain nodes to make your request more specific or filter the results. In our case, we want to get only articles that include the keyword "automation."
-The configuration of the parameters for the *Hacker News node* should now look like this:
+The configuration of the parameters for the **Hacker News node** should now look like this:
Hacker News node parameters
### Settings
-The *Settings* section includes several options for node design and executions. In this case, we'll configure only the first two settings, which set the node's appearance in the Editor UI. In the *Hacker News node* settings, edit:
+The **Settings** section includes several options for node design and executions. In this case, we'll configure only the final two settings, which set the node's appearance in the Editor UI's canvas.
-- *Notes:* Get the 10 latest articles
+In the **Hacker News node** Settings, edit:
+
+- **Notes**: Get the 10 latest articles.
/// note | Node notes
It's often helpful, especially for complex or shared workflows, to add a short description in the node about what it does.
///
-- *Display note in flow?:* toggle to true
-This option will display the description note under the node in the Editor UI.
+- **Display note in flow?**: toggle to true
+This option will display the Note under the node in the canvas.
-The configuration of the settings for the *Hacker News node* looks like this:
+The configuration of the settings for the **Hacker News node** should now look like this:
-Hacker News node renaming
+Hacker News node settings
/// note | Renaming a node
You can rename the node with a name that's more descriptive for your use case. There are two ways to do this:
- Select the node you want to rename and at the same time press the F2 key on your keyboard.
-- Double-click on the node to open the node window. Click on the name of the node in the top left corner of the window, rename it as you like, then click *Rename* to save the node under the new name.
+- Double-click on the node to open the node window. Click on the name of the node in the top left corner of the window, rename it as you like, then click **Rename** to save the node under the new name.
Renaming a node from the keyboard
///
+## 3. Execute the node
-## 3. Save the workflow
-
-Save the workflow under the name “Hacker News workflow”
-By default, your workflow is automatically saved as “My workflow.”
-
-There are two ways in which you can save a workflow:
-
-- From the Canvas in Editor UI, click **Ctrl + S** or **Cmd + S** on your keyboard
-- Click the **Save** button in the top right corner of the Editor UI. You may need to leave the node editor first by clicking outside the dialog.
-
-## 4. Execute the node
-
-Click on the *Execute Node* button in the top right corner of the node window. You should see 10 results in *Table* view.
+Select the **Test step** button in the node details window. You should see 10 results in the Output **Table** view.
+
Results in Table view for the Hacker News node
-## Node executions
+### Node executions
/// note | Node execution
A node execution represents a run of that node to retrieve the specified data.
///
-If a node is executed successfully a small green checkmark appear on top of the node.
+If a node executes successfully, a small green checkmark appears on top of the node in the canvas
Successfully executed workflow
-If the parameters are configured correctly and everything works fine, the requested data will be displayed in the node window in *Table*, *JSON* and *Schema* format. You can switch between these views by selecting the one you want from the *JSON|Table|Schema* button at the top of the node window.
+If the parameters are configured correctly and everything works fine, the requested data displays in the node window in **Table**, **JSON**, and **Schema** format. You can switch between these views by selecting the one you want from the **JSON|Table|Schema** button at the top of the node window.
/// note | Table vs JSON views
-The *Table* view is the default. It displays the requested data in a table, where the rows are the records and the columns are the available attributes of those records.
+The **Table** view is the default. It displays the requested data in a table, where the rows are the records and the columns are the available attributes of those records.
///
Results in JSON view for the Hacker News node
The node window displays more information about the node execution:
-- In the top left corner of the output window, you'll notice another piece of information: **10 items**.
-This field displays the number of items (records) that are returned by the node request. In our case, it's expected to be 10, since this is the limit we set in the node. But if you don't set a limit, it's useful to see how many records are actually returned.
-- Next to the *Items* information, notice a small grey *i* icon. If you hover on it, you'll get two more pieces of information: ***Start Time*** (when the node execution started) and ***Execution Time*** (how long it took for the node to return the results from the moment it started executing).
-*Start Time* and *Execution Time* can provide insights into the performance of each individual node.
-- Under the node name beside the **Parameters** tab, there is a link to the node's **Docs**. Check it out if you run into trouble or aren't sure how to configure the node's parameters.
+- Next to the **Output** title, notice a small icon (this will be a green checkmark if the node executed successfully). If you hover on it, you'll get two more pieces of information that can provide insights into the performance of each individual node in a workflow:
+ - **Start Time**: When the node execution started
+ - **Execution Time**: How long it took for the node to return the results from the moment it started executing
+- Just below the **Output** title, you'll notice another piece of information: **10 items**.
+This field displays the number of items (records) that the node request returned. In our case, it's expected to be 10, since this is the limit we set in step 2. But if you don't set a limit, it's useful to see how many records are actually returned.
/// warning | Error in nodes
-A red warning icon on a node means that the node has errors. This might happen if the node credentials are missing or incorrect, or the node parameters aren't configured correctly.
+A red warning icon on a node means that the node has errors. This might happen if the node credentials are missing or incorrect or the node parameters aren't configured correctly.
///
Error in nodes
+## 4. Save the workflow
+
+Once you're finished editing the node, select **Back to canvas** to return to the main canvas.
+
+By default, your workflow is automatically saved as "My workflow."
+
+For this lesson, let's rename the workflow to be "Hacker News workflow."
+
+/// note | Reminder
+You can rename a workflow by clicking on the workflow's name at the top of the Editor UI.
+///
+
+Once you've renamed the workflow, be sure to save it.
+
+There are two ways in which you can save a workflow:
+
+- From the Canvas in Editor UI, click **Ctrl + S** or **Cmd + S** on your keyboard.
+- Click the **Save** button in the top right corner of the Editor UI. You may need to leave the node editor first by clicking outside the dialog.
## Summary
Congratulations, you just built your first workflow! In this lesson, you learned how to use actions in app nodes, configure their parameters and settings, and save and execute your workflow.
-In the next lesson you will be introduced to your client, Nathan, who needs to automate his sales reporting work. You will build a more complex workflow for his use case, helping him become more productive at work.
+In the next lesson, we'll introduce you to your client, Nathan, who needs to automate his sales reporting work. You will build a more complex workflow for his use case, helping him become more productive at work.
