docs: improve readability of optimization.chunkIds documentation (#8068)

Author: Raginipatel17

src/content/configuration/optimization.mdx

@@ -41,9 +41,17 @@ export default {
 
 ## optimization.chunkIds
 
-`boolean = false` `string: 'natural' | 'named' | 'size' | 'total-size' | 'deterministic'`
+`boolean` | `natural` | `named` | `size` | `total-size` | `deterministic`
 
-Tells webpack which algorithm to use when choosing chunk ids. Setting `optimization.chunkIds` to `false` tells webpack that none of built-in algorithms should be used, as custom one can be provided via plugin. There are a couple of defaults for `optimization.chunkIds`:
+- `false`: disable webpack's built-in chunk id algorithm
+- one of the following values:
+  - `'natural'`
+  - `'named'`
+  - `'size'`
+  - `'total-size'`
+  - `'deterministic'`
+
+Tells Webpack which algorithm to use for chunk IDs. Setting `optimization.chunkIds` to `false` tells webpack that none of built-in algorithms should be used, as custom one can be provided via plugin. There are a couple of defaults for `optimization.chunkIds`:
 
 The default value of `optimization.chunkIds` depends on the [`mode`](/configuration/mode/):
 
@@ -135,6 +143,8 @@ W> If you are using webpack [CLI](/api/cli/), the webpack process will not exit
 
 <Badge text="5.95.0+" />
 
+T> IIFE (Immediately Invoked Function Expression) is a function that runs immediately after it is created. Webpack uses it to wrap code and avoid variable conflicts.
+
 Use `optimization.avoidEntryIife` to avoid wrapping the entry module in an IIFE when it is required (search for `"This entry needs to be wrapped in an IIFE because"` in [JavascriptModulesPlugin](https://github.com/webpack/webpack/blob/main/lib/javascript/JavascriptModulesPlugin.js)). This approach helps optimize performance for JavaScript engines and enables tree shaking when building ESM libraries.
 
 Currently, `optimization.avoidEntryIife` can only optimize a single entry module along with other modules.