From 9dd4813008680406f41addfa1a33ab6c040086e0 Mon Sep 17 00:00:00 2001
From: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Date: Wed, 29 May 2019 15:57:26 -0700
Subject: [PATCH] doc: order deprecation reasons

PR-URL: https://github.com/nodejs/node/pull/27960
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
---
 doc/api/deprecations.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md
index d40cf903dfd42a..6022cf37ee35f5 100644
--- 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: