docs: use cheap-module-eval-source-map consistently

Resolves #1577

Author: skipjack

src/content/api/cli.md

@@ -290,10 +290,10 @@ These options allow webpack to display various [stats](/configuration/stats/) an
 
 ### Shortcuts
 
-| Shortcut | Replaces                                                         |
-|----------|------------------------------------------------------------------|
-| -d       | --debug --devtool eval-cheap-module-source-map --output-pathinfo |
-| -p       | --optimize-minimize --define process.env.NODE_ENV="production", see [building for production](/guides/production) |
+Shortcut | Replaces
+---------|----------------------------
+-d       | `--debug --devtool cheap-module-source-map --output-pathinfo`
+-p       | `--optimize-minimize --define process.env.NODE_ENV="production"`, see [building for production](/guides/production)
 
 
 ### Profiling

src/content/guides/build-performance.md

@@ -123,7 +123,7 @@ Be aware of the performance differences of the different `devtool` settings.
 - The `cheap-source-map` variants are more performant, if you can live with the slightly worse mapping quality.
 - Use a `eval-source-map` variant for incremental builds.
 
-=> In most cases `eval-cheap-module-source-map` is the best option.
+=> In most cases `cheap-module-eval-source-map` is the best option.
 
 
 ### Avoid Production Specific Tooling