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

@@ -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
 

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
 ```