More minor build tweaks and docs updates.

1 files changed, 2 insertions, 2 deletions

diff --git a/js/tests/README.md b/js/tests/README.md
index b2d505723..72ece2d36 100644
--- a/js/tests/README.md
+++ b/js/tests/README.md
@@ -6,7 +6,7 @@ Bootstrap uses [QUnit](https://qunitjs.com/), a powerful, easy-to-use JavaScript
 * `vendor/` contains third-party testing-related code (QUnit and jQuery).
 * `visual/` contains "visual" tests which are run interactively in real browsers and require manual verification by humans.
 
-To run the unit test suite via [PhantomJS](http://phantomjs.org/), run `grunt test-js`.
+To run the unit test suite via [PhantomJS](http://phantomjs.org/), run `npm run js-test`.
 
 To run the unit test suite via a real web browser, open `index.html` in the browser.
 
@@ -16,7 +16,7 @@ To run the unit test suite via a real web browser, open `index.html` in the brow
 1. Locate and open the file dedicated to the plugin which you need to add tests to (`unit/<plugin-name>.js`).
 2. Review the [QUnit API Documentation](https://api.qunitjs.com/) and use the existing tests as references for how to structure your new tests.
 3. Write the necessary unit test(s) for the new or revised functionality.
-4. Run `grunt test-js` to see the results of your newly-added test(s).
+4. Run `npm run js-test` to see the results of your newly-added test(s).
 
 **Note:** Your new unit tests should fail before your changes are applied to the plugin, and should pass after your changes are applied to the plugin.