From 2a80f8b8634a78202c60783d5c2c293adcbce7c5 Mon Sep 17 00:00:00 2001
From: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Date: Sun, 29 Apr 2018 01:26:30 +0300
Subject: [PATCH] doc: add missing backticks in n-api.md

Codify types, variable names, and code fragments
checking patterns I've managed to think of.

Some nits were also fixed in passing
(add missing periods, remove extra line breaks etc).
---
 doc/api/n-api.md | 415 +++++++++++++++++++++++------------------------
 1 file changed, 204 insertions(+), 211 deletions(-)

diff --git a/doc/api/n-api.md b/doc/api/n-api.md
index 26b5e87463948e..adb8647b399ecd 100644
--- a/doc/api/n-api.md
+++ b/doc/api/n-api.md
@@ -185,7 +185,6 @@ typedef void (*napi_finalize)(napi_env env,
                               void* finalize_hint);
 ```
 
-
 #### napi_async_execute_callback
 Function pointer used with functions that support asynchronous
 operations. Callback functions must statisfy the following signature:
@@ -223,7 +222,7 @@ In cases where a return value other than `napi_ok` or
 must be called to check if an exception is pending.
 See the section on exceptions for more details.
 
-The full set of possible napi_status values is defined
+The full set of possible `napi_status` values is defined
 in `napi_api_types.h`.
 
 The `napi_status` return value provides a VM-independent representation of
@@ -282,7 +281,6 @@ logging purposes.
 
 This API can be called even if there is a pending JavaScript exception.
 
-
 ### Exceptions
 Any N-API function call may result in a pending JavaScript exception. This is
 obviously the case for any function that may cause the execution of
@@ -312,10 +310,10 @@ and then continue. This is only recommended in specific cases
 where it is known that the exception can be safely handled. In these
 cases [`napi_get_and_clear_last_exception`][] can be used to get and
 clear the exception. On success, result will contain the handle to
-the last JavaScript Object thrown. If it is determined, after
+the last JavaScript `Object` thrown. If it is determined, after
 retrieving the exception, the exception cannot be handled after all
 it can be re-thrown it with [`napi_throw`][] where error is the
-JavaScript Error object to be thrown.
+JavaScript `Error` object to be thrown.
 
 The following utility functions are also available in case native code
 needs to throw an exception or determine if a `napi_value` is an instance
@@ -324,10 +322,10 @@ of a JavaScript `Error` object: [`napi_throw_error`][],
 [`napi_is_error`][].
 
 The following utility functions are also available in case native
-code needs to create an Error object: [`napi_create_error`][],
-[`napi_create_type_error`][], and [`napi_create_range_error`][].
-where result is the napi_value that refers to the newly created
-JavaScript Error object.
+code needs to create an `Error` object: [`napi_create_error`][],
+[`napi_create_type_error`][], and [`napi_create_range_error`][],
+where result is the `napi_value` that refers to the newly created
+JavaScript `Error` object.
 
 The Node.js project is adding error codes to all of the errors
 generated internally. The goal is for applications to use these
@@ -346,9 +344,9 @@ the name associated with the error is also updated to be:
 originalName [code]
 ```
 
-where originalName is the original name associated with the error
-and code is the code that was provided. For example if the code
-is 'ERR_ERROR_1' and a TypeError is being created the name will be:
+where `originalName` is the original name associated with the error
+and `code` is the code that was provided. For example if the code
+is `'ERR_ERROR_1'` and a `TypeError` is being created the name will be:
 
 ```text
 TypeError [ERR_ERROR_1]
@@ -362,12 +360,11 @@ added: v8.0.0
 NODE_EXTERN napi_status napi_throw(napi_env env, napi_value error);
 ```
 - `[in] env`: The environment that the API is invoked under.
-- `[in] error`: The `napi_value` for the Error to be thrown.
+- `[in] error`: The `napi_value` for the `Error` to be thrown.
 
 Returns `napi_ok` if the API succeeded.
 
-This API throws the JavaScript Error provided.
-
+This API throws the JavaScript `Error` provided.
 
 #### napi_throw_error
 <!-- YAML
@@ -385,7 +382,7 @@ the error.
 
 Returns `napi_ok` if the API succeeded.
 
-This API throws a JavaScript Error with the text provided.
+This API throws a JavaScript `Error` with the text provided.
 
 #### napi_throw_type_error
 <!-- YAML
@@ -403,7 +400,7 @@ the error.
 
 Returns `napi_ok` if the API succeeded.
 
-This API throws a JavaScript TypeError with the text provided.
+This API throws a JavaScript `TypeError` with the text provided.
 
 #### napi_throw_range_error
 <!-- YAML
@@ -421,8 +418,7 @@ the error.
 
 Returns `napi_ok` if the API succeeded.
 
-This API throws a JavaScript RangeError with the text provided.
-
+This API throws a JavaScript `RangeError` with the text provided.
 
 #### napi_is_error
 <!-- YAML
@@ -442,7 +438,6 @@ Returns `napi_ok` if the API succeeded.
 
 This API queries a `napi_value` to check if it represents an error object.
 
-
 #### napi_create_error
 <!-- YAML
 added: v8.0.0
@@ -456,13 +451,13 @@ NODE_EXTERN napi_status napi_create_error(napi_env env,
 - `[in] env`: The environment that the API is invoked under.
 - `[in] code`: Optional `napi_value` with the string for the error code to
                be associated with the error.
-- `[in] msg`: napi_value that references a JavaScript String to be
-used as the message for the Error.
+- `[in] msg`: `napi_value` that references a JavaScript `String` to be
+used as the message for the `Error`.
 - `[out] result`: `napi_value` representing the error created.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns a JavaScript Error with the text provided.
+This API returns a JavaScript `Error` with the text provided.
 
 #### napi_create_type_error
 <!-- YAML
@@ -477,14 +472,13 @@ NODE_EXTERN napi_status napi_create_type_error(napi_env env,
 - `[in] env`: The environment that the API is invoked under.
 - `[in] code`: Optional `napi_value` with the string for the error code to
                be associated with the error.
-- `[in] msg`: napi_value that references a JavaScript String to be
-used as the message for the Error.
+- `[in] msg`: `napi_value` that references a JavaScript `String` to be
+used as the message for the `Error`.
 - `[out] result`: `napi_value` representing the error created.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns a JavaScript TypeError with the text provided.
-
+This API returns a JavaScript `TypeError` with the text provided.
 
 #### napi_create_range_error
 <!-- YAML
@@ -499,13 +493,13 @@ NODE_EXTERN napi_status napi_create_range_error(napi_env env,
 - `[in] env`: The environment that the API is invoked under.
 - `[in] code`: Optional `napi_value` with the string for the error code to
                be associated with the error.
-- `[in] msg`: napi_value that references a JavaScript String to be
-used as the message for the Error.
+- `[in] msg`: `napi_value` that references a JavaScript `String` to be
+used as the message for the `Error`.
 - `[out] result`: `napi_value` representing the error created.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns a JavaScript RangeError with the text provided.
+This API returns a JavaScript `RangeError` with the text provided.
 
 #### napi_get_and_clear_last_exception
 <!-- YAML
@@ -756,9 +750,10 @@ napi_status napi_escape_handle(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] scope`: `napi_value` representing the current scope.
-- `[in] escapee`: `napi_value` representing the JavaScript Object to be escaped.
+- `[in] escapee`: `napi_value` representing the JavaScript `Object` to be
+escaped.
 - `[out] result`: `napi_value` representing the handle to the escaped
-Object in the outer scope.
+`Object` in the outer scope.
 
 Returns `napi_ok` if the API succeeded.
 
@@ -819,7 +814,7 @@ NODE_EXTERN napi_status napi_create_reference(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing the Object to which we want
+- `[in] value`: `napi_value` representing the `Object` to which we want
 a reference.
 - `[in] initial_refcount`: Initial reference count for the new reference.
 - `[out] result`: `napi_ref` pointing to the new reference.
@@ -827,7 +822,7 @@ a reference.
 Returns `napi_ok` if the API succeeded.
 
 This API create a new reference with the specified reference count
-to the Object passed in.
+to the `Object` passed in.
 
 #### napi_delete_reference
 <!-- YAML
@@ -895,14 +890,14 @@ NODE_EXTERN napi_status napi_get_reference_value(napi_env env,
 the `napi_value passed` in or out of these methods is a handle to the
 object to which the reference is related.
 - `[in] env`: The environment that the API is invoked under.
-- `[in] ref`: `napi_ref` for which we requesting the corresponding Object.
-- `[out] result`: The `napi_value` for the Object referenced by the
+- `[in] ref`: `napi_ref` for which we requesting the corresponding `Object`.
+- `[out] result`: The `napi_value` for the `Object` referenced by the
 `napi_ref`.
 
 Returns `napi_ok` if the API succeeded.
 
 If still valid, this API returns the `napi_value` representing the
-JavaScript Object associated with the `napi_ref`. Otherwise, result
+JavaScript `Object` associated with the `napi_ref`. Otherwise, result
 will be NULL.
 
 ## Module registration
@@ -1011,7 +1006,8 @@ following the macro invocation.
 For more details on setting properties on objects, see the section on
 [Working with JavaScript Properties][].
 
-For more details on building addon modules in general, refer to the existing API
+For more details on building addon modules in general, refer to the existing
+API.
 
 ## Working with JavaScript Values
 N-API exposes a set of APIs to create all types of JavaScript values.
@@ -1053,7 +1049,7 @@ described in
 [Section 6.1](https://tc39.github.io/ecma262/#sec-ecmascript-language-types) of
 the ECMAScript Language Specification.
 In addition to types in that section, `napi_valuetype` can also represent
-Functions and Objects with external data.
+`Function`s and `Object`s with external data.
 
 #### napi_typedarray_type
 ```C
@@ -1070,7 +1066,7 @@ typedef enum {
 } napi_typedarray_type;
 ```
 
-This represents the underlying binary scalar datatype of the TypedArray.
+This represents the underlying binary scalar datatype of the `TypedArray`.
 Elements of this enum correspond to
 [Section 22.2][] of the [ECMAScript Language Specification][].
 
@@ -1084,11 +1080,11 @@ napi_status napi_create_array(napi_env env, napi_value* result)
 ```
 
 - `[in] env`: The environment that the N-API call is invoked under.
-- `[out] result`: A `napi_value` representing a JavaScript Array.
+- `[out] result`: A `napi_value` representing a JavaScript `Array`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns an N-API value corresponding to a JavaScript Array type.
+This API returns an N-API value corresponding to a JavaScript `Array` type.
 JavaScript arrays are described in
 [Section 22.1][] of the ECMAScript Language Specification.
 
@@ -1103,13 +1099,13 @@ napi_status napi_create_array_with_length(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] length`: The initial length of the Array.
-- `[out] result`: A `napi_value` representing a JavaScript Array.
+- `[in] length`: The initial length of the `Array`.
+- `[out] result`: A `napi_value` representing a JavaScript `Array`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns an N-API value corresponding to a JavaScript Array type.
-The Array's length property is set to the passed-in length parameter.
+This API returns an N-API value corresponding to a JavaScript `Array` type.
+The `Array`'s length property is set to the passed-in length parameter.
 However, the underlying buffer is not guaranteed to be pre-allocated by the VM
 when the array is created - that behavior is left to the underlying VM
 implementation.
@@ -1133,22 +1129,22 @@ napi_status napi_create_arraybuffer(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] length`: The length in bytes of the array buffer to create.
-- `[out] data`: Pointer to the underlying byte buffer of the ArrayBuffer.
-- `[out] result`: A `napi_value` representing a JavaScript ArrayBuffer.
+- `[out] data`: Pointer to the underlying byte buffer of the `ArrayBuffer`.
+- `[out] result`: A `napi_value` representing a JavaScript `ArrayBuffer`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns an N-API value corresponding to a JavaScript ArrayBuffer.
-ArrayBuffers are used to represent fixed-length binary data buffers. They are
-normally used as a backing-buffer for TypedArray objects.
-The ArrayBuffer allocated will have an underlying byte buffer whose size is
+This API returns an N-API value corresponding to a JavaScript `ArrayBuffer`.
+`ArrayBuffer`s are used to represent fixed-length binary data buffers. They are
+normally used as a backing-buffer for `TypedArray` objects.
+The `ArrayBuffer` allocated will have an underlying byte buffer whose size is
 determined by the `length` parameter that's passed in.
 The underlying buffer is optionally returned back to the caller in case the
 caller wants to directly manipulate the buffer. This buffer can only be
 written to directly from native code. To write to this buffer from JavaScript,
-a typed array or DataView object would need to be created.
+a typed array or `DataView` object would need to be created.
 
-JavaScript ArrayBuffer objects are described in
+JavaScript `ArrayBuffer` objects are described in
 [Section 24.1][] of the ECMAScript Language Specification.
 
 #### napi_create_buffer
@@ -1170,7 +1166,7 @@ napi_status napi_create_buffer(napi_env env,
 Returns `napi_ok` if the API succeeded.
 
 This API allocates a `node::Buffer` object. While this is still a
-fully-supported data structure, in most cases using a TypedArray will suffice.
+fully-supported data structure, in most cases using a `TypedArray` will suffice.
 
 #### napi_create_buffer_copy
 <!-- YAML
@@ -1188,14 +1184,14 @@ napi_status napi_create_buffer_copy(napi_env env,
 - `[in] size`: Size in bytes of the input buffer (should be the same as the
  size of the new buffer).
 - `[in] data`: Raw pointer to the underlying buffer to copy from.
-- `[out] result_data`: Pointer to the new Buffer's underlying data buffer.
+- `[out] result_data`: Pointer to the new `Buffer`'s underlying data buffer.
 - `[out] result`: A `napi_value` representing a `node::Buffer`.
 
 Returns `napi_ok` if the API succeeded.
 
 This API allocates a `node::Buffer` object and initializes it with data copied
 from the passed-in buffer. While this is still a fully-supported data
-structure, in most cases using a TypedArray will suffice.
+structure, in most cases using a `TypedArray` will suffice.
 
 #### napi_create_external
 <!-- YAML
@@ -1245,22 +1241,22 @@ napi_create_external_arraybuffer(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] external_data`: Pointer to the underlying byte buffer of the
-ArrayBuffer.
+`ArrayBuffer`.
 - `[in] byte_length`: The length in bytes of the underlying buffer.
-- `[in] finalize_cb`: Optional callback to call when the ArrayBuffer is
+- `[in] finalize_cb`: Optional callback to call when the `ArrayBuffer` is
 being collected.
 - `[in] finalize_hint`: Optional hint to pass to the finalize callback
 during collection.
-- `[out] result`: A `napi_value` representing a JavaScript ArrayBuffer.
+- `[out] result`: A `napi_value` representing a JavaScript `ArrayBuffer`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns an N-API value corresponding to a JavaScript ArrayBuffer.
-The underlying byte buffer of the ArrayBuffer is externally allocated and
+This API returns an N-API value corresponding to a JavaScript `ArrayBuffer`.
+The underlying byte buffer of the `ArrayBuffer` is externally allocated and
 managed. The caller must ensure that the byte buffer remains valid until the
 finalize callback is called.
 
-JavaScript ArrayBuffers are described in
+JavaScript `ArrayBuffer`s are described in
 [Section 24.1][] of the ECMAScript Language Specification.
 
 #### napi_create_external_buffer
@@ -1280,7 +1276,7 @@ napi_status napi_create_external_buffer(napi_env env,
 - `[in] length`: Size in bytes of the input buffer (should be the same as
 the size of the new buffer).
 - `[in] data`: Raw pointer to the underlying buffer to copy from.
-- `[in] finalize_cb`: Optional callback to call when the ArrayBuffer is
+- `[in] finalize_cb`: Optional callback to call when the `ArrayBuffer` is
 being collected.
 - `[in] finalize_hint`: Optional hint to pass to the finalize callback
 during collection.
@@ -1290,7 +1286,7 @@ Returns `napi_ok` if the API succeeded.
 
 This API allocates a `node::Buffer` object and initializes it with data
 backed by the passed in buffer. While this is still a fully-supported data
-structure, in most cases using a TypedArray will suffice.
+structure, in most cases using a `TypedArray` will suffice.
 
 For Node.js >=4 `Buffers` are Uint8Arrays.
 
@@ -1320,7 +1316,7 @@ function when it is invoked.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns an N-API value corresponding to a JavaScript Function object.
+This API returns an N-API value corresponding to a JavaScript `Function` object.
 It's used to wrap native functions so that they can be invoked from JavaScript.
 
 JavaScript Functions are described in
@@ -1336,14 +1332,14 @@ napi_status napi_create_object(napi_env env, napi_value* result)
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[out] result`: A `napi_value` representing a JavaScript Object.
+- `[out] result`: A `napi_value` representing a JavaScript `Object`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API allocates a default JavaScript Object.
+This API allocates a default JavaScript `Object`.
 It is the equivalent of doing `new Object()` in JavaScript.
 
-The JavaScript Object type is described in
+The JavaScript `Object` type is described in
 [Section 6.1.7](https://tc39.github.io/ecma262/#sec-object-type) of the
 ECMAScript Language Specification.
 
@@ -1358,15 +1354,15 @@ napi_status napi_create_symbol(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] description`: Optional napi_value which refers to a JavaScript
-String to be set as the description for the symbol.
-- `[out] result`: A `napi_value` representing a JavaScript Symbol.
+- `[in] description`: Optional `napi_value` which refers to a JavaScript
+`String` to be set as the description for the symbol.
+- `[out] result`: A `napi_value` representing a JavaScript `Symbol`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API creates a JavaScript Symbol object from a UTF8-encoded C string
+This API creates a JavaScript `Symbol` object from a UTF8-encoded C string.
 
-The JavaScript Symbol type is described in
+The JavaScript `Symbol` type is described in
 [Section 19.4](https://tc39.github.io/ecma262/#sec-symbol-objects)
 of the ECMAScript Language Specification.
 
@@ -1384,27 +1380,27 @@ napi_status napi_create_typedarray(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] type`: Scalar datatype of the elements within the TypedArray.
-- `[in] length`: Number of elements in the TypedArray.
-- `[in] arraybuffer`: ArrayBuffer underlying the typed array.
-- `[in] byte_offset`: The byte offset within the ArrayBuffer from which to
-start projecting the TypedArray.
-- `[out] result`: A `napi_value` representing a JavaScript TypedArray.
+- `[in] type`: Scalar datatype of the elements within the `TypedArray`.
+- `[in] length`: Number of elements in the `TypedArray`.
+- `[in] arraybuffer`: `ArrayBuffer` underlying the typed array.
+- `[in] byte_offset`: The byte offset within the `ArrayBuffer` from which to
+start projecting the `TypedArray`.
+- `[out] result`: A `napi_value` representing a JavaScript `TypedArray`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API creates a JavaScript TypedArray object over an existing ArrayBuffer.
-TypedArray objects provide an array-like view over an underlying data buffer
-where each element has the same underlying binary scalar datatype.
+This API creates a JavaScript `TypedArray` object over an existing
+`ArrayBuffer`. `TypedArray` objects provide an array-like view over an
+underlying data buffer where each element has the same underlying binary scalar
+datatype.
 
-It's required that (length * size_of_element) + byte_offset should
-be <= the size in bytes of the array passed in. If not, a RangeError exception
+It's required that `(length * size_of_element) + byte_offset` should
+be <= the size in bytes of the array passed in. If not, a `RangeError` exception
 is raised.
 
-JavaScript TypedArray Objects are described in
+JavaScript `TypedArray` objects are described in
 [Section 22.2][] of the ECMAScript Language Specification.
 
-
 #### napi_create_dataview
 <!-- YAML
 added: v8.3.0
@@ -1416,26 +1412,26 @@ napi_status napi_create_dataview(napi_env env,
                                  napi_value arraybuffer,
                                  size_t byte_offset,
                                  napi_value* result)
-
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] length`: Number of elements in the DataView.
-- `[in] arraybuffer`: ArrayBuffer underlying the DataView.
-- `[in] byte_offset`: The byte offset within the ArrayBuffer from which to
-  start projecting the DataView.
-- `[out] result`: A `napi_value` representing a JavaScript DataView.
+- `[in] length`: Number of elements in the `DataView`.
+- `[in] arraybuffer`: `ArrayBuffer` underlying the `DataView`.
+- `[in] byte_offset`: The byte offset within the `ArrayBuffer` from which to
+  start projecting the `DataView`.
+- `[out] result`: A `napi_value` representing a JavaScript `DataView`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API creates a JavaScript DataView object over an existing ArrayBuffer.
-DataView objects provide an array-like view over an underlying data buffer,
-but one which allows items of different size and type in the ArrayBuffer.
+This API creates a JavaScript `DataView` object over an existing `ArrayBuffer`.
+`DataView` objects provide an array-like view over an underlying data buffer,
+but one which allows items of different size and type in the `ArrayBuffer`.
 
 It is required that `byte_length + byte_offset` is less than or equal to the
-size in bytes of the array passed in. If not, a RangeError exception is raised.
+size in bytes of the array passed in. If not, a `RangeError` exception is
+raised.
 
-JavaScript DataView Objects are described in
+JavaScript `DataView` objects are described in
 [Section 24.3][] of the ECMAScript Language Specification.
 
 ### Functions to convert from C types to N-API
@@ -1449,14 +1445,14 @@ napi_status napi_create_int32(napi_env env, int32_t value, napi_value* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: Integer value to be represented in JavaScript.
-- `[out] result`: A `napi_value` representing a JavaScript Number.
+- `[out] result`: A `napi_value` representing a JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded.
 
 This API is used to convert from the C `int32_t` type to the JavaScript
-Number type.
+`Number` type.
 
-The JavaScript Number type is described in
+The JavaScript `Number` type is described in
 [Section 6.1.6][] of the ECMAScript Language Specification.
 
 #### napi_create_uint32
@@ -1469,14 +1465,14 @@ napi_status napi_create_uint32(napi_env env, uint32_t value, napi_value* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: Unsigned integer value to be represented in JavaScript.
-- `[out] result`: A `napi_value` representing a JavaScript Number.
+- `[out] result`: A `napi_value` representing a JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded.
 
 This API is used to convert from the C `uint32_t` type to the JavaScript
-Number type.
+`Number` type.
 
-The JavaScript Number type is described in
+The JavaScript `Number` type is described in
 [Section 6.1.6][] of the ECMAScript Language Specification.
 
 #### napi_create_int64
@@ -1489,14 +1485,14 @@ napi_status napi_create_int64(napi_env env, int64_t value, napi_value* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: Integer value to be represented in JavaScript.
-- `[out] result`: A `napi_value` representing a JavaScript Number.
+- `[out] result`: A `napi_value` representing a JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded.
 
 This API is used to convert from the C `int64_t` type to the JavaScript
-Number type.
+`Number` type.
 
-The JavaScript Number type is described in [Section 6.1.6][]
+The JavaScript `Number` type is described in [Section 6.1.6][]
 of the ECMAScript Language Specification. Note the complete range of `int64_t`
 cannot be represented with full precision in JavaScript. Integer values
 outside the range of
@@ -1515,14 +1511,14 @@ napi_status napi_create_double(napi_env env, double value, napi_value* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: Double-precision value to be represented in JavaScript.
-- `[out] result`: A `napi_value` representing a JavaScript Number.
+- `[out] result`: A `napi_value` representing a JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded.
 
 This API is used to convert from the C `double` type to the JavaScript
-Number type.
+`Number` type.
 
-The JavaScript Number type is described in
+The JavaScript `Number` type is described in
 [Section 6.1.6][] of the ECMAScript Language Specification.
 
 #### napi_create_string_latin1
@@ -1540,13 +1536,14 @@ napi_status napi_create_string_latin1(napi_env env,
 - `[in] str`: Character buffer representing a ISO-8859-1-encoded string.
 - `[in] length`: The length of the string in bytes, or
 `NAPI_AUTO_LENGTH` if it is null-terminated.
-- `[out] result`: A `napi_value` representing a JavaScript String.
+- `[out] result`: A `napi_value` representing a JavaScript `String`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API creates a JavaScript String object from a ISO-8859-1-encoded C string.
+This API creates a JavaScript `String` object from a ISO-8859-1-encoded C
+string.
 
-The JavaScript String type is described in
+The JavaScript `String` type is described in
 [Section 6.1.4][] of the ECMAScript Language Specification.
 
 #### napi_create_string_utf16
@@ -1564,13 +1561,13 @@ napi_status napi_create_string_utf16(napi_env env,
 - `[in] str`: Character buffer representing a UTF16-LE-encoded string.
 - `[in] length`: The length of the string in two-byte code units, or
 `NAPI_AUTO_LENGTH` if it is null-terminated.
-- `[out] result`: A `napi_value` representing a JavaScript String.
+- `[out] result`: A `napi_value` representing a JavaScript `String`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API creates a JavaScript String object from a UTF16-LE-encoded C string
+This API creates a JavaScript `String` object from a UTF16-LE-encoded C string.
 
-The JavaScript String type is described in
+The JavaScript `String` type is described in
 [Section 6.1.4][] of the ECMAScript Language Specification.
 
 #### napi_create_string_utf8
@@ -1588,13 +1585,13 @@ napi_status napi_create_string_utf8(napi_env env,
 - `[in] str`: Character buffer representing a UTF8-encoded string.
 - `[in] length`: The length of the string in bytes, or `NAPI_AUTO_LENGTH`
 if it is null-terminated.
-- `[out] result`: A `napi_value` representing a JavaScript String.
+- `[out] result`: A `napi_value` representing a JavaScript `String`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API creates a JavaScript String object from a UTF8-encoded C string
+This API creates a JavaScript `String` object from a UTF8-encoded C string.
 
-The JavaScript String type is described in
+The JavaScript `String` type is described in
 [Section 6.1.4][] of the ECMAScript Language Specification.
 
 ### Functions to convert from N-API to C types
@@ -1609,7 +1606,7 @@ napi_status napi_get_array_length(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing the JavaScript Array whose length is
+- `[in] value`: `napi_value` representing the JavaScript `Array` whose length is
 being queried.
 - `[out] result`: `uint32` representing length of the array.
 
@@ -1617,7 +1614,7 @@ Returns `napi_ok` if the API succeeded.
 
 This API returns the length of an array.
 
-Array length is described in
+`Array` length is described in
 [Section 22.1.4.1](https://tc39.github.io/ecma262/#sec-properties-of-array-instances-length)
 of the ECMAScript Language Specification.
 
@@ -1633,20 +1630,20 @@ napi_status napi_get_arraybuffer_info(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] arraybuffer`: `napi_value` representing the ArrayBuffer being queried.
-- `[out] data`: The underlying data buffer of the ArrayBuffer.
+- `[in] arraybuffer`: `napi_value` representing the `ArrayBuffer` being queried.
+- `[out] data`: The underlying data buffer of the `ArrayBuffer`.
 - `[out] byte_length`: Length in bytes of the underlying data buffer.
 
 Returns `napi_ok` if the API succeeded.
 
-This API is used to retrieve the underlying data buffer of an ArrayBuffer and
+This API is used to retrieve the underlying data buffer of an `ArrayBuffer` and
 its length.
 
 *WARNING*: Use caution while using this API. The lifetime of the underlying data
-buffer is managed by the ArrayBuffer even after it's returned. A
+buffer is managed by the `ArrayBuffer` even after it's returned. A
 possible safe way to use this API is in conjunction with
 [`napi_create_reference`][], which can be used to guarantee control over the
-lifetime of the ArrayBuffer. It's also safe to use the returned data buffer
+lifetime of the `ArrayBuffer`. It's also safe to use the returned data buffer
 within the same callback as long as there are no calls to other APIs that might
 trigger a GC.
 
@@ -1685,7 +1682,7 @@ napi_status napi_get_prototype(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] object`: `napi_value` representing JavaScript Object whose prototype
+- `[in] object`: `napi_value` representing JavaScript `Object` whose prototype
 to return. This returns the equivalent of `Object.getPrototypeOf` (which is
 not the same as the function's `prototype` property).
 - `[out] result`: `napi_value` representing prototype of the given object.
@@ -1707,20 +1704,20 @@ napi_status napi_get_typedarray_info(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] typedarray`: `napi_value` representing the TypedArray whose
+- `[in] typedarray`: `napi_value` representing the `TypedArray` whose
 properties to query.
-- `[out] type`: Scalar datatype of the elements within the TypedArray.
-- `[out] length`: Number of elements in the TypedArray.
+- `[out] type`: Scalar datatype of the elements within the `TypedArray`.
+- `[out] length`: `Number` of elements in the `TypedArray`.
 - `[out] data`: The data buffer underlying the typed array.
 - `[out] byte_offset`: The byte offset within the data buffer from which
-to start projecting the TypedArray.
+to start projecting the `TypedArray`.
 
 Returns `napi_ok` if the API succeeded.
 
 This API returns various properties of a typed array.
 
 *Warning*: Use caution while using this API since the underlying data buffer
-is managed by the VM
+is managed by the VM.
 
 #### napi_get_dataview_info
 <!-- YAML
@@ -1737,17 +1734,17 @@ napi_status napi_get_dataview_info(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] dataview`: `napi_value` representing the DataView whose
+- `[in] dataview`: `napi_value` representing the `DataView` whose
   properties to query.
-- `[out] byte_length`: Number of bytes in the DataView.
-- `[out] data`: The data buffer underlying the DataView.
-- `[out] arraybuffer`: ArrayBuffer underlying the DataView.
+- `[out] byte_length`: `Number` of bytes in the `DataView`.
+- `[out] data`: The data buffer underlying the `DataView`.
+- `[out] arraybuffer`: `ArrayBuffer` underlying the `DataView`.
 - `[out] byte_offset`: The byte offset within the data buffer from which
-  to start projecting the DataView.
+  to start projecting the `DataView`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns various properties of a DataView.
+This API returns various properties of a `DataView`.
 
 #### napi_get_value_bool
 <!-- YAML
@@ -1758,15 +1755,15 @@ napi_status napi_get_value_bool(napi_env env, napi_value value, bool* result)
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing JavaScript Boolean.
+- `[in] value`: `napi_value` representing JavaScript `Boolean`.
 - `[out] result`: C boolean primitive equivalent of the given JavaScript
-Boolean.
+`Boolean`.
 
 Returns `napi_ok` if the API succeeded. If a non-boolean `napi_value` is
 passed in it returns `napi_boolean_expected`.
 
 This API returns the C boolean primitive equivalent of the given JavaScript
-Boolean.
+`Boolean`.
 
 #### napi_get_value_double
 <!-- YAML
@@ -1779,15 +1776,15 @@ napi_status napi_get_value_double(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing JavaScript Number.
+- `[in] value`: `napi_value` representing JavaScript `Number`.
 - `[out] result`: C double primitive equivalent of the given JavaScript
-Number.
+`Number`.
 
 Returns `napi_ok` if the API succeeded. If a non-number `napi_value` is passed
 in it returns `napi_number_expected`.
 
 This API returns the C double primitive equivalent of the given JavaScript
-Number.
+`Number`.
 
 #### napi_get_value_external
 <!-- YAML
@@ -1820,14 +1817,14 @@ napi_status napi_get_value_int32(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing JavaScript Number.
-- `[out] result`: C int32 primitive equivalent of the given JavaScript Number.
+- `[in] value`: `napi_value` representing JavaScript `Number`.
+- `[out] result`: C int32 primitive equivalent of the given JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded. If a non-number `napi_value`
 is passed in `napi_number_expected`.
 
 This API returns the C int32 primitive equivalent
-of the given JavaScript Number.
+of the given JavaScript `Number`.
 
 If the number exceeds the range of the 32 bit integer, then the result is
 truncated to the equivalent of the bottom 32 bits. This can result in a large
@@ -1847,16 +1844,16 @@ napi_status napi_get_value_int64(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing JavaScript Number.
-- `[out] result`: C int64 primitive equivalent of the given JavaScript Number.
+- `[in] value`: `napi_value` representing JavaScript `Number`.
+- `[out] result`: C int64 primitive equivalent of the given JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded. If a non-number `napi_value`
 is passed in it returns `napi_number_expected`.
 
 This API returns the C int64 primitive equivalent of the given JavaScript
-Number.
+`Number`.
 
-Number values outside the range of
+`Number` values outside the range of
 [`Number.MIN_SAFE_INTEGER`](https://tc39.github.io/ecma262/#sec-number.min_safe_integer)
 -(2^53 - 1) -
 [`Number.MAX_SAFE_INTEGER`](https://tc39.github.io/ecma262/#sec-number.max_safe_integer)
@@ -1886,7 +1883,7 @@ insufficient, the returned string will be truncated.
 - `[out] result`: Number of bytes copied into the buffer, excluding the null
 terminator.
 
-Returns `napi_ok` if the API succeeded. If a non-String `napi_value`
+Returns `napi_ok` if the API succeeded. If a non-`String` `napi_value`
 is passed in it returns `napi_string_expected`.
 
 This API returns the ISO-8859-1-encoded string corresponding the value passed
@@ -1913,7 +1910,7 @@ insufficient, the returned string will be truncated.
 - `[out] result`: Number of bytes copied into the buffer, excluding the null
 terminator.
 
-Returns `napi_ok` if the API succeeded. If a non-String `napi_value`
+Returns `napi_ok` if the API succeeded. If a non-`String` `napi_value`
 is passed in it returns `napi_string_expected`.
 
 This API returns the UTF8-encoded string corresponding the value passed in.
@@ -1939,7 +1936,7 @@ insufficient, the returned string will be truncated.
 - `[out] result`: Number of 2-byte code units copied into the buffer, excluding
 the null terminator.
 
-Returns `napi_ok` if the API succeeded. If a non-String `napi_value`
+Returns `napi_ok` if the API succeeded. If a non-`String` `napi_value`
 is passed in it returns `napi_string_expected`.
 
 This API returns the UTF16-encoded string corresponding the value passed in.
@@ -1955,7 +1952,7 @@ napi_status napi_get_value_uint32(napi_env env,
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[in] value`: `napi_value` representing JavaScript Number.
+- `[in] value`: `napi_value` representing JavaScript `Number`.
 - `[out] result`: C primitive equivalent of the given `napi_value` as a
 `uint32_t`.
 
@@ -1976,13 +1973,13 @@ napi_status napi_get_boolean(napi_env env, bool value, napi_value* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The value of the boolean to retrieve.
-- `[out] result`: `napi_value` representing JavaScript Boolean singleton to
+- `[out] result`: `napi_value` representing JavaScript `Boolean` singleton to
 retrieve.
 
 Returns `napi_ok` if the API succeeded.
 
 This API is used to return the JavaScript singleton object that is used to
-represent the given boolean value
+represent the given boolean value.
 
 #### napi_get_global
 <!-- YAML
@@ -1993,11 +1990,11 @@ napi_status napi_get_global(napi_env env, napi_value* result)
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[out] result`: `napi_value` representing JavaScript Global Object.
+- `[out] result`: `napi_value` representing JavaScript `global` object.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns the global Object.
+This API returns the `global` object.
 
 #### napi_get_null
 <!-- YAML
@@ -2008,11 +2005,11 @@ napi_status napi_get_null(napi_env env, napi_value* result)
 ```
 
 - `[in] env`: The environment that the API is invoked under.
-- `[out] result`: `napi_value` representing JavaScript Null Object.
+- `[out] result`: `napi_value` representing JavaScript `null` object.
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns the null Object.
+This API returns the `null` object.
 
 #### napi_get_undefined
 <!-- YAML
@@ -2037,10 +2034,10 @@ values. Some of these operations are documented under
 of the [ECMAScript Language Specification][].
 
 These APIs support doing one of the following:
-1. Coerce JavaScript values to specific JavaScript types (such as Number or
-   String)
-2. Check the type of a JavaScript value
-3. Check for equality between two JavaScript values
+1. Coerce JavaScript values to specific JavaScript types (such as `Number` or
+   `String`).
+2. Check the type of a JavaScript value.
+3. Check for equality between two JavaScript values.
 
 ### napi_coerce_to_bool
 <!-- YAML
@@ -2054,14 +2051,14 @@ napi_status napi_coerce_to_bool(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to coerce.
-- `[out] result`: `napi_value` representing the coerced JavaScript Boolean.
+- `[out] result`: `napi_value` representing the coerced JavaScript `Boolean`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API implements the abstract operation ToBoolean as defined in
+This API implements the abstract operation `ToBoolean()` as defined in
 [Section 7.1.2](https://tc39.github.io/ecma262/#sec-toboolean)
 of the ECMAScript Language Specification.
-This API can be re-entrant if getters are defined on the passed-in Object.
+This API can be re-entrant if getters are defined on the passed-in `Object`.
 
 ### napi_coerce_to_number
 <!-- YAML
@@ -2075,14 +2072,14 @@ napi_status napi_coerce_to_number(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to coerce.
-- `[out] result`: `napi_value` representing the coerced JavaScript Number.
+- `[out] result`: `napi_value` representing the coerced JavaScript `Number`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API implements the abstract operation ToNumber as defined in
+This API implements the abstract operation `ToNumber()` as defined in
 [Section 7.1.3](https://tc39.github.io/ecma262/#sec-tonumber)
 of the ECMAScript Language Specification.
-This API can be re-entrant if getters are defined on the passed-in Object.
+This API can be re-entrant if getters are defined on the passed-in `Object`.
 
 ### napi_coerce_to_object
 <!-- YAML
@@ -2096,14 +2093,14 @@ napi_status napi_coerce_to_object(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to coerce.
-- `[out] result`: `napi_value` representing the coerced JavaScript Object.
+- `[out] result`: `napi_value` representing the coerced JavaScript `Object`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API implements the abstract operation ToObject as defined in
+This API implements the abstract operation `ToObject()` as defined in
 [Section 7.1.13](https://tc39.github.io/ecma262/#sec-toobject)
 of the ECMAScript Language Specification.
-This API can be re-entrant if getters are defined on the passed-in Object.
+This API can be re-entrant if getters are defined on the passed-in `Object`.
 
 ### napi_coerce_to_string
 <!-- YAML
@@ -2117,14 +2114,14 @@ napi_status napi_coerce_to_string(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to coerce.
-- `[out] result`: `napi_value` representing the coerced JavaScript String.
+- `[out] result`: `napi_value` representing the coerced JavaScript `String`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API implements the abstract operation ToString as defined in
+This API implements the abstract operation `ToString()` as defined in
 [Section 7.1.13](https://tc39.github.io/ecma262/#sec-tostring)
 of the ECMAScript Language Specification.
-This API can be re-entrant if getters are defined on the passed-in Object.
+This API can be re-entrant if getters are defined on the passed-in `Object`.
 
 ### napi_typeof
 <!-- YAML
@@ -2200,11 +2197,11 @@ napi_status napi_is_arraybuffer(napi_env env, napi_value value, bool* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to check.
-- `[out] result`: Whether the given object is an ArrayBuffer.
+- `[out] result`: Whether the given object is an `ArrayBuffer`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in is an array buffer.
+This API checks if the `Object` passed in is an array buffer.
 
 ### napi_is_buffer
 <!-- YAML
@@ -2221,7 +2218,7 @@ object.
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in is a buffer.
+This API checks if the `Object` passed in is a buffer.
 
 ### napi_is_error
 <!-- YAML
@@ -2233,11 +2230,11 @@ napi_status napi_is_error(napi_env env, napi_value value, bool* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to check.
-- `[out] result`: Whether the given `napi_value` represents an Error object.
+- `[out] result`: Whether the given `napi_value` represents an `Error` object.
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in is an Error.
+This API checks if the `Object` passed in is an `Error`.
 
 ### napi_is_typedarray
 <!-- YAML
@@ -2249,11 +2246,11 @@ napi_status napi_is_typedarray(napi_env env, napi_value value, bool* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to check.
-- `[out] result`: Whether the given `napi_value` represents a TypedArray.
+- `[out] result`: Whether the given `napi_value` represents a `TypedArray`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in is a typed array.
+This API checks if the `Object` passed in is a typed array.
 
 ### napi_is_dataview
 <!-- YAML
@@ -2266,11 +2263,11 @@ napi_status napi_is_dataview(napi_env env, napi_value value, bool* result)
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] value`: The JavaScript value to check.
-- `[out] result`: Whether the given `napi_value` represents a DataView.
+- `[out] result`: Whether the given `napi_value` represents a `DataView`.
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in is a DataView.
+This API checks if the `Object` passed in is a `DataView`.
 
 ### napi_strict_equals
 <!-- YAML
@@ -2308,7 +2305,7 @@ following forms:
 - Named: a simple UTF8-encoded string
 - Integer-Indexed: an index value represented by `uint32_t`
 - JavaScript value: these are represented in N-API by `napi_value`. This can
-be a `napi_value` representing a String, Number, or Symbol.
+be a `napi_value` representing a `String`, `Number`, or `Symbol`.
 
 N-API values are represented by the type `napi_value`.
 Any N-API call that requires a JavaScript value takes in a `napi_value`.
@@ -2475,10 +2472,10 @@ typedef struct {
 } napi_property_descriptor;
 ```
 
-- `utf8name`: Optional String describing the key for the property,
+- `utf8name`: Optional `String` describing the key for the property,
 encoded as UTF8. One of `utf8name` or `name` must be provided for the
 property.
-- `name`: Optional napi_value that points to a JavaScript string or symbol
+- `name`: Optional `napi_value` that points to a JavaScript string or symbol
 to be used as the key for the property. One of `utf8name` or `name` must
 be provided for the property.
 - `value`: The value that's retrieved by a get access of the property if the
@@ -2523,7 +2520,7 @@ and [`napi_get_element`][].
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns the array of properties for the Object passed in
+This API returns the array of properties for the `Object` passed in.
 
 #### napi_set_property
 <!-- YAML
@@ -2543,7 +2540,7 @@ napi_status napi_set_property(napi_env env,
 
 Returns `napi_ok` if the API succeeded.
 
-This API set a property on the Object passed in.
+This API set a property on the `Object` passed in.
 
 #### napi_get_property
 <!-- YAML
@@ -2563,8 +2560,7 @@ napi_status napi_get_property(napi_env env,
 
 Returns `napi_ok` if the API succeeded.
 
-This API gets the requested property from the Object passed in.
-
+This API gets the requested property from the `Object` passed in.
 
 #### napi_has_property
 <!-- YAML
@@ -2584,8 +2580,7 @@ napi_status napi_has_property(napi_env env,
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in has the named property.
-
+This API checks if the `Object` passed in has the named property.
 
 #### napi_delete_property
 <!-- YAML
@@ -2608,7 +2603,6 @@ Returns `napi_ok` if the API succeeded.
 
 This API attempts to delete the `key` own property from `object`.
 
-
 #### napi_has_own_property
 <!-- YAML
 added: v8.2.0
@@ -2627,10 +2621,9 @@ napi_status napi_has_own_property(napi_env env,
 
 Returns `napi_ok` if the API succeeded.
 
-This API checks if the Object passed in has the named own property. `key` must
-be a string or a Symbol, or an error will be thrown. N-API will not perform any
-conversion between data types.
-
+This API checks if the `Object` passed in has the named own property. `key` must
+be a string or a `Symbol`, or an error will be thrown. N-API will not perform
+any conversion between data types.
 
 #### napi_set_named_property
 <!-- YAML
@@ -2713,7 +2706,7 @@ napi_status napi_set_element(napi_env env,
 
 Returns `napi_ok` if the API succeeded.
 
-This API sets and element on the Object passed in.
+This API sets and element on the `Object` passed in.
 
 #### napi_get_element
 <!-- YAML
@@ -2753,7 +2746,7 @@ napi_status napi_has_element(napi_env env,
 
 Returns `napi_ok` if the API succeeded.
 
-This API returns if the Object passed in has an element at the
+This API returns if the `Object` passed in has an element at the
 requested index.
 
 #### napi_delete_element
@@ -2796,10 +2789,11 @@ napi_status napi_define_properties(napi_env env,
 Returns `napi_ok` if the API succeeded.
 
 This method allows the efficient definition of multiple properties on a given
-object. The properties are defined using property descriptors (See
+object. The properties are defined using property descriptors (see
 [`napi_property_descriptor`][]). Given an array of such property descriptors,
 this API will set the properties on the object one at a time, as defined by
-DefineOwnProperty (described in [Section 9.1.6][] of the ECMA262 specification).
+`DefineOwnProperty()` (described in [Section 9.1.6][] of the ECMA262
+specification).
 
 ## Working with JavaScript Functions
 
@@ -2819,7 +2813,6 @@ JavaScript functions from native code. One can either call a function
 like a regular JavaScript function call, or as a constructor
 function.
 
-
 ### napi_call_function
 <!-- YAML
 added: v8.0.0
@@ -3209,8 +3202,9 @@ This API may modify the prototype chain of the wrapper object. Afterward,
 additional manipulation of the wrapper's prototype chain may cause
 `napi_unwrap()` to fail.
 
-Calling napi_wrap() a second time on an object will return an error. To
-associate another native instance with the object, use napi_remove_wrap() first.
+Calling `napi_wrap()` a second time on an object will return an error. To
+associate another native instance with the object, use `napi_remove_wrap()`
+first.
 
 ### napi_unwrap
 <!-- YAML
@@ -3286,9 +3280,8 @@ typedef void (*napi_async_complete_callback)(napi_env env,
                                              void* data);
 ```
 
-
 When these methods are invoked, the `data` parameter passed will be the
-addon-provided void* data that was passed into the
+addon-provided `void*` data that was passed into the
 `napi_create_async_work` call.
 
 Once created the async worker can be queued
@@ -3327,7 +3320,7 @@ napi_status napi_create_async_work(napi_env env,
 
 - `[in] env`: The environment that the API is invoked under.
 - `[in] async_resource`: An optional object associated with the async work
-  that will be passed to possible async_hooks [`init` hooks][].
+  that will be passed to possible `async_hooks` [`init` hooks][].
 - `[in] async_resource_name`: Identifier for the kind of resource that is
 being provided for diagnostic information exposed by the `async_hooks` API.
 - `[in] execute`: The native function which should be called to execute
@@ -3513,7 +3506,7 @@ NAPI_EXTERN napi_status napi_open_callback_scope(napi_env env,
 ```
 - `[in] env`: The environment that the API is invoked under.
 - `[in] resource_object`: An optional object associated with the async work
-  that will be passed to possible async_hooks [`init` hooks][].
+  that will be passed to possible `async_hooks` [`init` hooks][].
 - `[in] context`: Context for the async operation that is
 invoking the callback. This should be a value previously obtained
 from [`napi_async_init`][].