From 4a218fd96fbd1dfd7158881798508a1259925d9d Mon Sep 17 00:00:00 2001
From: Michael Dawson <michael_dawson@ca.ibm.com>
Date: Fri, 17 May 2019 15:11:46 -0400
Subject: [PATCH] doc: remove stability highlight for stable functions

We don't have the stability functions for all stable
functions, only those that were previously experimental and
then when stable. Remove the stability indicator to be
consistent with the rest of the functions.

PR-URL: https://github.com/nodejs/node/pull/27753
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
---
 doc/api/n-api.md | 22 ----------------------
 1 file changed, 22 deletions(-)

diff --git a/doc/api/n-api.md b/doc/api/n-api.md
index 49db0d4e58591e..a39f62aa74cc2b 100644
--- a/doc/api/n-api.md
+++ b/doc/api/n-api.md
@@ -284,16 +284,12 @@ This is an opaque pointer that is used to represent a JavaScript value.
 
 ### napi_threadsafe_function
 
-> Stability: 2 - Stable
-
 This is an opaque pointer that represents a JavaScript function which can be
 called asynchronously from multiple threads via
 `napi_call_threadsafe_function()`.
 
 ### napi_threadsafe_function_release_mode
 
-> Stability: 2 - Stable
-
 A value to be given to `napi_release_threadsafe_function()` to indicate whether
 the thread-safe function is to be closed immediately (`napi_tsfn_abort`) or
 merely released (`napi_tsfn_release`) and thus available for subsequent use via
@@ -307,8 +303,6 @@ typedef enum {
 
 ### napi_threadsafe_function_call_mode
 
-> Stability: 2 - Stable
-
 A value to be given to `napi_call_threadsafe_function()` to indicate whether
 the call should block whenever the queue associated with the thread-safe
 function is full.
@@ -402,8 +396,6 @@ typedef void (*napi_async_complete_callback)(napi_env env,
 
 #### napi_threadsafe_function_call_js
 
-> Stability: 2 - Stable
-
 Function pointer used with asynchronous thread-safe function calls. The callback
 will be called on the main thread. Its purpose is to use a data item arriving
 via the queue from one of the secondary threads to construct the parameters
@@ -4600,8 +4592,6 @@ prevent the event loop from exiting. The APIs `napi_ref_threadsafe_function` and
 
 ### napi_create_threadsafe_function
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4
@@ -4644,8 +4634,6 @@ parameters and with `undefined` as its `this` value.
 
 ### napi_get_threadsafe_function_context
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4
@@ -4663,8 +4651,6 @@ This API may be called from any thread which makes use of `func`.
 
 ### napi_call_threadsafe_function
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4
@@ -4692,8 +4678,6 @@ This API may be called from any thread which makes use of `func`.
 
 ### napi_acquire_threadsafe_function
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4
@@ -4715,8 +4699,6 @@ This API may be called from any thread which will start making use of `func`.
 
 ### napi_release_threadsafe_function
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4
@@ -4744,8 +4726,6 @@ This API may be called from any thread which will stop making use of `func`.
 
 ### napi_ref_threadsafe_function
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4
@@ -4766,8 +4746,6 @@ This API may only be called from the main thread.
 
 ### napi_unref_threadsafe_function
 
-> Stability: 2 - Stable
-
 <!-- YAML
 added: v10.6.0
 napiVersion: 4