From de3d043f7423f5dd22591e7179eb5560e5d4ad97 Mon Sep 17 00:00:00 2001 From: Seppe Soete Date: Wed, 3 Nov 2021 22:25:38 +0100 Subject: [PATCH] Fixed some typos in the readme in the Posix_GCC demo (#697) Co-authored-by: Seppe Soete Co-authored-by: Joshua Yan <52796499+yanjos-dev@users.noreply.github.com> --- FreeRTOS/Demo/Posix_GCC/Readme.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/FreeRTOS/Demo/Posix_GCC/Readme.md b/FreeRTOS/Demo/Posix_GCC/Readme.md index 95580b64c..966697a1d 100644 --- a/FreeRTOS/Demo/Posix_GCC/Readme.md +++ b/FreeRTOS/Demo/Posix_GCC/Readme.md @@ -1,4 +1,4 @@ -# Profilig your application +# Profiling your application ## Introduction [(from the official gprof doc)](https://sourceware.org/binutils/docs/gprof/Introduction.html#Introduction) Profiling allows you to learn where your program spent its time and which @@ -22,7 +22,7 @@ $ make PROFILE=1 ``` Run your application ``` -$ ./build/possix_demo +$ ./build/posix_demo ``` Since FreeRTOS and its application never come to an end and typically run forever. The user has to kill the application with **Ctrl_C** when they feel @@ -66,6 +66,6 @@ $ make SANITIZE_LEAK=1 ``` Then run your program normally. ``` -$ ./build/possix_demo +$ ./build/posix_demo ``` If an error is detected by the sanitizer, a report showing the error will be printed to stdout.