GeezerVison is showing github.com — doc: improve wording in vm.md · nodejs/node@3d752cd
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/vm.md +2-3Lines changed: 2 additions & 3 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -312,9 +312,8 @@ specification. |
312 | 312 |
|
313 | 313 | Unlike `vm.Script` however, every `vm.Module` object is bound to a context from |
314 | 314 | its creation. Operations on `vm.Module` objects are intrinsically asynchronous, |
315 | | -in contrast with the synchronous nature of `vm.Script` objects. With the help |
316 | | -of async functions, however, manipulating `vm.Module` objects is fairly |
317 | | -straightforward. |
| 315 | +in contrast with the synchronous nature of `vm.Script` objects. The use of |
| 316 | +'async' functions can help with manipulating `vm.Module` objects. |
318 | 317 |
|
319 | 318 | Using a `vm.Module` object requires three distinct steps: creation/parsing, |
320 | 319 | linking, and evaluation. These three steps are illustrated in the following |
|