From b3207111eae027fed8931dccb97b8457f58f6b6a Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Sun, 24 Aug 2025 04:41:55 +0000
Subject: [PATCH] docs: improve clarity and correct paths in README files

- Revised wording for better clarity in the English README related to CUDA API calls.
- Updated directory path in the Chinese README to reflect the correct location for building components.
---
 src/47-cuda-events/README.md | 2 +-
 src/48-energy/README.zh.md   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/47-cuda-events/README.md b/src/47-cuda-events/README.md
index 7a48add..3d7ef15 100644
--- a/src/47-cuda-events/README.md
+++ b/src/47-cuda-events/README.md
@@ -22,7 +22,7 @@ This is where eBPF comes to the rescue! By using uprobes, we can intercept CUDA
 - Error codes and failures
 - Timing of operations
 
-This blog is mainly focus on the CPU side of the CUDA API calls, for fined-grained tracing of GPU operations, you can see [eGPU](https://dl.acm.org/doi/10.1145/3723851.3726984) paper and [bpftime](https://github.com/eunomia-bpf/bpftime) project.
+This blog mainly focuses on the CPU side of the CUDA API calls, for fined-grained tracing of GPU operations, you can see [eGPU](https://dl.acm.org/doi/10.1145/3723851.3726984) paper and [bpftime](https://github.com/eunomia-bpf/bpftime) project.
 
 ## Key CUDA Functions We Trace
 
diff --git a/src/48-energy/README.zh.md b/src/48-energy/README.zh.md
index 2e6cde3..2b5c979 100644
--- a/src/48-energy/README.zh.md
+++ b/src/48-energy/README.zh.md
@@ -277,7 +277,7 @@ static void print_stats(struct energy_monitor_bpf *skel)
 使用提供的 Makefile 构建所有组件：
 
 ```bash
-cd /yunwei37/bpf-developer-tutorial/src/48-energy
+cd /home/yunwei37/bpf-developer-tutorial/src/48-energy
 make clean && make
 ```