docs(plugins): avoid code in heading

Author: snitin315

src/content/plugins/dll-plugin.mdx

@@ -17,7 +17,7 @@ related:
 
 The `DllPlugin` and `DllReferencePlugin` provide means to split bundles in a way that can drastically improve build time performance. The term "DLL" stands for Dynamic-link library which was originally introduced by Microsoft.
 
-## `DllPlugin`
+## DllPlugin
 
 This plugin is used in a separate webpack configuration exclusively to create a dll-only-bundle. It creates a `manifest.json` file, which is used by the [`DllReferencePlugin`](#dllreferenceplugin) to map dependencies.
 
@@ -38,7 +38,7 @@ Creates a `manifest.json` which is written to the given `path`. It contains mapp
 
 Combine this plugin with [`output.library`](/configuration/output/#outputlibrary) option to expose (aka, put into the global scope) the dll function.
 
-## `DllReferencePlugin`
+## DllReferencePlugin
 
 This plugin is used in the primary webpack config, it references the dll-only-bundle(s) to require pre-built dependencies.
 

src/content/plugins/environment-plugin.mdx

@@ -103,7 +103,7 @@ new webpack.EnvironmentPlugin({
 });
 ```
 
-## `DotenvPlugin`
+## DotenvPlugin
 
 The third-party [`DotenvPlugin`](https://github.com/mrsteele/dotenv-webpack) (`dotenv-webpack`) allows you to expose (a subset of) [dotenv variables](https://www.npmjs.com/package/dotenv):
 

src/content/plugins/limit-chunk-count-plugin.mdx

@@ -22,7 +22,7 @@ new webpack.optimize.LimitChunkCountPlugin({
 
 The following options are supported:
 
-### `maxChunks`
+### maxChunks
 
 `number`
 
@@ -42,7 +42,7 @@ module.exports = {
 };
 ```
 
-### `minChunkSize`
+### minChunkSize
 
 Keeping chunk size above the specified limit is no longer a feature of this plugin. Use [MinChunkSizePlugin](/plugins/min-chunk-size-plugin) instead.
 

src/content/plugins/split-chunks-plugin.mdx

@@ -50,7 +50,7 @@ webpack provides a set of options for developers that want more control over thi
 
 W> The default configuration was chosen to fit web performance best practices, but the optimal strategy for your project might differ. If you're changing the configuration, you should measure the effect of your changes to ensure there's a real benefit.
 
-## `optimization.splitChunks`
+## optimization.splitChunks
 
 This configuration object represents the default behavior of the `SplitChunksPlugin`.
 
@@ -89,13 +89,13 @@ W> When files paths are processed by webpack, they always contain `/` on Unix sy
 
 W> Since webpack 5, passing an entry name to `{cacheGroup}.test` and using a name of an existing chunk for `{cacheGroup}.name` is no longer allowed.
 
-### `splitChunks.automaticNameDelimiter`
+### splitChunks.automaticNameDelimiter
 
 `string = '~'`
 
 By default webpack will generate names using origin and name of the chunk (e.g. `vendors~main.js`). This option lets you specify the delimiter to use for the generated names.
 
-### `splitChunks.chunks`
+### splitChunks.chunks
 
 `string = 'async'` `function (chunk)`
 
@@ -133,69 +133,69 @@ module.exports = {
 
 T> You can combine this configuration with the [HtmlWebpackPlugin](/plugins/html-webpack-plugin/). It will inject all the generated vendor chunks for you.
 
-### `splitChunks.maxAsyncRequests`
+### splitChunks.maxAsyncRequests
 
 `number = 30`
 
 Maximum number of parallel requests when on-demand loading.
 
-### `splitChunks.maxInitialRequests`
+### splitChunks.maxInitialRequests
 
 `number = 30`
 
 Maximum number of parallel requests at an entry point.
 
-### `splitChunks.defaultSizeTypes`
+### splitChunks.defaultSizeTypes
 
 `[string] = ['javascript', 'unknown']`
 
 Sets the size types which are used when a number is used for sizes.
 
-### `splitChunks.minChunks`
+### splitChunks.minChunks
 
 `number = 1`
 
 The minimum times must a module be shared among chunks before splitting.
 
-### `splitChunks.hidePathInfo`
+### splitChunks.hidePathInfo
 
 `boolean`
 
 Prevents exposing path info when creating names for parts splitted by maxSize.
 
-### `splitChunks.minSize`
+### splitChunks.minSize
 
 `number = 20000`
 
 Minimum size, in bytes, for a chunk to be generated.
 
-### `splitChunks.enforceSizeThreshold`
+### splitChunks.enforceSizeThreshold
 
-#### `splitChunks.cacheGroups.{cacheGroup}.enforceSizeThreshold`
+#### splitChunks.cacheGroups.{cacheGroup}.enforceSizeThreshold
 
 `number = 50000`
 
 Size threshold at which splitting is enforced and other restrictions (minRemainingSize, maxAsyncRequests, maxInitialRequests) are ignored.
 
-### `splitChunks.minRemainingSize`
+### splitChunks.minRemainingSize
 
-#### `splitChunks.cacheGroups.{cacheGroup}.minRemainingSize`
+#### splitChunks.cacheGroups.{cacheGroup}.minRemainingSize
 
 `number = 0`
 
 `splitChunks.minRemainingSize` option was introduced in webpack 5 to avoid zero sized modules by ensuring that the minimum size of the chunk which remains after splitting is above a limit. Defaults to `0` in ['development' mode](/configuration/mode/#mode-development). For other cases `splitChunks.minRemainingSize` defaults to the value of `splitChunks.minSize` so it doesn't need to be specified manually except for the rare cases where deep control is required.
 
 W> `splitChunks.minRemainingSize` only takes effect when a single chunk is remaining.
 
-### `splitChunks.layer`
+### splitChunks.layer
 
-#### `splitChunks.cacheGroups.{cacheGroup}.layer`
+#### splitChunks.cacheGroups.{cacheGroup}.layer
 
 `RegExp` `string` `function`
 
 Assign modules to a cache group by module layer.
 
-### `splitChunks.maxSize`
+### splitChunks.maxSize
 
 `number = 0`
 
@@ -210,23 +210,23 @@ T> `maxSize` takes higher priority than `maxInitialRequest/maxAsyncRequests`. Ac
 
 T> Setting the value for `maxSize` sets the value for both `maxAsyncSize` and `maxInitialSize`.
 
-### `splitChunks.maxAsyncSize`
+### splitChunks.maxAsyncSize
 
 `number`
 
 Like `maxSize`, `maxAsyncSize` can be applied globally (`splitChunks.maxAsyncSize`), to cacheGroups (`splitChunks.cacheGroups.{cacheGroup}.maxAsyncSize`), or to the fallback cache group (`splitChunks.fallbackCacheGroup.maxAsyncSize`).
 
 The difference between `maxAsyncSize` and `maxSize` is that `maxAsyncSize` will only affect on-demand loading chunks.
 
-### `splitChunks.maxInitialSize`
+### splitChunks.maxInitialSize
 
 `number`
 
 Like `maxSize`, `maxInitialSize` can be applied globally (`splitChunks.maxInitialSize`), to cacheGroups (`splitChunks.cacheGroups.{cacheGroup}.maxInitialSize`), or to the fallback cache group (`splitChunks.fallbackCacheGroup.maxInitialSize`).
 
 The difference between `maxInitialSize` and `maxSize` is that `maxInitialSize` will only affect initial load chunks.
 
-### `splitChunks.name`
+### splitChunks.name
 
 `boolean = false` `function (module, chunks, cacheGroupKey) => string` `string`
 
@@ -279,16 +279,16 @@ Running webpack with following `splitChunks` configuration would also output a c
 
 W> When assigning equal names to different split chunks, all vendor modules are placed into a single shared chunk, though it's not recommend since it can result in more code downloaded.
 
-### `splitChunks.usedExports`
+### splitChunks.usedExports
 
-#### `splitChunks.cacheGroups{cacheGroup}.usedExports`
+#### splitChunks.cacheGroups{cacheGroup}.usedExports
 
 `boolean = true`
 
 Figure out which exports are used by modules to mangle export names, omit unused exports and generate more efficient code.
 When it is `true`: analyse used exports for each runtime, when it is `"global"`: analyse exports globally for all runtimes combined).
 
-### `splitChunks.cacheGroups`
+### splitChunks.cacheGroups
 
 Cache groups can inherit and/or override any options from `splitChunks.*`; but `test`, `priority` and `reuseExistingChunk` can only be configured on cache group level. To disable any of the default cache groups, set them to `false`.
 
@@ -307,13 +307,13 @@ module.exports = {
 };
 ```
 
-#### `splitChunks.cacheGroups.{cacheGroup}.priority`
+#### splitChunks.cacheGroups.{cacheGroup}.priority
 
 `number = -20`
 
 A module can belong to multiple cache groups. The optimization will prefer the cache group with a higher `priority`. The default groups have a negative priority to allow custom groups to take higher priority (default value is `0` for custom groups).
 
-#### `splitChunks.cacheGroups.{cacheGroup}.reuseExistingChunk`
+#### splitChunks.cacheGroups.{cacheGroup}.reuseExistingChunk
 
 `boolean = true`
 
@@ -336,7 +336,7 @@ module.exports = {
 };
 ```
 
-#### `splitChunks.cacheGroups.{cacheGroup}.type`
+#### splitChunks.cacheGroups.{cacheGroup}.type
 
 `function` `RegExp` `string`
 
@@ -359,9 +359,9 @@ module.exports = {
 };
 ```
 
-#### `splitChunks.cacheGroups.test`
+#### splitChunks.cacheGroups.test
 
-#### `splitChunks.cacheGroups.{cacheGroup}.test`
+#### splitChunks.cacheGroups.{cacheGroup}.test
 
 `function (module, { chunkGraph, moduleGraph }) => boolean` `RegExp` `string`
 
@@ -422,7 +422,7 @@ module.exports = {
 };
 ```
 
-#### `splitChunks.cacheGroups.{cacheGroup}.filename`
+#### splitChunks.cacheGroups.{cacheGroup}.filename
 
 `string` `function (pathData, assetInfo) => string`
 
@@ -489,7 +489,7 @@ module.exports = {
 };
 ```
 
-#### `splitChunks.cacheGroups.{cacheGroup}.enforce`
+#### splitChunks.cacheGroups.{cacheGroup}.enforce
 
 `boolean = false`
 
@@ -512,7 +512,7 @@ module.exports = {
 };
 ```
 
-#### `splitChunks.cacheGroups.{cacheGroup}.idHint`
+#### splitChunks.cacheGroups.{cacheGroup}.idHint
 
 `string`