From cfbc1c428e7f98690e84a14bd44f810c8310fd5d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?T=E2=80=A2=C3=98=E2=80=A2R=E2=80=A2=C3=9C=E2=80=A2S?= Date: Sun, 20 Feb 2022 12:59:31 +0400 Subject: [PATCH] Update doc/contributing/maintaining-types-for-nodejs.md Co-authored-by: Derek Lewis --- doc/contributing/maintaining-types-for-nodejs.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/doc/contributing/maintaining-types-for-nodejs.md b/doc/contributing/maintaining-types-for-nodejs.md index 2b45e9193456c8..6047274b79cac0 100644 --- a/doc/contributing/maintaining-types-for-nodejs.md +++ b/doc/contributing/maintaining-types-for-nodejs.md @@ -13,8 +13,6 @@ maintained. The different options were discussed as part of the [next-10][] effort and it was agreed that maintaining them externally is the best approach. -[next-10][] -effort and it was agreed that maintaining them externally is the best approach. Some of the advantages to this approach include: * Node.js maintainers do not need to be familiar with any given type