@@ -286,16 +286,16 @@ table(width="100%")
286286 It tests how an app would install and use your library.
287287
288288 The **QuickStart Library seed** includes a directory called `integration` containing a standalone
289- app that consumes your built library in both JIT and AOT modes, with end-to-end tests to verify
289+ app that consumes your built library in both AOT and JIT modes, with end-to-end tests to verify
290290 it works.
291291
292292 To run the integration tests, do `npm run integration` which does the following:
293293 - Build your library.
294294 - Enter the integration app's directory.
295295 - Install dependencies.
296- - Test the app in JIT mode.
297296 - Build the app in AOT mode.
298297 - Test the app in AOT mode.
298+ - Test the app in JIT mode.
299299
300300 Running integration tests gives you greater confidence that your library is properly built.
301301
@@ -416,11 +416,11 @@ table(width="100%")
416416 ## Appendix: Supporting JIT
417417
418418 AOT compiled code is the preferred format for production builds, but due to the long compilation
419- time, it may not be practical to use AOT during development.
419+ time it may not be practical to use AOT during development.
420420
421- To create a more flexible developer experience, a JIT compatible build of the library should be
422- published as well. The format of the JIT bundle is `umd`, which stands for Universal Module
423- Definition.
421+ To create a more flexible developer experience a JIT compatible build of the library should be
422+ published as well.
423+ The format of the JIT bundle is `umd`, which stands for Universal Module Definition.
424424 Shipping the bundle as `umd` ensures compatibility with most common module loading formats.
425425
426426 The `umd` bundle will ship as a single file containing ES5 JavaScript and inlined versions of
0 commit comments