From 5c7b19ce69323f9e992156189b9c6da8d8df86a6 Mon Sep 17 00:00:00 2001 From: "Beegen, James C (CGI Federal)" Date: Thu, 22 Feb 2024 15:13:38 -0500 Subject: [PATCH] Fixed a typo in the word 'simplicity' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2af68241..d19f4776 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ If you attempt to configure the `NVM_SYMLINK` to use an existing directory (like _PATH Conflicts_ If you do not uninstall the original version, running `nvm use` may appear to do nothing at all. Running `node -v` will always show the original installation version. This is due to a [`PATH` conflict](https://github.com/coreybutler/nvm-windows/wiki/Common-Issues#why-do-i-need-to-uninstall-nodejs-before-installing-nvm-for-windows) that presents when the same application is installed multiple times. In NVM4W 1.1.11+, run `nvm debug` to determine if you have a `PATH` conflict. -For simpliciy, we recommend uninstalling any existing versions of Node.js before using NVM for Windows. Delete any existing Node.js installation directories (e.g., `%ProgramFiles%\nodejs`) that might remain. NVM's generated symlink will not overwrite an existing (even empty) installation directory. +For simplicity, we recommend uninstalling any existing versions of Node.js before using NVM for Windows. Delete any existing Node.js installation directories (e.g., `%ProgramFiles%\nodejs`) that might remain. NVM's generated symlink will not overwrite an existing (even empty) installation directory. :eyes: **Backup any global `npmrc` config** :eyes: (e.g. `%AppData%\npm\etc\npmrc`)