[Docs] Fix URLs and Paths (#11584)

* Fix URLs and Paths in docs/

* Avoiding link break to /docs/development/updgrading-chrome.md

* Fix URLs and Paths in docs/ #2

* Removed double spaces in docs

docs/development/build-instructions-linux.md

@@ -8,7 +8,7 @@ Follow the guidelines below for building Electron on Linux.
 * Python 2.7.x. Some distributions like CentOS 6.x still use Python 2.6.x
   so you may need to check your Python version with `python -V`.
 * Node.js. There are various ways to install Node. You can download
-  source code from [nodejs.org](http://nodejs.org) and compile it.
+  source code from [nodejs.org](https://nodejs.org) and compile it.
   Doing so permits installing Node on your own home directory as a standard user.
   Or try repositories such as [NodeSource](https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories).
 * [clang](https://clang.llvm.org/get_started.html) 3.4 or later.
@@ -155,12 +155,12 @@ information may help you.
 
 ### Building `libchromiumcontent` locally
 
-To avoid using the prebuilt binaries of `libchromiumcontent`, you can build `libchromiumcontent` locally.  To do so, follow these steps:
+To avoid using the prebuilt binaries of `libchromiumcontent`, you can build `libchromiumcontent` locally. To do so, follow these steps:
 
 1. Install [depot_tools](https://chromium.googlesource.com/chromium/src/+/master/docs/linux_build_instructions.md#Install)
 2. Install [additional build dependencies](https://chromium.googlesource.com/chromium/src/+/master/docs/linux_build_instructions.md#Install-additional-build-dependencies)
 3. Fetch the git submodules:
-  
+
 ```sh
 $ git submodule update --init --recursive
 ```
@@ -179,11 +179,11 @@ $ ./script/build.py -c R
 
 ### Using system `clang` instead of downloaded `clang` binaries
 
-By default Electron is built with prebuilt 
+By default Electron is built with prebuilt
 [`clang`](https://clang.llvm.org/get_started.html) binaries provided by the
-Chromium project. If for some reason you want to build with the `clang` 
-installed in your system, you can call `bootstrap.py` with `--clang_dir=<path>` 
-switch. By passing it the build script will assume the `clang` binaries reside 
+Chromium project. If for some reason you want to build with the `clang`
+installed in your system, you can call `bootstrap.py` with `--clang_dir=<path>`
+switch. By passing it the build script will assume the `clang` binaries reside
 in `<path>/bin/`.
 
 For example if you installed `clang` under `/user/local/bin/clang`:

docs/development/build-instructions-osx.md

@@ -6,7 +6,7 @@ Follow the guidelines below for building Electron on macOS.
 
 * macOS >= 10.11.6
 * [Xcode](https://developer.apple.com/technologies/tools/) >= 8.2.1
-* [node.js](http://nodejs.org) (external)
+* [node.js](https://nodejs.org) (external)
 
 If you are using the Python downloaded by Homebrew, you also need to install
 the following Python modules:

docs/development/build-instructions-windows.md

@@ -8,7 +8,7 @@ Follow the guidelines below for building Electron on Windows.
 * Visual Studio 2015 Update 3 - [download VS 2015 Community Edition for
   free](https://www.visualstudio.com/vs/older-downloads/)
 * [Python 2.7](http://www.python.org/download/releases/2.7/)
-* [Node.js](http://nodejs.org/download/)
+* [Node.js](https://nodejs.org/download/)
 * [Git](http://git-scm.com)
 * [Debugging Tools for Windows](https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063.aspx)
   if you plan on creating a full distribution since `symstore.exe` is used for
@@ -143,7 +143,7 @@ Try reinstalling 32bit Node.js.
 
 ### Error: ENOENT, stat 'C:\Users\USERNAME\AppData\Roaming\npm'
 
-Simply making that directory [should fix the problem](http://stackoverflow.com/a/25095327/102704):
+Simply making that directory [should fix the problem](https://stackoverflow.com/a/25095327/102704):
 
 ```powershell
 $ mkdir ~\AppData\Roaming\npm

docs/development/coding-style.md

@@ -8,7 +8,7 @@ You can run `npm run lint` to show any style issues detected by `cpplint` and
 ## C++ and Python
 
 For C++ and Python, we follow Chromium's [Coding
-Style](http://www.chromium.org/developers/coding-style). You can use
+Style](https://www.chromium.org/developers/coding-style). You can use
 [clang-format](clang-format.md) to format the C++ code automatically. There is
 also a script `script/cpplint.py` to check whether all files conform.
 
@@ -23,7 +23,7 @@ etc.
 
 ## JavaScript
 
-* Write [standard](http://npm.im/standard) JavaScript style.
+* Write [standard](https://npm.im/standard) JavaScript style.
 * File names should be concatenated with `-` instead of `_`, e.g.
   `file-name.js` rather than `file_name.js`, because in
   [github/atom](https://github.com/github/atom) module names are usually in

docs/development/releasing.md

@@ -10,7 +10,7 @@ This document describes the process for releasing a new version of Electron.
 
 ## Find out what version change is needed
 Run `npm run prepare-release -- --notesOnly` to view auto generated release
-notes.  The notes generated should help you determine if this is a major, minor,
+notes. The notes generated should help you determine if this is a major, minor,
 patch, or beta version change. Read the
 [Version Change Rules](../tutorial/electron-versioning.md#semver) for more information.
 
@@ -18,7 +18,7 @@ patch, or beta version change. Read the
 The prepare release script will do the following:
 1. Check if a release is already in process and if so it will halt.
 2. Create a release branch.
-3. Bump the version number in several files.  See [this bump commit] for an example.
+3. Bump the version number in several files. See [this bump commit] for an example.
 4. Create a draft release on GitHub with auto-generated release notes.
 5. Push the release branch.
 6. Call the APIs to run the release builds.
@@ -57,7 +57,7 @@ To monitor the build progress, see the following pages:
 
 - [mac-ci.electronjs.org/blue/organizations/jenkins/electron-mas-x64-release/activity](https://mac-ci.electronjs.org/blue/organizations/jenkins/electron-mas-x64-release/activity) for Mac App Store
 - [mac-ci.electronjs.org/blue/organizations/jenkins/electron-osx-x64-release/activity](https://mac-ci.electronjs.org/blue/organizations/jenkins/electron-osx-x64-release/activity) for OS X
-- [circleci.com/gh/electron](https://circleci.com/gh/electron) for Linux
+- [circleci.com/gh/electron/electron](https://circleci.com/gh/electron) for Linux
 - [windows-ci.electronjs.org/project/AppVeyor/electron](https://windows-ci.electronjs.org/project/AppVeyor/electron) for Windows
 
 ## Compile release notes
@@ -188,7 +188,7 @@ npm run merge-release -- 1-7-x
 ## Publish the release
 
 Once the merge has finished successfully, run the `release` script
-via `npm run release` to finish the release process.  This script will do the
+via `npm run release` to finish the release process. This script will do the
 following:
 1. Build the project to validate that the correct version number is being released.
 2. Download the binaries and generate the node headers and the .lib linker used

docs/development/setting-up-symbol-server.md

@@ -5,7 +5,7 @@ about the functions contained in executables and dynamic libraries and provide
 you with information to get clean call stacks. A Symbol Server allows the
 debugger to load the correct symbols, binaries and sources automatically without
 forcing users to download large debugging files. The server functions like
-[Microsoft's symbol server](http://support.microsoft.com/kb/311503) so the
+[Microsoft's symbol server](https://support.microsoft.com/kb/311503) so the
 documentation there can be useful.
 
 Note that because released Electron builds are heavily optimized, debugging is
@@ -38,7 +38,7 @@ or by typing the `.sympath` command. If you would like to get symbols from
 Microsoft's symbol server as well, you should list that first:
 
 ```powershell
-SRV*c:\code\symbols\*http://msdl.microsoft.com/download/symbols;SRV*c:\code\symbols\*https://electron-symbols.githubapp.com
+SRV*c:\code\symbols\*https://msdl.microsoft.com/download/symbols;SRV*c:\code\symbols\*https://electron-symbols.githubapp.com
 ```
 
 ## Using the symbol server in Visual Studio

docs/development/source-code-directory-structure.md

@@ -4,7 +4,7 @@ The source code of Electron is separated into a few parts, mostly
 following Chromium on the separation conventions.
 
 You may need to become familiar with [Chromium's multi-process
-architecture](http://dev.chromium.org/developers/design-documents/multi-process-architecture)
+architecture](https://dev.chromium.org/developers/design-documents/multi-process-architecture)
 to understand the source code better.
 
 ## Structure of Source Code

docs/development/updgrading-chrome.md

@@ -0,0 +1 @@
+Moved to [upgrading-chromium.md](upgrading-chromium.md)

docs/development/upgrading-chromium.md

@@ -37,7 +37,7 @@ This is an overview of the steps needed to upgrade Chromium in Electron.
   - If some patches are no longer compatible with the Chromium code,
     fix compilation errors.
 6. When the build succeeds, create a `dist` for Electron
-  - `$ ./script/create-dist  --no_zip`
+  - `$ ./script/create-dist --no_zip`
     - It will create a `dist/main` folder in the libcc repo's root.
       You will need this to build Electron.
 7. (Optional) Update script contents if there are errors resulting from files
@@ -107,7 +107,7 @@ Follow all the steps above to fix Electron code on all supported platforms.
 
 If there are any compilation errors related to the Crashpad, it probably means
 you need to update the fork to a newer revision. See
-[Upgrading Crashpad](https://github.com/electron/electron/tree/master/docs/development/upgrading-crashpad.md)
+[Upgrading Crashpad](upgrading-crashpad.md)
 for instructions on how to do that.
 
 
@@ -116,7 +116,7 @@ for instructions on how to do that.
 Upgrade `vendor/node` to the Node release that corresponds to the v8 version
 used in the new Chromium release. See the v8 versions in Node on
 
-See [Upgrading Node](https://github.com/electron/electron/tree/master/docs/development/upgrading-node.md)
+See [Upgrading Node](upgrading-node.md)
 for instructions on this.
 
 ## Verify ffmpeg support

docs/development/upgrading-crashpad.md

@@ -16,10 +16,10 @@
 
 2. Make a checklist of the Electron patches that need to be applied
   with `git log --oneline`
-    - Or view http://github.com/electron/crashpad/commits/previous-branch-name
+    - Or view https://github.com/electron/crashpad/commits/previous-branch-name
 
 3. For each patch:
-  - In `electron-crashpad-vA.B.C.D`, cherry-pick the patch's checksum    
+  - In `electron-crashpad-vA.B.C.D`, cherry-pick the patch's checksum
     - `git cherry-pick <checksum>`
   - Resolve any conflicts
   - Make sure it builds then add, commit, and push work to electron's crashpad fork
@@ -37,6 +37,3 @@
 6. Push changes to submodule reference
   - (From electron root) `git add vendor/crashpad`
   - `git push origin upgrade-to-chromium-62`
-
-
-

docs/development/upgrading-node.md

@@ -4,7 +4,7 @@
 
 One upgrade issue is building all of Electron with a single copy
 of V8 to ensure compatability. This is important because
-upstream Node and [libchromiumcontent](upgrading-chrome.md)
+upstream Node and [libchromiumcontent](upgrading-chromium.md)
 both use their own versions of V8.
 
 Upgrading Node is much easier than upgrading libchromiumcontent,
@@ -97,7 +97,7 @@ We need to generate a patch file from each patch applied to V8.
      - `mv test.patch patches/v8/xxx-patch_name.patch`
   - Add the patched code to the index _without_ committing:
      - `cd src/v8 && git add . && cd ../..`
-     -  We don't want to commit the changes (they're kept in the patchfiles)
+     - We don't want to commit the changes (they're kept in the patchfiles)
         but need them locally so that they don't show up in subsequent diffs
         while we iterate through more patches
   - Add the patch file to the index: