docs: explicitly state why globals is necessary

docs/src/use/configure/configuration-files-new.md

@@ -328,9 +328,9 @@ export default [
 
 For historical reasons, the boolean value `false` and the string value `"readable"` are equivalent to `"readonly"`. Similarly, the boolean value `true` and the string value `"writeable"` are equivalent to `"writable"`. However, the use of older values is deprecated.
 
-#### Using native globals variables
+##### Predefined global variables
 
-To enable native variables, like `console` (browser) or `$` (jQuery), you must use the `globals` package directly. For example, here is how you can add `console`, amongst other browser globals, into your configuration.
+Apart from the ECMAScript standard built-in globals, which are automatically enabled based on the configured `languageOptions.ecmaVersion`, ESLint doesn't provide predefined sets of global variables. You can use the `globals` package to additionally enable all globals for a specific environment. For example, here is how you can add `console`, amongst other browser globals, into your configuration.
 
 ```js
 import globals from "globals";
@@ -339,7 +339,7 @@ export default [
     {
         languageOptions: {
             globals: {
-                ...globals.browser,
+                ...globals.browser
             }
         }
     }