NWJS to NW.js

TheJaredWilcurt · rogerwang · commit b6af5d838fd4 · 2017-10-18T10:18:26.000+08:00
diff --git a/docs/For Users/Advanced/Autoupdates.md b/docs/For Users/Advanced/Autoupdates.md
@@ -3,7 +3,7 @@
 
 [TOC]
 
-NWJS tend to support the update solution made by community, not a built-in one. Below is the list of existing soutions, which worth checking.
+NW.js tend to support the update solution made by community, not a built-in one. Below is the list of existing soutions, which worth checking.
 - [node-webkit-updater](https://github.com/edjafarov/node-webkit-updater) (by [@edjafarov](https://github.com/edjafarov))
 - [nwjs-autoupdater](https://github.com/oaleynik/nwjs-autoupdater) (by [@oaleynik](https://github.com/oaleynik))
 - [nw-autoupdater](https://github.com/dsheiko/nw-autoupdater) (by [@dsheiko](https://github.com/dsheiko))
@@ -23,16 +23,16 @@ You should build this logic by yourself though ([basic example](https://github.c
 
 ## nwjs-autoupdater
 
-The tiny golang application (when built it is just ~2MB), which can be bundled with NWJS application and then used to unpack updates.
+The tiny golang application (when built it is just ~2MB), which can be bundled with NW.js application and then used to unpack updates.
 To update target application updater needs to know two things - where zip archive with the new version is located and where is the app's executable to restart application after update. These can be passed to updater via command line arguments `--bundle` and `--inst-dir`, where `--bundle` is the path to the zip archive with the new app version and `--inst-dir` is the path to app's executable.
 
 There are multiple advantages over `node-webkit-updater`:
 
 - It can update the updater itself.
 - Doesn't require elevated privilegies (unless application itself has been installed in the folder which require elevated privilegies).
-- Updater's executalbe has way smaller size as it doesn't require bundling the whole new NWJS application with the main application.
+- Updater's executalbe has way smaller size as it doesn't require bundling the whole new NW.js application with the main application.
 
-The logic to check for updates needs to be built on your own too. The [example](https://github.com/oaleynik/nwjs-autoupdater/blob/master/examples/index.js) shows the way how to use javascript module as an entry point for NWJS application and check for updates in background.
+The logic to check for updates needs to be built on your own too. The [example](https://github.com/oaleynik/nwjs-autoupdater/blob/master/examples/index.js) shows the way how to use javascript module as an entry point for NW.js application and check for updates in background.
 
 ## nw-autoupdater
 
@@ -47,4 +47,4 @@ The NPM module provides API similar to one of `node-webkit-updater`, but extende
 - Backup actual version and replace it with the new one
 - Restart the updated app from its original location
 
-The package includes examples of release server and client.
+The package includes examples of release server and client.
