docs(configuration): update stats.mdx (#7157)

Author: snitin315

src/content/configuration/stats.mdx

@@ -23,7 +23,7 @@ contributors:
 
 The `stats` option lets you precisely control what bundle information gets displayed. This can be a nice middle ground if you don't want to use `quiet` or `noInfo` because you want some bundle information, but not all of it.
 
-W> This option does not have any effect when using the Node.js API. You need to pass the stats options to the `stats.toString()` resp. `stats.toJson()` calls instead.
+W> This option does not have any effect when using the [Node.js API](/api/node). You need to pass the stats options to the `stats.toString()` resp. `stats.toJson()` calls instead.
 
 ```js
 module.exports = {
@@ -1232,31 +1232,31 @@ Tells `stats` to display chunk parents, children and siblings.
 
 ### Sorting fields
 
-For `assetsSort`, `chunksSort` and `modulesSort` there are several possible fields that you can sort items by:
-
-- `'id'` is the item's id;
-- `'name'` - a item's name that was assigned to it upon importing;
-- `'size'` - a size of item in bytes;
-- `'chunks'` - what chunks the item originates from (for example, if there are multiple subchunks for one chunk - the subchunks will be grouped together according to their main chunk);
-- `'errors'` - amount of errors in items;
-- `'warnings'` - amount of warnings in items;
-- `'failed'` - whether the item has failed compilation;
-- `'cacheable'` - whether the item is cacheable;
-- `'built'` - whether the asset has been built;
-- `'prefetched'` - whether the asset will be prefetched;
-- `'optional'` - whether the asset is optional;
-- `'identifier'` - identifier of the item;
-- `'index'` - item's processing index;
+For `assetsSort`, `chunksSort`, and `modulesSort` there are several possible fields that you can sort items by:
+
+- `'id'` - the item's id,
+- `'name'` - the item's name that was assigned to it upon importing,
+- `'size'` - the size of item in bytes,
+- `'chunks'` - what chunks the item originates from (for example, if there are multiple subchunks for one chunk: the subchunks will be grouped according to their main chunk),
+- `'errors'` - number of errors in items,
+- `'warnings'` - number of warnings in items,
+- `'failed'` - whether the item has failed compilation,
+- `'cacheable'` - whether the item is cacheable,
+- `'built'` - whether the asset has been built,
+- `'prefetched'` - whether the asset will be prefetched,
+- `'optional'` - whether the asset is optional.
+- `'identifier'` - identifier of the item.
+- `'index'` - item's processing index.
 - `'index2'`
 - `'profile'`
-- `'issuer'` - an identifier of the issuer;
-- `'issuerId'` - an id of the issuer;
-- `'issuerName'` - a name of the issuer;
-- `'issuerPath'` - a full issuer object. There's no real need to sort by this field;
+- `'issuer'` - an identifier of the issuer.
+- `'issuerId'` - an id of the issuer.
+- `'issuerName'` - a name of the issuer.
+- `'issuerPath'` - a full issuer object. There's no real need to sort by this field.
 
 ### Extending stats behaviours
 
-If you want to use one of the pre-defined behaviours e.g. `'minimal'` but still override one or more of the rules: specify the desired `stats.preset` and add the customized or additional rules afterwards.
+If you want to use one of the presets e.g. `'minimal'` but still override some of the rules: specify the desired `stats.preset` and add the customized or additional rules afterwards.
 
 **webpack.config.js**