doc: order deprecation reasons

PR-URL: #27960 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
nodejs · Jun 17, 2019 · 9dd4813008680406f41addfa1a33ab6c040086e0 · 9dd4813
1 parent 62de36e
commit 9dd4813008680406f41addfa1a33ab6c040086e0
Showing with 5 additions and 3 deletions.

+5 −3 doc/api/deprecations.md
diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md
@@ -3,9 +3,11 @@
 <!--introduced_in=v7.7.0-->
 <!-- type=misc -->
 
-Node.js may deprecate APIs when either: (a) use of the API is considered to be
-unsafe, (b) an improved alternative API is available, or (c) breaking changes to
-the API are expected in a future major release.
+Node.js may deprecate APIs for any of the following reasons:
+
+* Use of the API is considered to be unsafe.
+* An improved alternative API is available.
+* Breaking changes to the API are expected in a future major release.
 
 Node.js utilizes three kinds of Deprecations: