docs: Improved documentation (#13403)

docs/tutorial/application-distribution.md

@@ -141,7 +141,7 @@ we appreciate your help.
 2. Create a new S3 bucket and create the following empty directory structure:
 
     ```sh
-    - atom-shell/
+    - electron/
       - symbols/
       - dist/
     ```
@@ -150,7 +150,7 @@ we appreciate your help.
 
   * `ELECTRON_GITHUB_TOKEN` - a token that can create releases on GitHub
   * `ELECTRON_S3_ACCESS_KEY`, `ELECTRON_S3_BUCKET`, `ELECTRON_S3_SECRET_KEY` -
-    the place where you'll upload node.js headers as well as symbols
+    the place where you'll upload Node.js headers as well as symbols
   * `ELECTRON_RELEASE` - Set to `true` and the upload part will run, leave unset
     and `surf-build` will do CI-type checks, appropriate to run for every
     pull request.

docs/tutorial/electron-versioning.md

@@ -49,7 +49,7 @@ Below is a table explicitly mapping types of changes to their corresponding cate
 | Chromium version updates        |                                    | fix-related chromium patches  |
 
 
-Note that most chromium updates will be considered breaking. Fixes that can be backported will likely be cherry-picked as patches.
+Note that most Chromium updates will be considered breaking. Fixes that can be backported will likely be cherry-picked as patches.
 
 # Stabilization Branches
 

docs/tutorial/using-selenium-and-webdriver.md

@@ -164,7 +164,7 @@ To test your application without rebuilding Electron,
 [place](https://github.com/electron/electron/blob/master/docs/tutorial/application-distribution.md)
 your app source into Electron's resource directory.
 
-Alternatively, pass an argument to run with your electron binary that points to
+Alternatively, pass an argument to run with your Electron binary that points to
 your app's folder. This eliminates the need to copy-paste your app into
 Electron's resource directory.