eslint
diff --git a/‎docs/src/use/getting-started.md
Lines changed: 23 additions & 22 deletions b/‎docs/src/use/getting-started.md
Lines changed: 23 additions & 22 deletions
@@ -51,36 +51,31 @@ After that, you can run ESLint on any file or directory like this:
 
 **Note:** If you are coming from a version before 9.0.0 please see the [migration guide](configure/migration-guide).
 
-After running `npm init @eslint/config`, you'll have an `eslint.config.js` (or `eslint.config.mjs`) file in your directory. In it, you'll see some rules configured like this:
+When you run `npm init @eslint/config`, you'll be asked a series of questions to determine how you're using ESLint and what options should be included. After answering these questions, you'll have an `eslint.config.js` (or `eslint.config.mjs`) file created in your directory.
+
+For example, one of the questions is "Where does your code run?" If you select "Browser" then your configuration file will contain the definitions for global variables found in web browsers. Here's an example:
 
 ```js
-// eslint.config.js
+import globals from "globals";
+import pluginJs from "@eslint/js";
+
+
+/** @type {import('eslint').Linter.Config[]} */
 export default [
-    {
-        rules: {
-            "no-unused-vars": "error",
-            "no-undef": "error"
-        }
-    }
+  {languageOptions: { globals: globals.browser }},
+  pluginJs.configs.recommended,
 ];
 ```
 
-The names `"no-unused-vars"` and `"no-undef"` are the names of [rules](../rules) in ESLint. The first value is the error level of the rule and can be one of these values:
-
-* `"off"` or `0` - turn the rule off
-* `"warn"` or `1` - turn the rule on as a warning (doesn't affect exit code)
-* `"error"` or `2` - turn the rule on as an error (exit code will be 1)
-
-The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the [configuration docs](configure/)).
+The `pluginJs.configs.recommended` object contains configuration to ensure that all of the rules marked as recommended on the [rules page](../rules) will be turned on.  Alternatively, you can use configurations that others have created by searching for "eslint-config" on [npmjs.com](https://www.npmjs.com/search?q=eslint-config).  ESLint will not lint your code unless you extend from a shared configuration or explicitly turn rules on in your configuration.
 
-Your `eslint.config.js` configuration file will also include a recommended configuration, like this:
+You can configure rules individually by defining a new object with a `rules` key, as in this example:
 
 ```js
-// eslint.config.js
-import js from "@eslint/js";
+import pluginJs from "@eslint/js";
 
 export default [
-    js.configs.recommended,
+    pluginJs.configs.recommended,
 
     {
         rules: {
@@ -91,7 +86,13 @@ export default [
 ];
 ```
 
-The `js.configs.recommended` object contains configuration to ensure that all of the rules marked as recommended on the [rules page](../rules) will be turned on.  Alternatively, you can use configurations that others have created by searching for "eslint-config" on [npmjs.com](https://www.npmjs.com/search?q=eslint-config).  ESLint will not lint your code unless you extend from a shared configuration or explicitly turn rules on in your configuration.
+The names `"no-unused-vars"` and `"no-undef"` are the names of [rules](../rules) in ESLint. The first value is the error level of the rule and can be one of these values:
+
+* "off" or 0 - turn the rule off
+* "warn" or 1 - turn the rule on as a warning (doesn’t affect exit code)
+* "error" or 2 - turn the rule on as an error (exit code will be 1)
+
+The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).
 
 ## Global Install
 
@@ -121,10 +122,10 @@ Before you begin, you must already have a `package.json` file. If you don't, mak
 1. Add configuration to the `eslint.config.js` file. Refer to the [Configure ESLint document
736A
ation](configure/) to learn how to add rules, custom configurations, plugins, and more.
 
    ```js
-   import js from "@eslint/js";
+   import pluginJs from "@eslint/js";
 
    export default [
-       js.configs.recommended,
+       pluginJs.configs.recommended,
 
       {
           rules: {