Reworked explanation for package aliases. Also removed note about spl…

…itting into its own repo as this problem will not be solved as long as the package used is local

webpack/webpack.config.base.ts

@@ -139,11 +139,12 @@ const configBase: webpack.Configuration = {
       // use tsconfig.json paths https://www.npmjs.com/package/tsconfig-paths-webpack-plugin
       new TsconfigPathsPlugin(),
     ],
-    // Load `papi-components`' `dependencies` from `paranext-core` so the extension will share these
-    // dependencies with the bundled copy of `papi-components` and avoid duplicate packages.
-    // These paths are broken up like this so multi-extension folder can format the path properly
+    // Load `platform-bible-react`' `dependencies` from `paranext-core` so the extension will share
+    // these dependencies with the bundled copy of `platform-bible-react` and avoid duplicate
+    // packages. These paths are broken up like this so multi-extension folder can format the path
+    // properly
     // https://webpack.js.org/configuration/resolve/#resolvealias
-    // TODO: Remove this when `papi-components` is split into its own repo or is published to npm
+    // TODO: Remove this when `platform-bible-react` is published to npm
     alias: {
       '@emotion/react': path.resolve(
         __dirname,