Docs

README.md

@@ -9,8 +9,8 @@ This could be developed into a webpack plugin at some point, but as an example i
 The key features of the approach are:
 * Rather than call `boot()` at runtime, we perform a `loopback-boot` *compile* at build time and store the resulting *boot instructions* as a bundled JSON resource.
 * At runtime, we just call the `loopback-boot` executor to perform the boot. This avoids many problems trying to bundle the compiler and also provides much faster boot times for complex applications.
-* All of the boot-time resources are specified in a [ContextReplacementPlugin](https://webpack.github.io/docs/list-of-plugins.html#contextreplacementplugin) by providing a single *dependency map* that resolves all of the resources specified in the boot instructions. This feature of ContextReplacementPlugin is currently undocumented.
-* No browserify!
+* All of the boot-time resources are specified in a `ContextReplacementPlugin` by providing a single *dependency map* that resolves all of the resources specified in the boot instructions. This feature of `ContextReplacementPlugin` is [currently undocumented](https://webpack.github.io/docs/list-of-plugins.html#contextreplacementplugin).
+* No need for browserify!
 * We specify which `node_modules` dependencies will be bundled (internalized) and which will not. `loopback-boot/lib/executor` must be bundled so webpack can handle resolution of models, boot scripts, etc.
 * Dynamic configuration files (such as `config.json` and `datasources.json`) are excluded from the bundle (externalized) so that they can be modified without re-building.
 * [gulp](http://gulpjs.com) is used trivially to perform the build.