diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 927e8f8..25410ad 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -51,7 +51,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node_version: [8, 10, 12, 14, 16, 18, 20]
+        node_version: [10, 12, 14, 16, 18, 20]
 
     steps:
       - uses: actions/checkout@v4
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0f8e062..fc461ee 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -8,14 +8,14 @@ If you're filing a feature request, please remember:
 * Feature requests significantly expanding the scope of loglevel outside the description in [the readme](https://github.com/pimterry/loglevel/blob/master/README.md) will probably be rejected.
 * Features that can't be meaningfully implemented in a cross-environment compatible manner won't be implemented.
 * Please check the previously opened issues to see if somebody else has suggested it first.
-* Consider submitting a pull request to add the feature instead, if you're confident it fits within the above
+* Consider submitting a pull request to add the feature instead, if you're confident it fits within the above.
 
 If you're filing a bug, please remember:
 
-* To provide detailed steps to reproduce the behaviour
-* If possible, provide a Jasmine test which reproduces the behaviour
-* Please specify the exact details of the environment in which it fails: OS + Environment (i.e. Browser or Node) + version
-* Consider submitting a pull request to fix the bug instead
+* To provide detailed steps to reproduce the behaviour.
+* If possible, provide a Jasmine test which reproduces the behaviour.
+* Please specify the exact details of the environment in which it fails: OS + Environment (i.e. Browser or Node) + version.
+* Consider submitting a pull request to fix the bug instead.
 
 Helping develop loglevel
 ================================
@@ -26,38 +26,71 @@ Before submitting a pull request to fix a bug or add a new feature, please check
 
 To be more specific, before submitting your pull request please ensure:
 
-* You haven't broken the existing test suite in any obvious browsers (at least check latest IE/FF/Chrome)
-* You've added relevant tests for the bug you're fixing/the new feature you're adding/etc, which pass in all the relevant browsers
-* JSHint is happy with your new code
-* You've updated the API docs (in README.md) to detail any changes you've made to the public interface
-* Your change is backward compatible (or you've explicitly said if it's not; this isn't great, but will be considered)
-* You haven't changed any files in dist/ (these are auto-generated, and should only be changed on release)
+* You haven't broken the existing test suite in any obvious browsers (at least check latest IE/FF/Chrome).
+* You've added relevant tests for the bug you're fixing/the new feature you're adding/etc, which pass in all the relevant browsers.
+* JSHint is happy with your new code.
+* You've updated the API docs (in `README.md`) to detail any changes you've made to the public interface.
+* Your change is backward-compatible (or you've explicitly said that it's not; this isn't great, but will be considered).
+* You haven't changed any files in `dist/` (these are auto-generated, and should only be changed on release).
+
+Compatibility and JavaScript Runtimes
+-------------------------------------
+
+loglevel aims to stay compatible with browsers, Node.js versions, and other JS runtimes that may be fairly old at this point! Please take care to match existing conventions and JavaScript language features wherever possible. For example, loglevel uses `var` instead of the newer `let` and `const` keywords to define variables, uses old-style `for` loops instead of the newer `for...of` loop, and so on.
+
+That said, loglevel's *test and development tools* utilize newer JavaScript and Node.js features. To run most tests or build releases, you will need a newer version of Node.js than is required at runtime (see details below in ["how to make your change…"](#how-to-make-your-change-and-submit-it)). Using newer features or making breaking changes to the *dev tools* is OK.
 
 Project structure
 -----------------
 
-The core project code is all in lib/loglevel.js, and this should be the only file you need to touch for functional changes themselves.
+The core project code is all in [`lib/loglevel.js`](./lib/loglevel.js), and this should be the only file you need to touch for functional changes themselves.
 
-The released code is in dist/*.js, and should not be touched by anything except releases
+The released code is in `dist/*.js`, and should not be touched by anything except releases (pull requests should *not* update these files).
 
-The test suite is entirely in test/*.js:
+The test suite is entirely in `test/*.js`:
 
-* Every file ending in '-test.js' is a unit test, is written in RequireJS, and should pass in any environment
-* global-integration.js and node-integration.js are quick integration smoke tests for node and for browser global usage
-* test-helpers.js contains some test utilities
-* manual-test.html is a test page which includes the current loglevel build, so you can manually check it works in a given browser
+* Every file ending in `-test.js` is a unit test, is written in RequireJS, and should pass in any environment.
+* `global-integration.js` and `node-integration.js` are quick integration smoke tests for node and for browser global usage.
+* `test-helpers.js` contains some test utilities.
+* `manual-test.html` is a test page which includes the current loglevel build, so you can manually check that it works in a given browser.
 
 How to make your change and submit it
 -------------------------------------
 
-1. Fork loglevel
-2. Clone your fork locally
-3. Create a branch from master for your change
-4. Write some tests in /test for your change, as relevant
-5. Make your code changes in /lib/loglevel.js
-6. Check your code all passes (run `grunt`) - if you have any issues try running `grunt jasmine:requirejs:src:build` (or a different test build instead of 'requirejs': see the jasmine config in Gruntfile.js) and debugging the generated _SpecRunner.html in a browser
-7. Commit your changes
-8. Open a pull request back to master in loglevel
+1. Ensure you have Node.js v14 or later (some tests can run on earlier versions, but the full suite requires this version).
+2. Fork loglevel.
+3. Clone your fork locally.
+4. Create a branch from `master` for your change.
+5. Write some tests in `test/` for your change, as relevant.
+6. Make your code changes in `lib/loglevel.js`.
+7. Check your code all passes (run `npm test`). If you have issues and need to debug the tests, see the details on ["running tests"](#running-tests) below.
+8. Commit your changes.
+9. Open a pull request back to `master` in loglevel.
+
+Running Tests
+-------------
+
+There are several types of tests and test tools that loglevel uses to verify different types of support in different environments. When you run `npm test`, *all* of these tests are run automatically. However, you may want to run individual types of tests during development, or run some tests manually to debug them.
+
+Test commands (see `"scripts"` in `package.json` for a complete list of tools):
+- `npm test` — Runs all the below tests.
+- `npm run test-browser` — Runs detailed tests in a headless browser. There are actually 3 sub-groups here:
+    - `npx grunt jasmine:global` — Tests general usage of the global `log` variable.
+    - `npx grunt test-browser-context` — Tests usage when loglevel is injected into an anonymous function instead of included as a regular script on the page.
+    - `npx grunt jasmine:requirejs` — Tests the main test suite via Jasmine & RequireJS.
+- `npm run test-node` — Runs tests that check loglevel in Node.js.
+- `npm run test-types` — Runs tests of the TypeScript type definitions for loglevel.
+
+Alternatively, you might want to run tests manually in your browser in order to use debugging tools to step through the code:
+1. Run `npx grunt integration-test` to start a test server on port `8000`.
+2. Your default browser should open the tests automatically, but if not, open `http://127.0.0.1:8000/_SpecRunner.html` in any browser.
+3. Open your browser's dev tools and place breakpoints where you'd like to debug a test.
+4. Reload the page to re-run the tests and pause on breakpoints.
+
+You can also open a blank webpage with loglevel pre-loaded to experiment in your browser's console:
+1. Run `npx grunt integration-test` to start a test server on port `8000`.
+2. In whatever browser you want to test, open `http://127.0.0.1:8000/test/manual-test.html`.
+3. Play around with the global `log` object in the browser's dev console.
 
 Reporting security issues
 -------------------------
diff --git a/Gruntfile.js b/Gruntfile.js
index 21c44a7..5af9f54 100644
--- a/Gruntfile.js
+++ b/Gruntfile.js
@@ -153,7 +153,8 @@ module.exports = function (grunt) {
 
     // Check everything is good
     grunt.registerTask('test', ['jshint', 'test-browser', 'test-node']);
-    grunt.registerTask('test-browser', ['jasmine:global', 'preprocess', 'jasmine:context', 'clean:test', 'jasmine:requirejs']);
+    grunt.registerTask('test-browser', ['jasmine:global', 'test-browser-context', 'jasmine:requirejs']);
+    grunt.registerTask('test-browser-context', ['preprocess', 'jasmine:context', 'clean:test']);
     grunt.registerTask('test-node', ['jasmine_node']);
 
     // Test with a live server and an actual browser
diff --git a/README.md b/README.md
index a523c18..31fe26c 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@
 
 > _Don't debug with logs alone - check out [HTTP Toolkit](https://httptoolkit.tech/javascript): beautiful, powerful & open-source tools for building, testing & debugging HTTP(S)_
 
-Minimal lightweight simple logging for JavaScript (browsers, node.js or elsewhere). loglevel extends console.log() & friends with level-based logging and filtering, with none of console's downsides.
+Minimal lightweight simple logging for JavaScript (browsers, node.js or elsewhere). loglevel extends `console.log()` & friends with level-based logging and filtering, with none of console's downsides.
 
 Test it out live in your browser console at https://pimterry.github.io/loglevel/demo/index.html
 
@@ -16,24 +16,24 @@ Loglevel is a barebones reliable everyday logging library. It does not do fancy
 
 ### Simple
 
-* Log things at a given level (trace/debug/info/warn/error) to the console object (as seen in all modern browsers & node.js)
-* Filter logging by level (all the above or 'silent'), so you can disable all but error logging in production, and then run log.setLevel("trace") in your console to turn it all back on for a furious debugging session
-* Single file, no dependencies, weighs in at 1.1KB minified and gzipped
+* Log things at a given level (trace/debug/info/warn/error) to the `console` object (as seen in all modern browsers & node.js).
+* Filter logging by level (all the above or 'silent'), so you can disable all but error logging in production, and then run `log.setLevel("trace")` in your console to turn it all back on for a furious debugging session.
+* Single file, no dependencies, weighs in at 1.4 KB minified and gzipped.
 
 ### Effective
 
-* Log methods gracefully fall back to simpler console logging methods if more specific ones aren't available: so calls to log.debug() go to console.debug() if possible, or console.log() if not
-* Logging calls still succeed even if there's no console object at all, so your site doesn't break when people visit with old browsers that don't support the console object (here's looking at you IE) and similar
-* This then comes together giving a consistent reliable API that works in every JavaScript environment with a console available, and never breaks anything anywhere else
+* Log methods gracefully fall back to simpler console logging methods if more specific ones aren't available: so calls to `log.debug()` go to `console.debug()` if possible, or `console.log()` if not.
+* Logging calls still succeed even if there's no `console` object at all, so your site doesn't break when people visit with old browsers that don't support the `console` object (here's looking at you, IE) and similar.
+* This then comes together giving a consistent reliable API that works in every JavaScript environment with a console available, and never breaks anything anywhere else.
 
 ### Convenient
 
-* Log output keeps line numbers: most JS logging frameworks call console.log methods through wrapper functions, clobbering your stacktrace and making the extra info many browsers provide useless. We'll have none of that thanks.
-* It works with all the standard JavaScript loading systems out of the box (CommonJS, AMD, or just as a global)
-* Logging is filtered to "warn" level by default, to keep your live site clean in normal usage (or you can trivially re-enable everything with an initial log.enableAll() call)
-* Magically handles situations where console logging is not initially available (IE8/9), and automatically enables logging as soon as it does become available (when developer console is opened)
-* TypeScript type definitions included, so no need for extra `@types` packages
-* Extensible, to add other log redirection, filtering, or formatting functionality, while keeping all the above (except you will clobber your stacktrace, see Plugins below)
+* Log output keeps line numbers: most JS logging frameworks call `console.log` methods through wrapper functions, clobbering your stacktrace and making the extra info many browsers provide useless. We'll have none of that thanks.
+* It works with all the standard JavaScript loading systems out of the box (CommonJS, AMD, or just as a global).
+* Logging is filtered to "warn" level by default, to keep your live site clean in normal usage (or you can trivially re-enable everything with an initial `log.enableAll()` call).
+* Magically handles situations where console logging is not initially available (IE8/9), and automatically enables logging as soon as it does become available (when developer console is opened).
+* TypeScript type definitions included, so no need for extra `@types` packages.
+* Extensible, to add other log redirection, filtering, or formatting functionality, while keeping all the above (except you will clobber your stacktrace, see [“Plugins”](#plugins) below).
 
 ## Downloading loglevel
 
@@ -51,7 +51,7 @@ Finally, if you want to tweak loglevel to your own needs or you immediately need
 
 ## Setting it up
 
-loglevel supports AMD (e.g. RequireJS), CommonJS (e.g. Node.js) and direct usage (e.g. loading globally with a <script> tag) loading methods. You should be able to do nearly anything, and then skip to the next section anyway and have it work. Just in case though, here's some specific examples that definitely do the right thing:
+loglevel supports AMD (e.g. RequireJS), CommonJS (e.g. Node.js) and direct usage (e.g. loading globally with a `<script>` tag) loading methods. You should be able to do nearly anything, and then skip to the next section anyway and have it work. Just in case, though, here's some specific examples that definitely do the right thing:
 
 ### CommonsJS (e.g. Node)
 
@@ -79,7 +79,7 @@ log.warn("too easy");
 
 ### As an ES6 module
 
-loglevel is written as a UMD module, with a single object exported. Unfortunately ES6 module loaders & transpilers don't all handle this the same way. Some will treat the object as the default export, while others use it as the root exported object. In addition, loglevel includes `default` property on the root object, designed to help handle this differences. Nonetheless, there's two possible syntaxes that might work for you:
+loglevel is written as a UMD module, with a single object exported. Unfortunately, ES6 module loaders & transpilers don't all handle this the same way. Some will treat the object as the default export, while others use it as the root exported object. In addition, loglevel includes a `default` property on the root object, designed to help handle this difference. Nonetheless, there are two possible syntaxes that might work for you:
 
 For most tools, using the default import is the most convenient and flexible option:
 
@@ -99,7 +99,7 @@ There's no major difference, unless you're using TypeScript & building a logleve
 
 ### With noConflict()
 
-If you're using another JavaScript library that exposes a 'log' global, you can run into conflicts with loglevel.  Similarly to jQuery, you can solve this by putting loglevel into no-conflict mode immediately after it is loaded onto the page. This resets to 'log' global to its value before loglevel was loaded (typically `undefined`), and returns the loglevel object, which you can then bind to another name yourself.
+If you're using another JavaScript library that exposes a `log` global, you can run into conflicts with loglevel. Similarly to jQuery, you can solve this by putting loglevel into no-conflict mode immediately after it is loaded onto the page. This resets the `log` global to its value before loglevel was loaded (typically `undefined`), and returns the loglevel object, which you can then bind to another name yourself.
 
 For example:
 
@@ -132,7 +132,7 @@ If you really want to use LogLevel as a global however, but from TypeScript, you
 
 ### Methods
 
-The loglevel API is extremely minimal. All methods are available on the root loglevel object, which it's suggested you name 'log' (this is the default if you import it in globally, and is what's set up in the above examples). The API consists of:
+The loglevel API is extremely minimal. All methods are available on the root loglevel object, which we suggest you name `log` (this is the default if you import it globally, and is what's set up in the above examples). The API consists of:
 
 #### Logging Methods
 
@@ -146,11 +146,11 @@ The loglevel API is extremely minimal. All methods are available on the root log
 
 `log.log(msg)` is also available, as an alias for `log.debug(msg)`, to improve compatibility with `console`, and make migration easier.
 
-Exact output formatting of these will depend on the console available in the current context of your application. For example, many environments will include a full stack trace with all trace() calls, and icons or similar to highlight other calls.
+Exact output formatting of these will depend on the console available in the current context of your application. For example, many environments will include a full stack trace with all `trace()` calls, and icons or similar to highlight other calls.
 
-These methods should never fail in any environment, even if no console object is currently available, and should always fall back to an available log method even if the specific method called (e.g. warn) isn't available.
+These methods should never fail in any environment, even if no `console` object is currently available, and should always fall back to an available log method even if the specific method called (e.g. `warn`) isn't available.
 
-Be aware that all this means that these method won't necessarily always produce exactly the output you expect in every environment; loglevel only guarantees that these methods will never explode on you, and that it will call the most relevant method it can find, with your argument. For example, `log.trace(msg)` in Firefox before version 64 prints the stacktrace by itself, and doesn't include your message (see [#84](https://github.com/pimterry/loglevel/issues/84)).
+Be aware that this means that these methods won't always produce exactly the output you expect in every environment; loglevel only guarantees that these methods will never explode on you, and that it will call the most relevant method it can find, with your argument. For example, `log.trace(msg)` in Firefox before version 64 prints the stacktrace by itself, and doesn't include your message (see [#84](https://github.com/pimterry/loglevel/issues/84)).
 
 #### `log.setLevel(level, [persist])`
 
@@ -162,15 +162,15 @@ This can take either a log level name or `'silent'` (which disables everything)
 * As a string, like `'error'` (case-insensitive) ← _for a reasonable practical balance_
 * As a numeric index from `0` (trace) to `5` (silent) ← _deliciously terse, and more easily programmable (...although, why?)_
 
-Where possible, the log level will be persisted. LocalStorage will be used if available, falling back to cookies if not. If neither is available in the current environment (i.e. in Node), or if you pass `false` as the optional 'persist' second argument, persistence will be skipped.
+Where possible, the log level will be persisted. LocalStorage will be used if available, falling back to cookies if not. If neither is available in the current environment (e.g. in Node), or if you pass `false` as the optional 'persist' second argument, persistence will be skipped.
 
-If `log.setLevel()` is called when a console object is not available (in IE 8 or 9 before the developer tools have been opened, for example) logging will remain silent until the console becomes available, and then begin logging at the requested level.
+If `log.setLevel()` is called when a `console` object is not available (in IE 8 or 9 before the developer tools have been opened, for example) logging will remain silent until the console becomes available, and then begin logging at the requested level.
 
 #### `log.setDefaultLevel(level)`
 
-This sets the current log level only if one has not been persisted and can’t be loaded. This is useful when initializing modules or scripts; if a developer or user has previously called `setLevel()`, this won’t alter their settings. For example, your application might set the log level to `error` in a production environment, but when debugging an issue, you might call `setLevel("trace")` on the console to see all the logs. If that `error` setting was set using `setDefaultLevel()`, it will still stay as `trace` on subsequent page loads and refreshes instead of resetting to `error`.
+This sets the current log level only if one has not been persisted and can’t be loaded. This is useful when initializing modules or scripts; if a developer or user has previously called `setLevel()`, this won’t alter their settings. For example, your application might use `setDefaultLevel("error")` set the log level to `error` in a production environment, but when debugging an issue, you might call `setLevel("trace")` on the console to see all the logs. If that `error` setting was set using `setDefaultLevel()`, it will still stay as `trace` on subsequent page loads and refreshes instead of resetting to `error`.
 
-The `level` argument takes is the same values that you might pass to `setLevel()`. Levels set using `setDefaultLevel()` never persist to subsequent page loads.
+The `level` argument takes the same values that you might pass to `setLevel()`. Levels set using `setDefaultLevel()` never persist to subsequent page loads.
 
 #### `log.resetLevel()`
 
@@ -178,11 +178,11 @@ This resets the current log level to the logger's default level (if no explicit
 
 #### `log.enableAll()` and `log.disableAll()`
 
-These enable or disable all log messages, and are equivalent to log.setLevel("trace") and log.setLevel("silent") respectively.
+These enable or disable all log messages, and are equivalent to `log.setLevel("trace")` and `log.setLevel("silent")`, respectively.
 
 #### `log.getLevel()`
 
-Returns the current logging level, as a number from 0 (trace) to 5 (silent)
+Returns the current logging level, as a number from `0` (trace) to `5` (silent)
 
 It's very unlikely you'll need to use this for normal application logging; it's provided partly to help plugin development, and partly to let you optimize logging code as below, where debug data is only generated if the level is set such that it'll actually be logged. This probably doesn't affect you, unless you've run profiling on your code and you have hard numbers telling you that your log data generation is a real performance problem.
 
@@ -193,11 +193,11 @@ if (log.getLevel() <= log.levels.DEBUG) {
 }
 ```
 
-This notably isn't the right solution to avoid the cost of string concatenation in your logging. Firstly, it's very unlikely that string concatenation in your logging is really an important performance problem. Even if you do genuinely have hard metrics showing that it is though, the better solution that wrapping your log statements in this is to use multiple arguments, as below. The underlying console API will automatically concatenate these for you if logging is enabled, and if it isn't then all log methods are no-ops, and no concatenation will be done at all.
+This notably isn't the right solution to avoid the cost of string concatenation in your logging. Firstly, it's very unlikely that string concatenation in your logging is really an important performance problem. Even if you do genuinely have hard metrics showing that it is, though, the better solution that wrapping your log statements in this is to use multiple arguments, as below. The underlying console API will automatically concatenate these for you if logging is enabled, and if it isn't then all log methods are no-ops, and no concatenation will be done at all.
 
 ```javascript
 // Prints 'My concatenated log message'
-log.debug("My ", "concatenated ", "log message");
+log.debug("My", "concatenated", "log message");
 ```
 
 #### `log.getLogger(loggerName)`
@@ -237,13 +237,13 @@ moduleTwo.doSomethingSpecial();
 
 Loggers returned by `getLogger()` support all the same properties and methods as the default root logger, excepting `noConflict()` and the `getLogger()` method itself.
 
-Like the root logger, other loggers can have their logging level saved. If a logger’s level has not been saved, it will inherit the root logger’s level when it is first created. If the root logger’s level changes later, the new level will not affect other loggers that have already been created. Loggers with Symbol names (rather than string names) will be always considered as unique instances, and will never have their logging level saved or restored.
+Like the root logger, other loggers can have their logging level saved. If a logger’s level has not been saved, it will inherit the root logger’s level when it is first created. If the root logger’s level changes later, the new level will not affect other loggers that have already been created. Loggers with Symbol names (rather than string names) will always be considered unique instances, and will never have their logging level saved or restored.
 
-Likewise, loggers will inherit the root logger’s `methodFactory`. After creation, each logger can have its `methodFactory` independently set. See the _plugins_ section below for more about `methodFactory`.
+Likewise, loggers inherit the root logger’s `methodFactory`. After creation, each logger can have its `methodFactory` independently set. See the _plugins_ section below for more about `methodFactory`.
 
 #### `log.getLoggers()`
 
-This will return you the dictionary of all loggers created with `getLogger`, keyed off of their names.
+This will return the dictionary of all loggers created with `getLogger()`, keyed by their names.
 
 #### `log.rebuild()`
 
@@ -281,17 +281,17 @@ childLogger2.getLevel();  // TRACE (no longer inheriting because `.setDefaultLev
 
 [loglevel-plugin-remote](https://github.com/kutuluk/loglevel-plugin-remote) - plugin for sending loglevel messages to a remote log server.
 
-ServerSend - <https://github.com/artemyarulin/loglevel-serverSend> - Forward your log messages to a remote server.
+[loglevel-serverSend](https://github.com/artemyarulin/loglevel-serverSend) - Forward your log messages to a remote server.
 
-DEBUG - <https://github.com/vectrlabs/loglevel-debug> - Control logging from a DEBUG environmental variable (similar to the classic [Debug](https://github.com/visionmedia/debug) module)
+[loglevel-debug](https://github.com/vectrlabs/loglevel-debug) - Control logging from a DEBUG environmental variable (similar to the classic [Debug](https://github.com/visionmedia/debug) module).
 
 ### Writing plugins
 
-Loglevel provides a simple reliable minimal base for console logging that works everywhere. This means it doesn't include lots of fancy functionality that might be useful in some cases, such as log formatting and redirection (e.g. also sending log messages to a server over AJAX)
+Loglevel provides a simple, reliable, minimal base for console logging that works everywhere. This means it doesn't include lots of fancy functionality that might be useful in some cases, such as log formatting and redirection (e.g. also sending log messages to a server over AJAX)
 
-Including that would increase the size and complexity of the library, but more importantly would remove stacktrace information. Currently log methods are either disabled, or enabled with directly bound versions of the console.log methods (where possible). This means your browser shows the log message as coming from your code at the call to `log.info("message!")` not from within loglevel, since it really calls the bound console method directly, without indirection. The indirection required to dynamically format, further filter, or redirect log messages would stop this.
+Including that would increase the size and complexity of the library, but more importantly would remove stacktrace information. Currently log methods are either disabled, or enabled with directly bound versions of the `console.log` methods (where possible). This means your browser shows the log message as coming from your code at the call to `log.info("message!")` not from within loglevel, since it really calls the bound console method directly, without indirection. The indirection required to dynamically format, further filter, or redirect log messages would stop this.
 
-There's clearly enough enthusiasm for this even at that cost though that loglevel now includes a plugin API. To use it, redefine `log.methodFactory(methodName, logLevel, loggerName)` with a function of your own. This will be called for each enabled method each time the level is set (including initially), and should return a function to be used for the given log method `methodName`, at the given _configured_ (not actual) level `logLevel`, for a logger with the given name `loggerName`. If you'd like to retain all the reliability and features of loglevel, it's recommended that this wraps the initially provided value of `log.methodFactory`.
+There's clearly enough enthusiasm for this even at that cost that loglevel now includes a plugin API. To use it, redefine `log.methodFactory(methodName, logLevel, loggerName)` with a function of your own. This will be called for each enabled method each time the level is set (including initially), and should return a function to be used for the given log method `methodName`, at the given _configured_ (not actual) level `logLevel`, for a logger with the given name `loggerName`. If you'd like to retain all the reliability and features of loglevel, we recommended that you wrap the initially provided value of `log.methodFactory`.
 
 For example, a plugin to prefix all log messages with "Newsflash: " would look like:
 
@@ -309,26 +309,26 @@ log.rebuild(); // Be sure to call the rebuild method in order to apply plugin.
 
 *(The above supports only a single string `log.warn("...")` argument for clarity, but it's easy to extend to a [fuller variadic version](http://jsbin.com/xehoye/edit?html,console).)*
 
-If you develop and release a plugin, please get in contact! I'd be happy to reference it here for future users. Some consistency is helpful; naming your plugin 'loglevel-PLUGINNAME' (e.g. loglevel-newsflash) is preferred, as is giving it the 'loglevel-plugin' keyword in your package.json
+If you develop and release a plugin, please get in contact! I'd be happy to reference it here for future users. Some consistency is helpful; naming your plugin 'loglevel-PLUGINNAME' (e.g. loglevel-newsflash) is preferred, as is giving it the 'loglevel-plugin' keyword in your `package.json`.
 
 ## Developing & Contributing
 
 In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality.
 
-Builds can be run with npm: run `npm run dist` to build a distributable version of the project (in /dist), or `npm test` to just run the tests and linting. During development you can run `npm run watch` and it will monitor source files, and rerun the tests and linting as appropriate when they're changed.
+Builds can be run with npm: run `npm run dist` to build a distributable version of the project (in `dist/`), or `npm test` to just run the tests and linting. During development you can run `npm run watch` and it will monitor source files, and rerun the tests and linting as appropriate when they're changed.
 
-_Also, please don't manually edit files in the "dist" subdirectory as they are generated via Grunt. You'll find source code in the "lib" subdirectory!_
+_Also, please don't manually edit files in the `dist/` subdirectory as they are generated via Grunt. You'll find source code in the `lib/` subdirectory!_
 
 #### Release process
 
 To do a release of loglevel:
 
-* Update the version number in package.json and bower.json
-* Run `npm run dist` to build a distributable version in dist/
-* Update the release history in this file (below)
-* Commit the built code, tagging it with the version number and a brief message about the release
-* Push to Github
-* Run `npm publish .` to publish to NPM
+* Update the version number in `package.json` and `bower.json`.
+* Run `npm run dist` to build a distributable version in `dist/`.
+* Update the release history in this file (below).
+* Commit the built code, tagging it with the version number and a brief message about the release.
+* Push to Github.
+* Run `npm publish .` to publish to NPM.
 
 ## Release History
 
@@ -336,7 +336,7 @@ v0.1.0 - First working release with apparent compatibility with everything teste
 
 v0.2.0 - Updated release with various tweaks and polish and real proper documentation attached
 
-v0.3.0 - Some bugfixes (#12, #14), cookie-based log level persistence, doc tweaks, support for Bower and JamJS
+v0.3.0 - Some bugfixes ([#12](https://github.com/pimterry/loglevel/issues/12), [#14](https://github.com/pimterry/loglevel/issues/14)), cookie-based log level persistence, doc tweaks, support for Bower and JamJS
 
 v0.3.1 - Fixed incorrect text in release build banner, various other minor tweaks
 
@@ -344,27 +344,27 @@ v0.4.0 - Use LocalStorage for level persistence if available, compatibility impr
 
 v0.5.0 - Fix for Modernizr+IE8 issues, improved setLevel error handling, support for auto-activation of desired logging when console eventually turns up in IE8
 
-v0.6.0 - Handle logging in Safari private browsing mode (#33), fix TRACE level persistence bug (#35), plus various minor tweaks
+v0.6.0 - Handle logging in Safari private browsing mode ([#33](https://github.com/pimterry/loglevel/issues/33)), fix `TRACE` level persistence bug ([#35](https://github.com/pimterry/loglevel/issues/35)), plus various minor tweaks
 
-v1.0.0 - Official stable release! Fixed a bug with localStorage in Android webviews, improved CommonJS detection, and added noConflict().
+v1.0.0 - Official stable release! Fixed a bug with localStorage in Android webviews, improved CommonJS detection, and added `noConflict()`.
 
-v1.1.0 - Added support for including loglevel with preprocessing and .apply() (#50), and fixed QUnit dep version which made tests potentially unstable.
+v1.1.0 - Added support for including loglevel with preprocessing and `.apply()` ([#50](https://github.com/pimterry/loglevel/issues/50)), and fixed QUnit dep version which made tests potentially unstable.
 
 v1.2.0 - New plugin API! Plus various bits of refactoring and tidy up, nicely simplifying things and trimming the size down.
 
-v1.3.0 - Make persistence optional in setLevel, plus lots of documentation updates and other small tweaks
+v1.3.0 - Make persistence optional in `setLevel()`, plus lots of documentation updates and other small tweaks
 
-v1.3.1 - With the new optional persistence, stop unnecessarily persisting the initially set default level (warn)
+v1.3.1 - With the new optional persistence, stop unnecessarily persisting the initially set default level (`WARN`)
 
-v1.4.0 - Add getLevel(), setDefaultLevel() and getLogger() functionality for more fine-grained log level control
+v1.4.0 - Add `getLevel()`, `setDefaultLevel()` and `getLogger()` functionality for more fine-grained log level control
 
-v1.4.1 - Reorder UMD (#92) to improve bundling tool compatibility
+v1.4.1 - Reorder UMD ([#92](https://github.com/pimterry/loglevel/issues/92)) to improve bundling tool compatibility
 
-v1.5.0 - Fix log.debug (#111) after V8 changes deprecating console.debug, check for `window` upfront (#104), and add `.log` alias for `.debug` (#64)
+v1.5.0 - Fix `log.debug` ([#111](https://github.com/pimterry/loglevel/issues/111)) after V8 changes deprecating console.debug, check for `window` upfront ([#104](https://github.com/pimterry/loglevel/issues/104)), and add `.log` alias for `.debug` ([#64](https://github.com/pimterry/loglevel/issues/64))
 
-v1.5.1 - Fix bug (#112) in level-persistence cookie fallback, which failed if it wasn't the first cookie present
+v1.5.1 - Fix bug ([#112](https://github.com/pimterry/loglevel/issues/112)) in level-persistence cookie fallback, which failed if it wasn't the first cookie present
 
-v1.6.0 - Add a name property to loggers and add log.getLoggers() (#114), and recommend unpkg as CDN instead of CDNJS.
+v1.6.0 - Add a name property to loggers and add `log.getLoggers()` ([#114](https://github.com/pimterry/loglevel/issues/114)), and recommend unpkg as CDN instead of CDNJS.
 
 v1.6.1 - Various small documentation & test updates
 
@@ -372,9 +372,9 @@ v1.6.2 - Include TypeScript type definitions in the package itself
 
 v1.6.3 - Avoid TypeScript type conflicts with other global `log` types (e.g. `core-js`)
 
-v1.6.4 - Ensure package.json's 'main' is a fully qualified path, to fix webpack issues
+v1.6.4 - Ensure `package.json`'s `"main"` is a fully qualified path, to fix webpack issues
 
-v1.6.5 - Ensure the provided message is included when calling trace() in IE11
+v1.6.5 - Ensure the provided message is included when calling `trace()` in IE11
 
 v1.6.6 - Fix bugs in v1.6.5, which caused issues in node.js & IE < 9
 
@@ -388,7 +388,7 @@ v1.7.1 - Update TypeScript types to support Symbol-named loggers.
 
 v1.8.0 - Add `resetLevel()` method to clear persisted levels & reset to defaults
 
-v1.8.1 - Fix incorrect type definitions for MethodFactory
+v1.8.1 - Fix incorrect type definitions for `MethodFactory`
 
 v1.9.0 - Added `rebuild()` method, overhaul dev & test setup, and fix some bugs (notably around cookies) en route
 
@@ -403,4 +403,4 @@ The maintainers of `loglevel` and thousands of other packages are working with T
 ## License
 
 Copyright (c) 2013 Tim Perry
-Licensed under the MIT license.
+Licensed under the MIT license. See [`LICENSE-MIT`](./LICENSE-MIT) for full license text.
diff --git a/package.json b/package.json
index 266939d..70d233b 100644
--- a/package.json
+++ b/package.json
@@ -39,13 +39,13 @@
   "devDependencies": {
     "@types/core-js": "2.5.0",
     "@types/node": "^12.0.4",
-    "grunt": "~1.0.4",
-    "grunt-cli": "~1.2.0",
+    "grunt": "~1.5.3",
+    "grunt-cli": "^1.4.3",
     "grunt-contrib-clean": "^1.1.0",
     "grunt-contrib-concat": "~0.5.0",
-    "grunt-contrib-connect": "^1.0.2",
+    "grunt-contrib-connect": "^3.0.0",
     "grunt-contrib-jasmine": "^4.0.0",
-    "grunt-contrib-jshint": "^1.1.0",
+    "grunt-contrib-jshint": "^3.2.0",
     "grunt-contrib-uglify": "^3.4.0",
     "grunt-contrib-watch": "^1.1.0",
     "grunt-open": "~0.2.3",