From dc084223a33e63d2441966977762a73c346b475b Mon Sep 17 00:00:00 2001
From: Michael Dawson <michael_dawson@ca.ibm.com>
Date: Wed, 4 Sep 2019 15:18:26 -0400
Subject: [PATCH 1/3] doc: simply wording in n-api doc

Simplify/clarify wording documenting n-api execute
callback.
---
 doc/api/n-api.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/api/n-api.md b/doc/api/n-api.md
index 8c02d418bf4eb9..1f57f98cc96441 100644
--- a/doc/api/n-api.md
+++ b/doc/api/n-api.md
@@ -548,12 +548,12 @@ operations. Callback functions must satisfy the following signature:
 typedef void (*napi_async_execute_callback)(napi_env env, void* data);
 ```
 
-Implementations of this type of function should avoid making any N-API calls
-that could result in the execution of JavaScript or interaction with
-JavaScript objects. Most often, any code that needs to make N-API
-calls should be made in `napi_async_complete_callback` instead.
-Avoid using the `napi_env` parameter in the execute callback as
-it will likely execute JavaScript.
+Implementations of this function must avoid making N-API calls
+that result in the execution of JavaScript or interaction with
+JavaScript objects. Any code that needs to make N-API
+calls should be in the `napi_async_complete_callback` instead.
+Do not use the `napi_env` parameter as it will likely
+result in execution of JavaScript.
 
 #### napi_async_complete_callback
 <!-- YAML

From bf69aabac48d7ad421645ef18454e3cdfb9343e4 Mon Sep 17 00:00:00 2001
From: Michael Dawson <michael_dawson@ca.ibm.com>
Date: Thu, 5 Sep 2019 16:09:00 -0400
Subject: [PATCH 2/3] Update doc/api/n-api.md

Co-Authored-By: Rich Trott <rtrott@gmail.com>
---
 doc/api/n-api.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/api/n-api.md b/doc/api/n-api.md
index 1f57f98cc96441..6e826b58b1b4d0 100644
--- a/doc/api/n-api.md
+++ b/doc/api/n-api.md
@@ -549,7 +549,7 @@ typedef void (*napi_async_execute_callback)(napi_env env, void* data);
 ```
 
 Implementations of this function must avoid making N-API calls
-that result in the execution of JavaScript or interaction with
+that execute JavaScript or interact with
 JavaScript objects. Any code that needs to make N-API
 calls should be in the `napi_async_complete_callback` instead.
 Do not use the `napi_env` parameter as it will likely

From 644887892d70dc4af24a5180b590a8890e9e9be9 Mon Sep 17 00:00:00 2001
From: Michael Dawson <michael_dawson@ca.ibm.com>
Date: Thu, 5 Sep 2019 16:09:53 -0400
Subject: [PATCH 3/3] Update doc/api/n-api.md

Co-Authored-By: Rich Trott <rtrott@gmail.com>
---
 doc/api/n-api.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/api/n-api.md b/doc/api/n-api.md
index 6e826b58b1b4d0..2cbe01684d246a 100644
--- a/doc/api/n-api.md
+++ b/doc/api/n-api.md
@@ -550,7 +550,7 @@ typedef void (*napi_async_execute_callback)(napi_env env, void* data);
 
 Implementations of this function must avoid making N-API calls
 that execute JavaScript or interact with
-JavaScript objects. Any code that needs to make N-API
+JavaScript objects.  N-API
 calls should be in the `napi_async_complete_callback` instead.
 Do not use the `napi_env` parameter as it will likely
 result in execution of JavaScript.