Update README.md

Author: ChandimaJayaneththi

README.md

@@ -1,6 +1,6 @@
 # **Automated ESP32 Testing with GitHub Actions on Raspberry Pi**
 This tutorial demonstrates how to automate **ESP-IDF firmware testing** using **GitHub Actions** and a **Raspberry Pi** configured as a **self-hosted runner**.  
-An **ESP32-S3** board is physically connected to the Raspberry Pi via USB.
+An **ESP32-S3** board is physically connected to the Raspberry Pi via USB, which serves as the testing host.
 
 This tutorial continues from **[Stage 3 — VS Code Pytest Testing](https://github.com/ChandimaJayaneththi/esp32_hw_testing_series/blob/main/stage3_pytest_testing/README.md)**.  
 It uses the **same ESP-IDF project and test structure**, but instead of manually running the tests inside VS Code, everything is **automated using GitHub Actions**.  
@@ -38,6 +38,8 @@ It allows you to define workflows that automatically run tasks whenever specific
 
 This automation greatly improves productivity and reliability by catching bugs early — just like CI pipelines in large-scale software projects.
 
+Reference: [GitHub Actions](https://docs.github.com/en/actions)
+
 ---
 
 ## Setup
@@ -49,7 +51,7 @@ This automation greatly improves productivity and reliability by catching bugs e
     ```bash
     git clone https://github.com/ChandimaJayaneththi/esp32_github_actions_ci_rpi.git
     ```
-    Then, create your own GitHub repository (you can name it something like esp32_ci_rpi_runner) and push the cloned project into it
+    Next, create your own GitHub repository (for example, esp32_ci_rpi_runner) and push the cloned project into it
 
 2. **Ensure the Raspberry Pi has internet access and ESP-IDF installed with Pytest:**
 
@@ -170,7 +172,7 @@ jobs:
           . ~/esp/esp-idf/export.sh
           pytest pytest_esp32_test.py --port <PORT>
 ```
-**Note:** Replace "PORT" with the correct COM port the ESP32 is connected to. 
+**Note:** Replace "PORT" with the correct device (for example, /dev/ttyUSB0).
 
 ### Workflow Breakdown
  1. `name`:Defines the workflow’s display name in GitHub Actions
@@ -187,7 +189,7 @@ jobs:
 ---
 
 ## Running the CI Workflow
-1. Trigger the workflow ether commit and push your latest code or manually from the Actions tab.
+1. Trigger the workflow either commit and push your latest code or manually from the Actions tab.
 2. Go to your repository → Actions tab
     - You’ll see a workflow named "ESP-IDF CI on Raspberry Pi" automatically start.
 3. The workflow will:
@@ -199,7 +201,7 @@ jobs:
 
 ## Expected Output on GitHub Actions
 
-![GitHub action output](images/ci_results.png) 
+![GitHub action output](images/ci_results.png)
 
 You will see the following logs under `Run Unit tests` section
 ```log
@@ -274,7 +276,12 @@ This project was tested on:
 ---
 
 ## What You’ll Learn
-
+By the end of this tutorial, you will understand how to:
+- Set up a Raspberry Pi as a self-hosted GitHub Actions runner.
+- Configure ESP-IDF and Pytest to work seamlessly in an automated CI environment.
+- Use GitHub Actions to build, flash, and test ESP32 firmware automatically.
+- Run hardware-in-the-loop (HIL) testing directly from GitHub whenever new code is pushed.
+- Extend this setup for continuous testing and integration in embedded firmware projects.
 
 
 ---