diff --git a/docs/api/environment-variables.md b/docs/api/environment-variables.md
index 3bd2326810f9..a840eec1d175 100644
--- a/docs/api/environment-variables.md
+++ b/docs/api/environment-variables.md
@@ -36,12 +36,10 @@ file, before opening any browser windows that will make geocoding requests:
 process.env.GOOGLE_API_KEY = 'YOUR_KEY_HERE'
 ```
 
-For instructions on how to acquire a Google API key, see
-https://www.chromium.org/developers/how-tos/api-keys
+For instructions on how to acquire a Google API key, visit [this page](https://www.chromium.org/developers/how-tos/api-keys).
 
 By default, a newly generated Google API key may not be allowed to make
-geocoding requests. To enable geocoding requests, visit this page:
-https://console.developers.google.com/apis/api/geolocation/overview
+geocoding requests. To enable geocoding requests, visit [this page](https://console.developers.google.com/apis/api/geolocation/overview).
 
 ### `ELECTRON_NO_ASAR`
 
diff --git a/docs/api/ipc-main.md b/docs/api/ipc-main.md
index 6ba9c2656403..9e39d789a9c9 100644
--- a/docs/api/ipc-main.md
+++ b/docs/api/ipc-main.md
@@ -3,7 +3,7 @@
 > Communicate asynchronously from the main process to renderer processes.
 
 The `ipcMain` module is an instance of the
-[EventEmitter](https://nodejs.org/api/events.html) class. When used in the main
+[EventEmitter](https://nodejs.org/api/events.html#events_class_eventemitter) class. When used in the main
 process, it handles asynchronous and synchronous messages sent from a renderer
 process (web page). Messages sent from a renderer will be emitted to this
 module.
diff --git a/docs/api/ipc-renderer.md b/docs/api/ipc-renderer.md
index 9835e42b4679..cf4c75133b7d 100644
--- a/docs/api/ipc-renderer.md
+++ b/docs/api/ipc-renderer.md
@@ -3,7 +3,7 @@
 > Communicate asynchronously from a renderer process to the main process.
 
 The `ipcRenderer` module is an instance of the
-[EventEmitter](https://nodejs.org/api/events.html) class. It provides a few
+[EventEmitter](https://nodejs.org/api/events.html#events_class_eventemitter) class. It provides a few
 methods so you can send synchronous and asynchronous messages from the render
 process (web page) to the main process.  You can also receive replies from the
 main process.
diff --git a/docs/api/remote.md b/docs/api/remote.md
index 420c0fdd2120..08e86bc1926f 100644
--- a/docs/api/remote.md
+++ b/docs/api/remote.md
@@ -20,7 +20,7 @@ win.loadURL('https://github.com')
 ```
 
 **Note:** For the reverse (access the renderer process from the main process),
-you can use [webContents.executeJavascript](web-contents.md#webcontentsexecutejavascriptcode-usergesture-callback).
+you can use [webContents.executeJavascript](web-contents.md#contentsexecutejavascriptcode-usergesture-callback).
 
 ## Remote Objects
 
diff --git a/docs/api/screen.md b/docs/api/screen.md
index ebc2be45ab7d..2467b646db72 100644
--- a/docs/api/screen.md
+++ b/docs/api/screen.md
@@ -5,7 +5,7 @@
 You cannot require or use this module until the `ready` event of the `app`
 module is emitted.
 
-`screen` is an [EventEmitter](http://nodejs.org/api/events.html#events_class_events_eventemitter).
+`screen` is an [EventEmitter](https://nodejs.org/api/events.html#events_class_eventemitter).
 
 **Note:** In the renderer / DevTools, `window.screen` is a reserved DOM
 property, so writing `let {screen} = require('electron')` will not work.
diff --git a/docs/api/synopsis.md b/docs/api/synopsis.md
index 8a7fca71b77d..71ca497cc264 100644
--- a/docs/api/synopsis.md
+++ b/docs/api/synopsis.md
@@ -2,7 +2,7 @@
 
 > How to use Node.js and Electron APIs.
 
-All of [Node.js's built-in modules](http://nodejs.org/api/) are available in
+All of [Node.js's built-in modules](https://nodejs.org/api/) are available in
 Electron and third-party node modules also fully supported as well (including
 the [native modules](../tutorial/using-native-node-modules.md)).
 
@@ -13,7 +13,7 @@ both processes.
 
 The basic rule is: if a module is [GUI][gui] or low-level system related, then
 it should be only available in the main process. You need to be familiar with
-the concept of [main process vs. renderer process](../tutorial/quick-start.md#the-main-process)
+the concept of [main process vs. renderer process](../tutorial/quick-start.md#main-process)
 scripts to be able to use those modules.
 
 The main process script is just like a normal Node.js script:
diff --git a/docs/api/tray.md b/docs/api/tray.md
index ed9747ec3545..3ac2d54038f4 100644
--- a/docs/api/tray.md
+++ b/docs/api/tray.md
@@ -239,4 +239,4 @@ The `bounds` of this tray icon as `Object`.
 
 Returns `Boolean` - Whether the tray icon is destroyed.
 
-[event-emitter]: http://nodejs.org/api/events.html#events_class_events_eventemitter
+[event-emitter]: https://nodejs.org/api/events.html#events_class_eventemitter
diff --git a/docs/api/web-contents.md b/docs/api/web-contents.md
index 28051df461d3..2ae7532dc430 100644
--- a/docs/api/web-contents.md
+++ b/docs/api/web-contents.md
@@ -3,7 +3,7 @@
 > Render and control web pages.
 
 `webContents` is an
-[EventEmitter](http://nodejs.org/api/events.html#events_class_events_eventemitter).
+[EventEmitter](https://nodejs.org/api/events.html#events_class_eventemitter).
 It is responsible for rendering and controlling a web page and is a property of
 the [`BrowserWindow`](browser-window.md) object. An example of accessing the
 `webContents` object: