doc: update tags in adding-new-napi-api.md

legendecas · danielleadams · commit 60de663334f0 · 2022-08-15T21:12:28.000-04:00
The tag is now renamed as "node-api". PR-URL: #44190 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Akhil Marsonya <akhil.marsonya27@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Harshitha K P <harshitha014@gmail.com> Reviewed-By: Qingyu Deng <i@ayase-lab.com>
diff --git a/doc/contributing/adding-new-napi-api.md b/doc/contributing/adding-new-napi-api.md
@@ -18,7 +18,7 @@ Node-API.
     ABI compatibility with other versions of Node.js.
 * New API **should** be agnostic towards the underlying JavaScript VM.
 * New API PRs **must** have a corresponding documentation update.
-* New API PRs **must** be tagged as **n-api**.
+* New API PRs **must** be tagged as **node-api**.
 * There **must** be at least one test case showing how to use the API.
 * There **should** be at least one test case per interesting use of the API.
 * There **should** be a sample provided that operates in a realistic way
@@ -38,7 +38,7 @@ Node-API.
   * Experimental status exit criteria **must** involve at least the
     following:
     * A new PR **must** be opened in `nodejs/node` to remove experimental
-      status. This PR **must** be tagged as **n-api** and **semver-minor**.
+      status. This PR **must** be tagged as **node-api** and **semver-minor**.
     * Exiting an API from experimental **must** be signed off by the team.
     * If a backport is merited, an API **must** have a down-level
       implementation.
