doc: use consistent unordered list style

Convert to asterisks when there are mixed styles in document.
Addresses Markdownlint MD004 rule

PR-URL: #29516
Reviewed-By: David Carlier <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>

Author: nschonni

COLLABORATOR_GUIDE.md

@@ -3,35 +3,35 @@
 ## Contents
 
 * [Issues and Pull Requests](#issues-and-pull-requests)
-  - [Welcoming First-Time Contributors](#welcoming-first-time-contributors)
-  - [Closing Issues and Pull Requests](#closing-issues-and-pull-requests)
-  - [Author ready pull requests](#author-ready-pull-requests)
-  - [Handling own pull requests](#handling-own-pull-requests)
+  * [Welcoming First-Time Contributors](#welcoming-first-time-contributors)
+  * [Closing Issues and Pull Requests](#closing-issues-and-pull-requests)
+  * [Author ready pull requests](#author-ready-pull-requests)
+  * [Handling own pull requests](#handling-own-pull-requests)
 * [Accepting Modifications](#accepting-modifications)
-  - [Code Reviews](#code-reviews)
-  - [Consensus Seeking](#consensus-seeking)
-  - [Waiting for Approvals](#waiting-for-approvals)
-  - [Testing and CI](#testing-and-ci)
-    - [Useful CI Jobs](#useful-ci-jobs)
-  - [Internal vs. Public API](#internal-vs-public-api)
-  - [Breaking Changes](#breaking-changes)
-    - [Breaking Changes and Deprecations](#breaking-changes-and-deprecations)
-    - [Breaking Changes to Internal Elements](#breaking-changes-to-internal-elements)
-    - [Unintended Breaking Changes](#unintended-breaking-changes)
-      - [Reverting commits](#reverting-commits)
-  - [Introducing New Modules](#introducing-new-modules)
-  - [Additions to N-API](#additions-to-n-api)
-  - [Deprecations](#deprecations)
-  - [Involving the TSC](#involving-the-tsc)
+  * [Code Reviews](#code-reviews)
+  * [Consensus Seeking](#consensus-seeking)
+  * [Waiting for Approvals](#waiting-for-approvals)
+  * [Testing and CI](#testing-and-ci)
+    * [Useful CI Jobs](#useful-ci-jobs)
+  * [Internal vs. Public API](#internal-vs-public-api)
+  * [Breaking Changes](#breaking-changes)
+    * [Breaking Changes and Deprecations](#breaking-changes-and-deprecations)
+    * [Breaking Changes to Internal Elements](#breaking-changes-to-internal-elements)
+    * [Unintended Breaking Changes](#unintended-breaking-changes)
+      * [Reverting commits](#reverting-commits)
+  * [Introducing New Modules](#introducing-new-modules)
+  * [Additions to N-API](#additions-to-n-api)
+  * [Deprecations](#deprecations)
+  * [Involving the TSC](#involving-the-tsc)
 * [Landing Pull Requests](#landing-pull-requests)
-  - [Using `git-node`](#using-git-node)
-  - [Technical HOWTO](#technical-howto)
-  - [Troubleshooting](#troubleshooting)
-  - [I Made a Mistake](#i-made-a-mistake)
-  - [Long Term Support](#long-term-support)
-    - [What is LTS?](#what-is-lts)
-    - [How are LTS Branches Managed?](#how-are-lts-branches-managed)
-    - [How can I help?](#how-can-i-help)
+  * [Using `git-node`](#using-git-node)
+  * [Technical HOWTO](#technical-howto)
+  * [Troubleshooting](#troubleshooting)
+  * [I Made a Mistake](#i-made-a-mistake)
+  * [Long Term Support](#long-term-support)
+    * [What is LTS?](#what-is-lts)
+    * [How are LTS Branches Managed?](#how-are-lts-branches-managed)
+    * [How can I help?](#how-can-i-help)
 * [Who to CC in the issue tracker](#who-to-cc-in-the-issue-tracker)
 
 This document explains how Collaborators manage the Node.js project.
@@ -371,10 +371,10 @@ deprecation level of an API.
 Collaborators may opt to elevate pull requests or issues to the [TSC][].
 Do this if a pull request or issue:
 
-- is labeled `semver-major`, or
-- has a significant impact on the codebase, or
-- is controversial, or
-- is at an impasse among Collaborators who are participating in the discussion.
+* is labeled `semver-major`, or
+* has a significant impact on the codebase, or
+* is controversial, or
+* is at an impasse among Collaborators who are participating in the discussion.
 
 @-mention the `@nodejs/tsc` GitHub team if you want to elevate an issue to the
 [TSC][]. Do not use the GitHub UI on the right-hand side to assign to

CPP_STYLE_GUIDE.md

@@ -191,8 +191,8 @@ class FancyContainer {
 
 ### Memory allocation
 
-- `Malloc()`, `Calloc()`, etc. from `util.h` abort in Out-of-Memory situations
-- `UncheckedMalloc()`, etc. return `nullptr` in OOM situations
+* `Malloc()`, `Calloc()`, etc. from `util.h` abort in Out-of-Memory situations
+* `UncheckedMalloc()`, etc. return `nullptr` in OOM situations
 
 ### Use `nullptr` instead of `NULL` or `0`
 
@@ -278,10 +278,10 @@ data[0] = 12345;
 
 ### Type casting
 
-- Use `static_cast<T>` if casting is required, and it is valid
-- Use `reinterpret_cast` only when it is necessary
-- Avoid C-style casts (`(type)value`)
-- `dynamic_cast` does not work because Node.js is built without
+* Use `static_cast<T>` if casting is required, and it is valid
+* Use `reinterpret_cast` only when it is necessary
+* Avoid C-style casts (`(type)value`)
+* `dynamic_cast` does not work because Node.js is built without
   [Run Time Type Information][]
 
 Further reading:

GOVERNANCE.md

@@ -2,13 +2,13 @@
 
 <!-- TOC -->
 
-- [Collaborators](#collaborators)
-  - [Collaborator Activities](#collaborator-activities)
-- [Technical Steering Committee](#technical-steering-committee)
-  - [TSC Meetings](#tsc-meetings)
-- [Collaborator Nominations](#collaborator-nominations)
-  - [Onboarding](#onboarding)
-- [Consensus Seeking Process](#consensus-seeking-process)
+* [Collaborators](#collaborators)
+  * [Collaborator Activities](#collaborator-activities)
+* [Technical Steering Committee](#technical-steering-committee)
+  * [TSC Meetings](#tsc-meetings)
+* [Collaborator Nominations](#collaborator-nominations)
+  * [Onboarding](#onboarding)
+* [Consensus Seeking Process](#consensus-seeking-process)
 
 <!-- /TOC -->
 

SECURITY.md

@@ -14,22 +14,22 @@ nonetheless.
 
 ## Public disclosure preferred
 
-- [#14519](https://github.com/nodejs/node/issues/14519): _Internal domain
+* [#14519](https://github.com/nodejs/node/issues/14519): _Internal domain
   function can be used to cause segfaults_. Requires the ability to execute
   arbitrary JavaScript code. That is already the highest level of privilege
   possible.
 
 ## Private disclosure preferred
 
-- [CVE-2016-7099](https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/):
+* [CVE-2016-7099](https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/):
   _Fix invalid wildcard certificate validation check_. This was a high-severity
   defect. It caused Node.js TLS clients to accept invalid wildcard certificates.
 
-- [#5507](https://github.com/nodejs/node/pull/5507): _Fix a defect that makes
+* [#5507](https://github.com/nodejs/node/pull/5507): _Fix a defect that makes
   the CacheBleed Attack possible_. Many, though not all, OpenSSL vulnerabilities
   in the TLS/SSL protocols also affect Node.js.
 
-- [CVE-2016-2216](https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/):
+* [CVE-2016-2216](https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/):
   _Fix defects in HTTP header parsing for requests and responses that can allow
   response splitting_. This was a remotely-exploitable defect in the Node.js
   HTTP implementation.

doc/api/addons.md

@@ -17,13 +17,13 @@ for more information on N-API.
 When not using N-API, implementing Addons is complicated,
 involving knowledge of several components and APIs:
 
-- V8: the C++ library Node.js currently uses to provide the
+* V8: the C++ library Node.js currently uses to provide the
   JavaScript implementation. V8 provides the mechanisms for creating objects,
   calling functions, etc. V8's API is documented mostly in the
   `v8.h` header file (`deps/v8/include/v8.h` in the Node.js source
   tree), which is also available [online][v8-docs].
 
-- [libuv][]: The C library that implements the Node.js event loop, its worker
+* [libuv][]: The C library that implements the Node.js event loop, its worker
   threads and all of the asynchronous behaviors of the platform. It also
   serves as a cross-platform abstraction library, giving easy, POSIX-like
   access across all major operating systems to many common system tasks, such
@@ -35,11 +35,11 @@ involving knowledge of several components and APIs:
   off-loading work via libuv to non-blocking system operations, worker threads
   or a custom use of libuv's threads.
 
-- Internal Node.js libraries. Node.js itself exports a number of C++ APIs
+* Internal Node.js libraries. Node.js itself exports a number of C++ APIs
   that Addons can use — the most important of which is the
   `node::ObjectWrap` class.
 
-- Node.js includes a number of other statically linked libraries including
+* Node.js includes a number of other statically linked libraries including
   OpenSSL. These other libraries are located in the `deps/` directory in the
   Node.js source tree. Only the libuv, OpenSSL, V8 and zlib symbols are
   purposefully re-exported by Node.js and may be used to various extents by
@@ -262,8 +262,8 @@ signature.
 In order to be loaded from multiple Node.js environments,
 such as a main thread and a Worker thread, an add-on needs to either:
 
-- Be an N-API addon, or
-- Be declared as context-aware using `NODE_MODULE_INIT()` as described above
+* Be an N-API addon, or
+* Be declared as context-aware using `NODE_MODULE_INIT()` as described above
 
 ### Building
 

doc/api/cli.md

@@ -301,8 +301,8 @@ added: v11.4.0
 
 Chooses an HTTP parser library. Available values are:
 
-- `llhttp` for https://llhttp.org/
-- `legacy` for https://github.com/nodejs/http-parser
+* `llhttp` for https://llhttp.org/
+* `legacy` for https://github.com/nodejs/http-parser
 
 The default is `llhttp`, unless otherwise specified when building Node.js.
 
@@ -987,79 +987,79 @@ node --require "./a.js" --require "./b.js"
 
 Node.js options that are allowed are:
 <!-- node-options-node start -->
-- `--enable-fips`
-- `--es-module-specifier-resolution`
-- `--experimental-exports`
-- `--experimental-modules`
-- `--experimental-policy`
-- `--experimental-repl-await`
-- `--experimental-report`
-- `--experimental-vm-modules`
-- `--experimental-wasm-modules`
-- `--force-fips`
-- `--frozen-intrinsics`
-- `--heapsnapshot-signal`
-- `--http-parser`
-- `--icu-data-dir`
-- `--input-type`
-- `--inspect-brk`
-- `--inspect-port`, `--debug-port`
-- `--inspect-publish-uid`
-- `--inspect`
-- `--loader`
-- `--max-http-header-size`
-- `--napi-modules`
-- `--no-deprecation`
-- `--no-force-async-hooks-checks`
-- `--no-warnings`
-- `--openssl-config`
-- `--pending-deprecation`
-- `--policy-integrity`
-- `--preserve-symlinks-main`
-- `--preserve-symlinks`
-- `--prof-process`
-- `--redirect-warnings`
-- `--report-directory`
-- `--report-filename`
-- `--report-on-fatalerror`
-- `--report-on-signal`
-- `--report-signal`
-- `--report-uncaught-exception`
-- `--require`, `-r`
-- `--throw-deprecation`
-- `--title`
-- `--tls-cipher-list`
-- `--tls-max-v1.2`
-- `--tls-max-v1.3`
-- `--tls-min-v1.0`
-- `--tls-min-v1.1`
-- `--tls-min-v1.2`
-- `--tls-min-v1.3`
-- `--trace-deprecation`
-- `--trace-event-categories`
-- `--trace-event-file-pattern`
-- `--trace-events-enabled`
-- `--trace-sync-io`
-- `--trace-tls`
-- `--trace-warnings`
-- `--track-heap-objects`
-- `--unhandled-rejections`
-- `--use-bundled-ca`
-- `--use-openssl-ca`
-- `--v8-pool-size`
-- `--zero-fill-buffers`
+* `--enable-fips`
+* `--es-module-specifier-resolution`
+* `--experimental-exports`
+* `--experimental-modules`
+* `--experimental-policy`
+* `--experimental-repl-await`
+* `--experimental-report`
+* `--experimental-vm-modules`
+* `--experimental-wasm-modules`
+* `--force-fips`
+* `--frozen-intrinsics`
+* `--heapsnapshot-signal`
+* `--http-parser`
+* `--icu-data-dir`
+* `--input-type`
+* `--inspect-brk`
+* `--inspect-port`, `--debug-port`
+* `--inspect-publish-uid`
+* `--inspect`
+* `--loader`
+* `--max-http-header-size`
+* `--napi-modules`
+* `--no-deprecation`
+* `--no-force-async-hooks-checks`
+* `--no-warnings`
+* `--openssl-config`
+* `--pending-deprecation`
+* `--policy-integrity`
+* `--preserve-symlinks-main`
+* `--preserve-symlinks`
+* `--prof-process`
+* `--redirect-warnings`
+* `--report-directory`
+* `--report-filename`
+* `--report-on-fatalerror`
+* `--report-on-signal`
+* `--report-signal`
+* `--report-uncaught-exception`
+* `--require`, `-r`
+* `--throw-deprecation`
+* `--title`
+* `--tls-cipher-list`
+* `--tls-max-v1.2`
+* `--tls-max-v1.3`
+* `--tls-min-v1.0`
+* `--tls-min-v1.1`
+* `--tls-min-v1.2`
+* `--tls-min-v1.3`
+* `--trace-deprecation`
+* `--trace-event-categories`
+* `--trace-event-file-pattern`
+* `--trace-events-enabled`
+* `--trace-sync-io`
+* `--trace-tls`
+* `--trace-warnings`
+* `--track-heap-objects`
+* `--unhandled-rejections`
+* `--use-bundled-ca`
+* `--use-openssl-ca`
+* `--v8-pool-size`
+* `--zero-fill-buffers`
 <!-- node-options-node end -->
 
 V8 options that are allowed are:
 <!-- node-options-v8 start -->
-- `--abort-on-uncaught-exception`
-- `--interpreted-frames-native-stack`
-- `--max-old-space-size`
-- `--perf-basic-prof-only-functions`
-- `--perf-basic-prof`
-- `--perf-prof-unwinding-info`
-- `--perf-prof`
-- `--stack-trace-limit`
+* `--abort-on-uncaught-exception`
+* `--interpreted-frames-native-stack`
+* `--max-old-space-size`
+* `--perf-basic-prof-only-functions`
+* `--perf-basic-prof`
+* `--perf-prof-unwinding-info`
+* `--perf-prof`
+* `--stack-trace-limit`
 <!-- node-options-v8 end -->
 
 ### `NODE_PATH=path[:…]`
@@ -1194,12 +1194,12 @@ Asynchronous system APIs are used by Node.js whenever possible, but where they
 do not exist, libuv's threadpool is used to create asynchronous node APIs based
 on synchronous system APIs. Node.js APIs that use the threadpool are:
 
-- all `fs` APIs, other than the file watcher APIs and those that are explicitly
+* all `fs` APIs, other than the file watcher APIs and those that are explicitly
   synchronous
-- asynchronous crypto APIs such as `crypto.pbkdf2()`, `crypto.scrypt()`,
+* asynchronous crypto APIs such as `crypto.pbkdf2()`, `crypto.scrypt()`,
   `crypto.randomBytes()`, `crypto.randomFill()`, `crypto.generateKeyPair()`
-- `dns.lookup()`
-- all `zlib` APIs, other than those that are explicitly synchronous
+* `dns.lookup()`
+* all `zlib` APIs, other than those that are explicitly synchronous
 
 Because libuv's threadpool has a fixed size, it means that if for whatever
 reason any of these APIs takes a long time, other (seemingly unrelated) APIs