Tidy up module-federation.md, prepare for final review and merge

Author: stevepiercy

docs/classic-ui/module-federation.md

@@ -3,18 +3,18 @@ html_meta:
   "description": "How to use Module Federation in Mockup and add-on bundles."
   "property=og:description": "How to use Module Federation in Mockup and add-on bundles."
   "property=og:title": "Module Federation in Mockup"
-  "keywords": "Plone, Classic UI, classic-ui, Mockup, mockup, Module Federation, Webpack, JavaScript"
+  "keywords": "Plone, Classic UI, classic-ui, Mockup, mockup, module federation, webpack, JavaScript"
 ---
 
 (classic-ui-module-federation-in-mockup-label)=
 
-# Module Federation in Mockup
+# Module federation in Mockup
 
 Module Federation allows sharing of dependencies between bundles.
 Each bundle includes the whole set of dependencies.
-However, if multiple bundles have the same dependencies they are loaded only once.
+However, if multiple bundles have the same dependencies, then they are loaded only once.
 
-For example, if bundle A and B both depend on jQuery and bundle A has already loaded it, bundle B can just reuse the already loaded jQuery file.
+For example, if bundle A and B both depend on jQuery and bundle A has already loaded it, then bundle B can just reuse the already loaded jQuery file.
 But if only bundle B is loaded, it uses its own bundled version of the jQuery library.
 
 There is a host bundle, as in the fictional example above, our bundle A.
@@ -26,42 +26,43 @@ Webpack's documentation on [Module Federation](https://webpack.js.org/concepts/m
 ```
 
 
-## Using module federation
+## Use module federation
 
-The following instructions are for you if you created an add-on with a Mockup pattern and you want to include the respective JavaScript code in your theme code.
-Starting with the webpack configuration that you get when creating a Barceloneta theme package via [plonecli][1], add the following:
+If you created an add-on with a Mockup pattern, and you want to include the respective JavaScript code in your theme code, then the following instructions are for you.
 
-Create a new entry point `index.js` which only imports the normal entry point.
+Starting with the webpack configuration that you get when creating a Barceloneta theme package via [`plonecli`](https://pypi.org/project/plonecli/), add the following.
+
+Create a new entry point {file}`index.js` which only imports the normal entry point.
 
 ```js
 import("./patterns");
 ```
 
-Next add the module federation plugin in `webpack.config.js`.
+Next add the module federation plugin in {file}`webpack.config.js`.
 There is a configuration factory `mf_config` which you can use for that.
-Add the following line near the top of the file:
+Add the following line near the top of the file.
 
 ```js
 const mf_config = require("@patternslib/dev/webpack/webpack.mf");
 ```
 
 Import all the dependencies you want to share.
-Potentially these are the ones from Patternslib, Mockup and your own dependencies.
-You can just add the Patternslib and Mockup dependencies, even if you are not using them.
+Potentially these are the ones from Patternslib, Mockup, and your own dependencies.
+You can add the Patternslib and Mockup dependencies, even if you are not using them.
 
 ```js
 const package_json = require("./package.json");
 const package_json_mockup = require("@plone/mockup/package.json");
 const package_json_patternslib = require("@patternslib/patternslib/package.json");
 ```
 
-Then find the following line:
+Then find the following line.
 
 ```js
     config = patternslib_config(env, argv, config, ["@plone/mockup"]);
 ```
 
-Below this line add the following:
+Below this line add the following.
 
 ```js
     config.plugins.push(
@@ -79,26 +80,20 @@ Below this line add the following:
 ```
 
 Replace the name `myaddon` with your add-on bundle's unique name.
-Replace the filename `myaddon-remote.min.js` with the file name you want to use for your remote bundle.
-Finally replace `myaddon.min` with the corresponding key in `config.entry` that points to your `index.js`.
+Replace the file name {file}`myaddon-remote.min.js` with the file name you want to use for your remote bundle.
+Finally replace `myaddon.min` with the corresponding key in `config.entry` that points to your {file}`index.js`.
 
-For a full but simple example, see the Patterns generator [pat-PATTERN-TEMPLATE][2] or any other Pattern add-on in the [patternslib GitHub organization](https://github.com/patternslib/).
-For a complex example with Mockup integration see [plone.app.mosaic][3] and [Mockup][4] itself.
+For a full and basic example, see the Patterns generator [pat-PATTERN-TEMPLATE](https://github.com/Patternslib/pat-PATTERN_TEMPLATE/blob/master/webpack.config.js) or any other Pattern add-on in the [patternslib GitHub organization](https://github.com/patternslib/).
+For a complex example with Mockup integration see [`plone.app.mosaic`](https://github.com/plone/plone.app.mosaic/blob/master/webpack.config.js) and [Mockup](https://github.com/plone/mockup/blob/master/webpack.config.js) itself.
 
-[1]: https://pypi.org/project/plonecli/
-[2]: https://github.com/Patternslib/pat-PATTERN_TEMPLATE/blob/master/webpack.config.js
-[3]: https://github.com/plone/plone.app.mosaic/blob/master/webpack.config.js
-[4]: https://github.com/plone/mockup/blob/master/webpack.config.js
 
 ## Special case: global modules `jQuery` and `Bootstrap`
 
-In order to preserve compatibility with older add-ons and JavaScript implementations,
-the modules `jQuery` and `Bootstrap` are stored in the  global `window` namespace.
-So constructs like the following are still working:
+To preserve compatibility with older add-ons and JavaScript implementations, the modules `jQuery` and `Bootstrap` are stored in the  global `window` namespace.
+Constructs like the following still work:
 
 ```js
     (function($) {
         // JS code which uses $
     })(jQuery);
 ```
-