docs: improve contribution documentation (#1865) [skip ci]

Co-authored-by: Vijay Raghavan Aravamudhan <vraravam@users.noreply.github.com>

1 files changed, 22 insertions, 2 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index cc3f9e73c..6a7091624 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -65,6 +65,8 @@ npm -v
 6.14.13
 ```
 
+_Note:_ You can choose any package manager to manage multiple versions of `node` and `npm`. For eg, [nvm](https://github.com/nvm-sh/nvm) or [asdf](https://github.com/asdf-vm/asdf).
+
 #### Git
 
 The version [2.23.0](https://github.com/git-for-windows/git/releases/tag/v2.23.0.windows.1) for Git is working fine for development. You can then use the console from Git to do the development procedure.
@@ -132,12 +134,12 @@ Run the following command to install all dependencies, and link sibling modules
 npx lerna bootstrap
 ```
 
-If you previously ran `npm install`, it sometimes is necessary to delete your `node_modules` folder before running `npx lerna bootstrap`. If you encounter the `gyp: No Xcode or CLT version` error on macOS at this step, please have a look [here](https://medium.com/flawless-app-stories/gyp-no-xcode-or-clt-version-detected-macos-catalina-anansewaa-38b536389e8d).
+If you previously ran `npm install`, it is sometimes necessary to delete your `node_modules` folder before running `npx lerna bootstrap`. If you encounter the `gyp: No Xcode or CLT version` error on macOS at this step, please have a look [here](https://medium.com/flawless-app-stories/gyp-no-xcode-or-clt-version-detected-macos-catalina-anansewaa-38b536389e8d).
 
 ### Fix native modules to match current electron node version
 
 ```bash
-npm run rebuild
+npm run build
 ```
 
 ### Package recipe repository
@@ -235,3 +237,21 @@ git push
 ```
 
 This will automatically trigger the build, as part of which, a new, draft release will be created [here](https://github.com/getferdi/ferdi/releases/). Once all the assets are uploaded (19 assets in total), publish the release (you will need elevated permissions in GitHub for doing this). The last commit of the `release` branch will be tagged.
+
+## Update
+
+### Update the code
+
+```bash
+git pull
+```
+
+### Update Node.js and npm
+
+If node.js and/or npm version have changed, don't forget to update them by running the appropriate command of your chosen package manager.
+
+### Update dependences
+
+```bash
+npx lerna bootstrap
+```