Skip to content

Commit 31cbda3

Browse files
Amanda Butlerbulislaw
authored andcommitted
Copy edit PowerManagement.md
Copy edit for consistent tense and precise language.
1 parent 6f7460d commit 31cbda3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/reference/api/platform/PowerManagement.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ There is only one sleep function in Mbed OS:
88
void sleep();
99
```
1010

11-
This function will invoke sleep manager, which will select the most appropriate sleep mode.
11+
This function invokes sleep manager, which selects the most appropriate sleep mode.
1212

13-
<span class="notes">**Note:** In most cases you won't need to call `sleep()` directly. Mbed OS will enter sleep mode automatically, any time the system is idle. That is when all your threads are in a waiting state, for example: waiting for an event or a timeout.</span>
13+
<span class="notes">**Note:** In most cases, you don't need to call `sleep()` directly. Mbed OS enters sleep mode automatically any time the system is idle. That is when all your threads are in a waiting state, for example waiting for an event or a timeout.</span>
1414

1515
#### Sleep modes
1616

@@ -28,7 +28,7 @@ This mode is similar to sleep but saves more power and has a longer wakeup time.
2828

2929
#### Sleep manager
3030

31-
The sleep manager provides an API and logic to control device sleep mode selection. While standard sleep shouldn't affect application execution, deep sleep might introduce some additional power savings that can affect the application, for instance high speed clock dependent drivers. To ensure correct operation of your application, sleep manager may disable deep sleep, in which case your board will enter normal sleep instead. This mechanism is mostly invisible for the user, but you should be aware that it may affect the power consumption of your hardware.
31+
The sleep manager provides an API and logic to control device sleep mode selection. Although standard sleep doesn't affect application execution, deep sleep might introduce some additional power savings that can affect the application, for instance high-speed clock-dependent drivers. To ensure correct operation of your application, sleep manager may disable deep sleep, in which case your board enters normal sleep, instead. This mechanism is mostly invisible to the user, but you should be aware that it may affect the power consumption of your hardware.
3232

3333
These Mbed OS drivers can lock the deep sleep:
3434

@@ -42,7 +42,7 @@ These Mbed OS drivers can lock the deep sleep:
4242

4343
### Idle loop
4444

45-
Idle loop is a background system thread, which scheduler will execute when there's no other threads ready to run. That may happen when your application is waiting for some event to happen. By default the idle loop will invoke sleep manager to enter a sleep mode. You can overwrite this behavior by providing a different handler as demonstrated below.
45+
Idle loop is a background system thread, which scheduler executes when no other threads are ready to run. That may happen when your application is waiting for an event to happen. By default, the idle loop invokes sleep manager to enter a sleep mode. You can overwrite this behavior by providing a different handler:
4646

4747
```c++
4848
void new_idle_loop()

0 commit comments

Comments
 (0)