docs: remove empty lines

lib/node_modules/@stdlib/datasets/afinn-111/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ArrayArray} word ratings
 *

lib/node_modules/@stdlib/datasets/afinn-96/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ArrayArray} word ratings
 *

lib/node_modules/@stdlib/datasets/anscombes-quartet/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ArrayArray} Anscombe's quartet
 *

lib/node_modules/@stdlib/datasets/berndt-cps-wages-1985/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} data
 *

lib/node_modules/@stdlib/datasets/cdc-nchs-us-births-1969-1988/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} birth data
 *

lib/node_modules/@stdlib/datasets/cdc-nchs-us-births-1994-2003/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} birth data
 *

lib/node_modules/@stdlib/datasets/cdc-nchs-us-infant-mortality-bw-1915-2013/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} infant mortality data
 *

lib/node_modules/@stdlib/datasets/cmudict/lib/main.js

@@ -50,7 +50,6 @@ var fopts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @param {Options} [options] - options object
 * @param {string} [options.data] - dataset name
 * @throws {Error} unable to read data

lib/node_modules/@stdlib/datasets/dale-chall-new/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} words
 *

lib/node_modules/@stdlib/datasets/emoji-code-picto/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Object} codes to pictographs
 *

lib/node_modules/@stdlib/datasets/emoji-picto-code/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Object} pictographs to codes
 *

lib/node_modules/@stdlib/datasets/emoji/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} emoji database
 *

lib/node_modules/@stdlib/datasets/female-first-names-en/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} female first names
 *

lib/node_modules/@stdlib/datasets/fivethirtyeight-ffq/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} FFQ data
 *

lib/node_modules/@stdlib/datasets/frb-sf-wage-rigidity/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} data
 *

lib/node_modules/@stdlib/datasets/harrison-boston-house-prices-corrected/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} housing data
 *

lib/node_modules/@stdlib/datasets/harrison-boston-house-prices/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} housing data
 *

lib/node_modules/@stdlib/datasets/herndon-venus-semidiameters/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {NumberArray} data
 *

lib/node_modules/@stdlib/datasets/img-acanthus-mollis/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-airplane-from-above/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-allium-oreophilum/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-black-canyon/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-dust-bowl-home/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-french-alpine-landscape/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-locomotion-house-cat/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-locomotion-nude-male/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-march-pastoral/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/img-nagasaki-boats/lib/main.js

@@ -38,7 +38,6 @@ var fpath = resolve( __dirname, '..', 'data', 'image.jpg' );
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {Buffer} image
 *

lib/node_modules/@stdlib/datasets/liu-negative-opinion-words-en/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} words
 *

lib/node_modules/@stdlib/datasets/liu-positive-opinion-words-en/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} words
 *

lib/node_modules/@stdlib/datasets/male-first-names-en/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} male first names
 *

lib/node_modules/@stdlib/datasets/minard-napoleons-march/lib/main.js

@@ -51,7 +51,6 @@ var fopts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @param {Options} [options] - options object
 * @param {string} [options.data] - dataset name
 * @throws {Error} unable to read data

lib/node_modules/@stdlib/datasets/moby-dick/lib/main.js

@@ -44,7 +44,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} data
 *

lib/node_modules/@stdlib/datasets/month-names-en/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} month names
 *

lib/node_modules/@stdlib/datasets/nightingales-rose/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} dataset
 *

lib/node_modules/@stdlib/datasets/pace-boston-house-prices/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {ObjectArray} housing data
 *

lib/node_modules/@stdlib/datasets/primes-100k/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {PositiveIntegerArray} primes
 *

lib/node_modules/@stdlib/datasets/savoy-stopwords-fin/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} stop words
 *

lib/node_modules/@stdlib/datasets/savoy-stopwords-fr/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} stop words
 *

lib/node_modules/@stdlib/datasets/savoy-stopwords-ger/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} stop words
 *

lib/node_modules/@stdlib/datasets/savoy-stopwords-it/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} stop words
 *

lib/node_modules/@stdlib/datasets/savoy-stopwords-por/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} stop words
 *

lib/node_modules/@stdlib/datasets/savoy-stopwords-sp/lib/main.js

@@ -41,7 +41,6 @@ var opts = {
 *
 * -   This function synchronously reads data from disk for each invocation. Such behavior is intentional and so is the avoidance of `require`. We assume that invocations are infrequent, and we want to avoid the `require` cache. This means that we allow data to be garbage collected and a user is responsible for explicitly caching data.
 *
-*
 * @throws {Error} unable to read data
 * @returns {StringArray} stop words
 *