docs(devServer): Clarify devServer "open" option description (#1890)

* docs(devServer): clarify devServer "open" option description

Added information that you can also use browser name in the config file.

* docs(devServer): add missing type to 'open' option

* docs(devServer): fix Travis CI

* docs(guides): fix sentence (#1887)

This removes a word that made a sentence not grammatically correct.

* docs (guides): Missing line in diff and missing semicolons (#1907)

* Update dev-server.md

Author: Simek

src/content/configuration/dev-server.md

@@ -638,13 +638,24 @@ module.exports = {
 };
 ```
 
+If no browser is provided (as shown above), your default browser will be used. To specify a different browser, just pass its name instead of boolean:
+
+```javascript
+module.exports = {
+  //...
+  devServer: {
+    open: 'Google Chrome'
+  }
+};
+```
+
 Usage via the CLI
 
 ```bash
 webpack-dev-server --open
 ```
 
-If no browser is provided (as shown above), your default browser will be used. To specify a different browser, just pass its name:
+Or with specified browser:
 
 __webpack.config.js__
 

src/content/guides/production.md

@@ -147,7 +147,6 @@ __package.json__
 
 Feel free to run those scripts and see how the output changes as we continue adding to our _production_ configuration.
 
-
 ## Specify the Mode
 
 Many libraries will key off the `process.env.NODE_ENV` variable to determine what should be included in the library. For example, when not in _production_ some libraries may add additional logging and testing to make debugging easier. However, with `process.env.NODE_ENV === 'production'` they might drop or add significant portions of code to optimize how things run for your actual users. Since webpack v4, specifying [`mode`](/concepts/mode/) automatically configures [`DefinePlugin`](/plugins/define-plugin) for you: