From 24810c68869f515731b6c367fd37e40c149ed17d Mon Sep 17 00:00:00 2001
From: HarpPDX <7102637+HarpPDX@users.noreply.github.com>
Date: Sat, 28 Dec 2024 09:20:33 -0800
Subject: [PATCH] Update README.md

Fix typos in 'flame' and 'lock' command descriptions.
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index b26c4d2..438f5e9 100644
--- a/README.md
+++ b/README.md
@@ -55,10 +55,10 @@ $ ./perfspect config --cores 24 --llc 2.0 --uncoremaxfreq 1.8
 ...
 ```
 #### Flame Command
-Software flamegraphs are useful in diagnosing software performance bottlenecks. Run `perfspect flame -h` to capture a system-wide software flamegraph.
+Software flamegraphs are useful in diagnosing software performance bottlenecks. Run `perfspect flame` to capture a system-wide software flamegraph.
 
 #### Lock Command
-As system contains more and more cores, it would be usuful to be able to analyze the kernel lock overhead and potential false-sharing that impact the overall system scalability. Run `perfspect lock -h` to collect system wide hotspot, c2c and lock contention information, that will be helpful for experienced performance engineers to have a chance to look into the related problems.
+As systems contain more and more cores, it can be useful to analyze the kernel lock overhead and potential false-sharing that impacts system scalability. Run `perfspect lock` to collect system wide hotspot, c2c and lock contention information. Experienced performance engineers can analyze the collected information to identify bottlenecks.
 
 #### Metrics Command
 The `metrics` command provides system performance characterization metrics. The metrics provided are dependent on the platform architecture.