Commit dfcc3e8
doc: improve wording in vm.md
Simplify complex sentence. Remove use of "straightforward".
PR-URL: #32427
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>1 parent bbea3f2 commit dfcc3e8
1 file changed
Lines changed: 2 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -362,9 +362,8 @@ specification. | |||
| 362 | 362 | ||
| 363 | 363 | Unlike `vm.Script` however, every `vm.Module` object is bound to a context from | |
| 364 | 364 | its creation. Operations on `vm.Module` objects are intrinsically asynchronous, | |
| 365 | - in contrast with the synchronous nature of `vm.Script` objects. With the help | ||
| 366 | - of async functions, however, manipulating `vm.Module` objects is fairly | ||
| 367 | - straightforward. | ||
| 365 | + in contrast with the synchronous nature of `vm.Script` objects. The use of | ||
| 366 | + 'async' functions can help with manipulating `vm.Module` objects. | ||
| 368 | 367 | ||
| 369 | 368 | Using a `vm.Module` object requires three distinct steps: creation/parsing, | |
| 370 | 369 | linking, and evaluation. These three steps are illustrated in the following | |
0 commit comments