From 1770f0c47683a2efb874d5ff348e0715106a9afd Mon Sep 17 00:00:00 2001
From: Teos <47872542+teofanis@users.noreply.github.com>
Date: Sat, 22 Oct 2022 14:09:51 +0100
Subject: [PATCH] Update adding-dependencies.md

---
 docs/adding-dependencies.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/adding-dependencies.md b/docs/adding-dependencies.md
index 321a51b7..bbbc01bb 100644
--- a/docs/adding-dependencies.md
+++ b/docs/adding-dependencies.md
@@ -25,7 +25,7 @@ This boilerplate uses a [two package.json structure](https://www.electron.build/
 **Rule of thumb** is: all modules go into `./package.json` except for native modules, or modules with native dependencies or peer dependencies. Native modules, or packages with native dependencies should go into `./release/app/package.json`.
 
 1. If the module is native to a platform (like node-postgres), it should be listed under `dependencies` in `./release/app/package.json`
-2. If a module is `import`ed by another module, include it in `dependencies` in `./package.json`. See [this ESLint rule](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-extraneous-dependencies.md). Examples of such modules are `material-ui`, `redux-form`, and `moment`.
+2. If a module is `imported` by another module, include it in `dependencies` in `./package.json`. See [this ESLint rule](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-extraneous-dependencies.md). Examples of such modules are `material-ui`, `redux-form`, and `moment`.
 3. Otherwise, modules used for building, testing, and debugging should be included in `devDependencies` in `./package.json`.
 
 ### Further Readings