diff --git a/doc/api/esm.md b/doc/api/esm.md
index a6c579466da200..f8fdc0c011bca2 100644
--- a/doc/api/esm.md
+++ b/doc/api/esm.md
@@ -620,8 +620,8 @@ stateless):
 
 ##### Approach #2: Isolate State
 
-The most straightforward `package.json` would be one that defines the separate
-CommonJS and ES module entry points directly:
+A `package.json` file can define the separate CommonJS and ES module entry
+points directly:
 
 <!-- eslint-skip -->
 ```js
diff --git a/doc/api/vm.md b/doc/api/vm.md
index 91d16be3986d22..ec731ffd36c6a0 100644
--- a/doc/api/vm.md
+++ b/doc/api/vm.md
@@ -362,9 +362,8 @@ specification.
 
 Unlike `vm.Script` however, every `vm.Module` object is bound to a context from
 its creation. Operations on `vm.Module` objects are intrinsically asynchronous,
-in contrast with the synchronous nature of `vm.Script` objects. With the help
-of async functions, however, manipulating `vm.Module` objects is fairly
-straightforward.
+in contrast with the synchronous nature of `vm.Script` objects. The use of
+'async' functions can help with manipulating `vm.Module` objects.
 
 Using a `vm.Module` object requires three distinct steps: creation/parsing,
 linking, and evaluation. These three steps are illustrated in the following