docs: fix some typos (yargs#1807)

docs/api.md

@@ -807,7 +807,7 @@ error message when this promise rejects
 <a name="exit"></a>.exit(code, err)
 ---------
 Manually indicate that the program should exit, and provide context about why we
-wanted to exit. Follows the behaviour set by `.exitProcess()`.
+wanted to exit. Follows the behavior set by `.exitProcess()`.
 
 <a name="fail"></a>.fail(fn)
 ---------
@@ -816,7 +816,7 @@ Method to execute when a failure occurs, rather than printing the failure messag
 
 `fn` is called with the failure message that would have been printed, the
 `Error` instance originally thrown and yargs state when the failure
-occured.
+occurred.
 
 ```js
 var argv = require('yargs/yargs')(process.argv.slice(2))
@@ -1308,7 +1308,7 @@ for details of this object
 
 For additional configuration options, see [yargs-parser's configuration](https://github.com/yargs/yargs-parser#configuration).
 
-_Note: configuraton should be top level keys on the `obj` passed to `parserConfiguration`, not populated under the configuration key, as in `yargs-parser`._
+_Note: configuration should be top level keys on the `obj` passed to `parserConfiguration`, not populated under the configuration key, as in `yargs-parser`._
 
 <a name="pkg-conf"></a>
 .pkgConf(key, [cwd])

docs/browser.md

@@ -1,6 +1,6 @@
 # Running yargs in the browser
 
-Newer versions of yargs have a `./browser.mjs` entrypoint, which can be used
+Newer versions of yargs have a `./browser.mjs` entry point, which can be used
 through a CDN like [unpkg.com](https://unpkg.com/) to load yargs directly in
 the browser:
 

docs/bundling.md

@@ -10,7 +10,7 @@ Newer releases of yargs can run directly in modern browsers, take a look at
 
 ## ncc
 
-If you are targetting Node.js with your bundle, we recommend using
+If you are targeting Node.js with your bundle, we recommend using
 [`@vercel/ncc`](https://www.npmjs.com/package/@vercel/ncc).
 
 Given a CommonJS file, **index.js**: