docs: e. g. -> e.g. (#4157)

* e. g. -> e.g.

* ignore

* del.vs

* revert .gitignore

Co-authored-by: Sam Chen <[email protected]>

Author: xp44mm

src/content/api/loaders.md

@@ -390,7 +390,7 @@ loadModule(request: string, callback: function(err, source, sourceMap, module))
 
 Resolves the given request to a module, applies all configured loaders and calls back with the generated source, the sourceMap and the module instance (usually an instance of [`NormalModule`](https://github.com/webpack/webpack/blob/master/lib/NormalModule.js)). Use this function if you need to know the source code of another module to generate the result.
 
-`this.loadModule` in a loader context uses CommonJS resolve rules by default. Use `this.getResolve` with an appropriate `dependencyType`, e. g. `'esm'`, `'commonjs'` or a custom one before using a different semantic.
+`this.loadModule` in a loader context uses CommonJS resolve rules by default. Use `this.getResolve` with an appropriate `dependencyType`, e.g. `'esm'`, `'commonjs'` or a custom one before using a different semantic.
 
 
 ### `this.resolve`

src/content/blog/2020-10-10-webpack-5-release.md

@@ -168,7 +168,7 @@ __MIGRATION__: Use the default export.
 
 Even when using the default export, unused properties are dropped by the `optimization.usedExports` optimization and properties are mangled by the `optimization.mangleExports` optimization.
 
-It's possible to specify a custom JSON parser in `Rule.parser.parse` to import JSON-like files (e. g. for toml, yaml, json5, etc.).
+It's possible to specify a custom JSON parser in `Rule.parser.parse` to import JSON-like files (e.g. for toml, yaml, json5, etc.).
 
 ### import.meta
 
@@ -475,7 +475,7 @@ The `target` option now influences more things about the generated code than bef
 - Some loaders might change behavior based on that
 
 For some of these things the choice between `"web"` and `"node"` is too rough and we need more information.
-Therefore we allow to specify the minimum version e. g. like `"node10.13"` and infer more properties about the target environment.
+Therefore we allow to specify the minimum version e.g. like `"node10.13"` and infer more properties about the target environment.
 
 It's now also allowed to combined multiple targets with an array and webpack will determine the minimum properties of all targets. Using an array is also useful when using targets that doesn't give full information like `"web"` or `"node"` (without version number). E. g. `["web", "es2020"]` combines these two partial targets.
 
@@ -735,7 +735,7 @@ __MIGRATION__: Upgrade to the latest Node.js version available.
 - `stats.chunkRelations` added: Show parent/children/sibling chunks
 - `stats.errorStack` added: Show webpack-internal stack trace of errors
 - `stats.preset` added: select a preset
-- `stats.relatedAssets` added: show assets that are related to other assets (e. g. SourceMaps)
+- `stats.relatedAssets` added: show assets that are related to other assets (e.g. SourceMaps)
 - `stats.warningsFilter` deprecated in favor of `ignoreWarnings`
 - `BannerPlugin.banner` signature changed
     - `data.basename` removed
@@ -803,7 +803,7 @@ __MIGRATION__: This can be implemented in the loader itself
 
 `getResolve(options)` in the loader API will merge options in a different way, see `module.rules` `resolve`.
 
-As webpack 5 differs between different issuing dependencies so it might make sense to pass a `dependencyType` as option (e. g. `"esm"`, `"commonjs"`, or others).
+As webpack 5 differs between different issuing dependencies so it might make sense to pass a `dependencyType` as option (e.g. `"esm"`, `"commonjs"`, or others).
 
 ## Major Internal Changes
 

src/content/configuration/stats.md

@@ -957,7 +957,7 @@ module.exports = {
 
 `boolean = true`
 
-Display children of the chunk groups (e. g. prefetched, preloaded chunks and assets).
+Display children of the chunk groups (e.g. prefetched, preloaded chunks and assets).
 
 ```javascript
 module.exports = {

src/content/guides/code-splitting.md

@@ -147,7 +147,7 @@ The [`dependOn` option](/configuration/entry-context/#dependencies) allows to sh
 
 Using multiple entry points per page should be avoided when possible in favor of an entry point with multiple imports: `entry: { page: ['./analytics', './app'] }`. This results in a better optimization and consistent execution order when using `async` script tags.
 
-T> Multiple entry points per page could be used in scenarios where HTML is generated in a dynamic matter, e. g. when components on page are unknown at compile-time and HTML page is composed dynamically depending on the data.
+T> Multiple entry points per page could be used in scenarios where HTML is generated in a dynamic matter, e.g. when components on page are unknown at compile-time and HTML page is composed dynamically depending on the data.
 
 ### `SplitChunksPlugin`
 

src/content/guides/ecma-script-modules.md

@@ -81,7 +81,7 @@ In addition to the module format, flagging modules as ESM also affect the resolv
 
 Imports in ESM are resolved more stictly. Relative requests must include a filename and file extension.
 
-T> Requests to packages e. g. `import "lodash"` are still supported.
+T> Requests to packages e.g. `import "lodash"` are still supported.
 
 Only the "default" export can be imported from non-ESM. Named exports are not available.
 

src/content/migrate/5.md

@@ -129,7 +129,7 @@ Need to support an older browser?
 
 - By default, webpack will use your browserslist config to decide which code style to emit.
 - Without a browserslist it would emit ES6 style. You can use `target: ["web", "es5"]` to change it to ES5.
-- For Node.js, builds include the supported Node.js version in the `target` option and webpack will automatically figure out which syntax is supported, e. g. `target: 'node8.6'`.
+- For Node.js, builds include the supported Node.js version in the `target` option and webpack will automatically figure out which syntax is supported, e.g. `target: 'node8.6'`.
 
 #### Cleanup the code