reflected changes mentioned in review

Author: madewithkode

README.md

@@ -47,30 +47,37 @@ via lektor (see [Deployment](#deployment), below).
 
 ### Pre-Requisites
 
-Make sure you have [pipenv][pipenvdocs], [Node.js][nodejswebsite] and [npm][npmdocs] installed. To install these, execute the following commands:
+Make sure you have:
+
+* [pipenv][pipenvdocs]
+
+* [Node.js][nodejswebsite] **v12+** and [npm][npmdocs] installed. 
+
+To install these, execute the following commands:
 
 > For  macOS:
+
 1. `brew install pipenv`
 2. `brew install node`
 
 > For GNU/Linux:
+
 1. `curl https://raw.githubusercontent.com/kennethreitz/pipenv/master/get-pipenv.py | python`
 2. `sudo apt update`
-3. `sudo apt install nodejs`
-4. `sudo apt install npm `
+3. `curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash -`
+4. `sudo apt-get install -y nodejs`
+5. `sudo apt install npm `
 
 [pipenvdocs]:https://pipenv.readthedocs.io/en/latest/
 [nodejswebsite]:https://nodejs.org/en/
 [npmdocs]:https://docs.npmjs.com/ 
 
-
 ### Installing Project Requirements
 
 1. Clone this repository.
-2. Open your command line interface and `cd` to the repository root directory.
+2. Open your command line interface and `cd` to the repository's root directory.
 3. Run `pipenv install` to create a Python virtual environment and install the requirements for this project.
 
-
 ### pipenv Troubleshooting
 
 `pipenv` doesn't always provide the best error messages ([Provide better error
@@ -81,35 +88,32 @@ else fails, try removing the virtual environment and reinstalling:
 
 [pipenverror]:https://github.com/pypa/pipenv/issues/1918
 
-
 ## Development
 
-- `cd` into `webpack`
-- Run `npm install` to install required node packages
 - Run `pipenv run lektor server -f webpack` to start the Lektor development
   server.
 - You will be able to see the website at [`http://localhost:5000/`][local5000].
   - The Lektor server will rebuild the site every time you change any content.
 
 [local5000]:http://localhost:5000/
 
-
 ### Troubleshooting Possible Errors
 
-Should you get series of type errors that looks something like `npm ERR! typeerror Error: Missing required argument #1`, after running `npm install`, this is most likely due to running an older version of node. 
+Should you get series of type errors that looks something like `npm ERR! typeerror Error: Missing required argument #1`, after running `pipenv run lektor server -f webpack`, this is most likely due to running an older version of node. 
 
-From experience, running Node versions 12+ seems to be okay. Follow [this](https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions) tutorial to upgrade your node version(for unix systems).
-
-Should you get an `OSError: [Errno 28] inotify watch limit reached` after running any command, this means that your system file watcher is running out of alloted handles, usually because the workspace is large and contains many files. 
+As stated earlier in the prerequisites, you should be running Node versions 12+.
 
-The solution is to run `sudo sysctl fs.inotify.max_user_watches=524288`
+* Follow [this](https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions) tutorial to upgrade your node version (for GNU/Unix systems).
 
-This increases your inotify watch limit to 524288, which is the maximum value.
+Should you get an `OSError: [Errno 28] inotify watch limit reached` after running any command, this means that your system file watcher is running out of alloted handles, usually because the workspace is large and contains many files. 
 
-You can learn more about file watchers [here](https://unixia.wordpress.com/2018/04/28/inotify-watch-limit-reached-wait-what/) and [here](https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc).
+The solution is to run:
 
+* `sudo sysctl fs.inotify.max_user_watches=524288`
 
+This increases your inotify watch limit (for the session) to 524288, which is the maximum value and is also enough to allow the  setup go through.
 
+You can learn more about file watchers [here](https://unixia.wordpress.com/2018/04/28/inotify-watch-limit-reached-wait-what/) and [here](https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc).
 
 ## Deployment