docs: correct lodash dependency usage in authoring libraries guide

Author: prince-up

src/content/guides/author-libraries.mdx

@@ -33,14 +33,15 @@ The basic project structure would look like this:
 +     └── ref.json
 ```
 
-Initialize the project with npm, then install `webpack`, `webpack-cli` and `lodash`:
+Initialize the project with npm, then install `webpack` and `webpack-cli` as development dependencies, and `lodash` as a runtime dependency:
 
 ```bash
 npm init -y
-npm install --save-dev webpack webpack-cli lodash
+npm install --save-dev webpack webpack-cli
+npm install lodash
 ```
 
-We install `lodash` as `devDependencies` instead of `dependencies` because we don't want to bundle it into our library, or our library could be easily bloated.
+We install `lodash` as a `dependency` because it is required at runtime by our library. However, to prevent our library from becoming bloated, we will configure webpack to treat it as an external module rather than bundling it.
 
 **src/ref.json**
 
@@ -252,7 +253,7 @@ T> Note that the `library` setup is tied to the `entry` configuration. For most
 
 ## Externalize Lodash
 
-Now, if you run `npx webpack`, you will find that a largish bundle is created. If you inspect the file, you'll see that lodash has been bundled along with your code. In this case, we'd prefer to treat `lodash` as a _peer dependency_. Meaning that the consumer should already have `lodash` installed. Hence you would want to give up control of this external library to the consumer of your library.
+Now, if you run `npx webpack`, you will find that a largish bundle is created. If you inspect the file, you'll see that lodash has been bundled along with your code. Since `lodash` is listed as a `dependency` in your `package.json`, package managers will install it automatically for consumers of your library. This means you can rely on the consumer's environment to provide it, rather than bundling it directly.
 
 This can be done using the [`externals`](/configuration/externals/) configuration: