Skip to content

Commit d754c34

Browse files
Amanda Butlerkegilbert
authored andcommitted
Edit MbedStats.md
Make minor copy edits.
1 parent 59a9d58 commit d754c34

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/api/platform/MbedStats.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Mbed statistics
22

3-
Mbed OS provides a set of functions that you can use to capture the memory and thread statistics at runtime. `mbed_stats.h` declares these functions. To enable all Mbed OS platform statistics, you must enable the following Mbed OS configuration option.
3+
Mbed OS provides a set of functions that you can use to capture the memory and thread statistics at runtime. `mbed_stats.h` declares these functions. To enable all Mbed OS platform statistics, you must enable the following Mbed OS configuration option:
44

55
```json
66
{
@@ -14,7 +14,7 @@ Mbed OS provides a set of functions that you can use to capture the memory and t
1414

1515
### Memory statistics
1616

17-
You can use memory statistics functions to capture heap usage, cumulative stack usage or stack usage per thread at runtime. To enable memory usage monitoring, you must enable the following Mbed OS configuration options.
17+
You can use memory statistics functions to capture heap use, cumulative stack use or stack use for each thread at runtime. To enable memory use monitoring, you must enable the following Mbed OS configuration options:
1818

1919
```json
2020
{
@@ -31,7 +31,7 @@ You can use memory statistics functions to capture heap usage, cumulative stack
3131

3232
### Thread statistics
3333

34-
You can use the thread statistics function `mbed_stats_thread_get_each` to capture the thread ID, state, priority, name and stack information for all active threads at runtime. To enable thread monitoring, you must enable the following Mbed OS configuration options.
34+
You can use the thread statistics function `mbed_stats_thread_get_each` to capture the thread ID, state, priority, name and stack information for all active threads at runtime. To enable thread monitoring, you must enable the following Mbed OS configuration options:
3535

3636
```json
3737
{
@@ -45,7 +45,7 @@ You can use the thread statistics function `mbed_stats_thread_get_each` to captu
4545

4646
### System information
4747

48-
You can use the `mbed_stats_sys_get` function to get the CPU ID, compiler information and RAM and ROM memories on the target device. To enable system information fetching, you must enable the following Mbed OS configuration option.
48+
You can use the `mbed_stats_sys_get` function to get the CPU ID, compiler information and RAM and ROM memories on the target device. To enable system information fetching, you must enable the following Mbed OS configuration option:
4949

5050
```json
5151
{
@@ -59,7 +59,7 @@ You can use the `mbed_stats_sys_get` function to get the CPU ID, compiler inform
5959

6060
### CPU statistics
6161

62-
You can use the `mbed_stats_cpu_get` function to get the uptime, idle time and sleep time information. Timing information available is cumulative since the system is on. Please note CPU statistics depend on the availability of the low power timer in the hardware. To enable fetching of CPU information, you must enable the following Mbed OS configuration option.
62+
You can use the `mbed_stats_cpu_get` function to get the uptime, idle time and sleep time information. Timing information available is cumulative because the system is on. Please note CPU statistics depend on the availability of the low power timer in the hardware. To enable fetching of CPU information, you must enable the following Mbed OS configuration option:
6363

6464
```json
6565
{

0 commit comments

Comments
 (0)