update build-targets

Author: mansona

.local.dic

@@ -22,7 +22,7 @@ BelongsTo
 blockquote
 blogPost
 bookmarklet
-Browserlist
+Browserslist
 callouts
 camelize
 centric
@@ -179,6 +179,7 @@ rerender
 rerendering
 rerenders
 RequestManager
+Rollup
 routable
 RunDOC
 runnable
@@ -218,6 +219,7 @@ templating
 TextMate
 todo
 todos
+toolchain
 tooltip
 tooltips
 trackable

guides/release/configuring-ember/build-targets.md

@@ -1,10 +1,10 @@
-By default, Ember apps are built with Vite. The toolchain uses Babel (alongside modern compilers like esbuild/Rollup) so you can write current-generation JavaScript and TypeScript with confidence.
+By default, Ember apps are built with Vite. The toolchain uses Babel, esbuild, and Rollup so you can write current-generation JavaScript and TypeScript while still allowing your application to work with older browsers.
 
 Rather than always compiling everything down to legacy syntax, Ember determines what—if anything—needs to be transformed based on the browsers you target. With today’s defaults aimed at evergreen browsers, many features (ES modules, classes, arrow functions, async/await, etc.) ship largely as-is.
 
-Why does this matter? Over-transpiling to very old JavaScript increases bundle size and slows parsing. As the web platform has advanced and legacy browsers have faded, Ember’s defaults avoid unnecessary transforms to keep apps smaller and faster.
+Why does this matter? Over-transpiling to very old JavaScript increases bundle size, slows parsing, and in some cases can slow down the execution of your JavaScript code. As the Web platform has advanced and percentage of users on legacy browsers have decreased, Ember’s default targets avoid unnecessary transforms to keep apps smaller and faster.
 
-That’s why the build respects your browser targets: set the targets for your app and the compiler applies only the minimal transforms and polyfills required for those browsers.
+If you need to update the defaults for any reason (i.e. need to target a very legacy browser), you can set the targets for your app and the compiler applies only the minimal transforms and polyfills required for those browsers.
 
 If you open `config/targets.js`, you will find the following code:
 
@@ -22,7 +22,7 @@ module.exports = {
 };
 ```
 
-If you inspect the compiled code, you’ll see many modern features (like arrow functions and async/await) preserved when your targets support them.
+If you inspect your compiled code after running a build with `npm run build`, you'll see that many modern features (like arrow functions and async/await) preserved when your targets support them.
 
 This feature is backed by [Browserslist](https://github.com/ai/browserslist) and [Can I Use](https://caniuse.com/).
 These websites track usage stats of browsers, so you can use complex queries based on the user base of every browser.
@@ -37,9 +37,3 @@ module.exports = {
 ```
 
 It is very important that you properly configure the targets of your app so you get the smallest and fastest code possible.
-
-Build targets can also be leveraged in other ways.
-
-Some addons might conditionally include polyfills only if needed.
-Some linters may emit warnings when using features not yet fully supported in your targets.
-Some addons may even automatically prefix unsupported CSS properties.