docs(readme): update naming again

Author: jrolfs

README.md

@@ -1,5 +1,5 @@
 <div align="center">
-<h1>hvr-scripts 🛠📦</h1>
+<h1>@hover/javascript 🛠📦</h1>
 
 <p>CLI toolbox for common scripts for <del>my</del> <strong>our</strong> projects</p>
 </div>
@@ -39,25 +39,25 @@ This module is distributed via [npm][npm] which is bundled with [node][node] and
 should be installed as one of your project's `devDependencies`:
 
 ```
-yarn add -D hvr-scripts
+yarn add -D @hover/javascript
 ```
 
 ## Usage
 
-This is a CLI and exposes a bin called `hvr-scripts`. You'll find all available scripts in `src/scripts`.
+This is a CLI and exposes a bin called `hover-scripts`. You'll find all available scripts in `src/scripts`.
 
 This project actually dogfoods itself. If you look in the `package.json`, you'll
 find scripts with `node src {scriptName}`. This serves as an example of some
-of the things you can do with `hvr-scripts`.
+of the things you can do with `hover-scripts`.
 
 ### Overriding Config
 
-Unlike `react-scripts`, `hvr-scripts` allows you to specify your own
+Unlike `react-scripts`, `hover-scripts` allows you to specify your own
 configuration for things and have that plug directly into the way things work
-with `hvr-scripts`. There are various ways that it works, but basically if you
+with `hover-scripts`. There are various ways that it works, but basically if you
 want to have your own config for something, just add the configuration and
-`hvr-scripts` will use that instead of it's own internal config. In addition,
-`hvr-scripts` exposes its configuration so you can use it and override only
+`hover-scripts` will use that instead of it's own internal config. In addition,
+`hover-scripts` exposes its configuration so you can use it and override only
 the parts of the config you need to.
 
 This can be a very helpful way to make editor integration work for tools like
@@ -67,19 +67,19 @@ So, if we were to do this for ESLint, you could create an `.eslintrc` with the
 contents of:
 
 ```
-{"extends": "./node_modules/hvr-scripts/eslint.js"}
+{"extends": "./node_modules/@hover/javascript/eslint.js"}
 ```
 
 Or, for `babel`, a `.babelrc` with:
 
 ```
-{"presets": ["hvr-scripts/babel"]}
+{"presets": ["@hover/javascript/babel"]}
 ```
 
 Or, for `jest`:
 
 ```javascript
-const {jest: jestConfig} = require('hvr-scripts/config')
+const {jest: jestConfig} = require('@hover/javascript/config')
 module.exports = Object.assign(jestConfig, {
   // your overrides here
 
@@ -90,7 +90,7 @@ module.exports = Object.assign(jestConfig, {
 })
 ```
 
-> Note: `hvr-scripts` intentionally does not merge things for you when you start
+> Note: `hover-scripts` intentionally does not merge things for you when you start
 > configuring things to make it less magical and more straightforward. Extending
 > can take place on your terms. ~~I~~ _Kent_ thinks this is actually a great way to do this.