Remove more words (#12852)

* remove 'basically' from docs

* remove 'simply' from docs

* remove most uses of 'just' from docs

docs/api/browser-window.md

@@ -435,7 +435,7 @@ window.onbeforeunload = (e) => {
   e.returnValue = false // equivalent to `return false` but not recommended
 }
 ```
-_**Note**: There is a subtle difference between the behaviors of `window.onbeforeunload = handler` and `window.addEventListener('beforeunload', handler)`. It is recommended to always set the `event.returnValue` explicitly, instead of just returning a value, as the former works more consistently within Electron._
+_**Note**: There is a subtle difference between the behaviors of `window.onbeforeunload = handler` and `window.addEventListener('beforeunload', handler)`. It is recommended to always set the `event.returnValue` explicitly, instead of only returning a value, as the former works more consistently within Electron._
 
 #### Event: 'closed'
 

docs/api/chrome-command-line-switches.md

@@ -175,7 +175,7 @@ Gives the per-module maximal V-logging levels to override the value given by
 source files `my_module.*` and `foo*.*`.
 
 Any pattern containing a forward or backward slash will be tested against the
-whole pathname and not just the module. E.g. `*/foo/bar/*=2` would change the
+whole pathname and not only the module. E.g. `*/foo/bar/*=2` would change the
 logging level for all code in the source files under a `foo/bar` directory.
 
 This switch only works when `--enable-logging` is also passed.

docs/api/menu.md

@@ -37,7 +37,7 @@ be dynamically modified.
 * `action` String
 
 Sends the `action` to the first responder of application. This is used for
-emulating default macOS menu behaviors. Usually you would just use the
+emulating default macOS menu behaviors. Usually you would use the
 [`role`](menu-item.md#roles) property of a [`MenuItem`](menu-item.md).
 
 See the [macOS Cocoa Event Handling Guide](https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/EventOverview/EventArchitecture/EventArchitecture.html#//apple_ref/doc/uid/10000060i-CH3-SW7)

docs/api/notification.md

@@ -100,7 +100,7 @@ Objects created with `new Notification` have the following instance methods:
 #### `notification.show()`
 
 Immediately shows the notification to the user, please note this means unlike the
-HTML5 Notification implementation, simply instantiating a `new Notification` does
+HTML5 Notification implementation, instantiating a `new Notification` does
 not immediately show it to the user, you need to call this method before the OS
 will display it.
 

docs/api/sandbox-option.md

@@ -37,7 +37,7 @@ do in chromium (i.e. they do not return a [`BrowserWindowProxy`](browser-window-
 
 ## Example
 
-To create a sandboxed window, simply pass `sandbox: true` to `webPreferences`:
+To create a sandboxed window, pass `sandbox: true` to `webPreferences`:
 
 ```js
 let win
@@ -86,7 +86,7 @@ It is not possible to have the OS sandbox active only for some renderers, if
 `--enable-sandbox` is enabled, normal electron windows cannot be created.
 
 If you need to mix sandboxed and non-sandboxed renderers in one application,
-simply omit the `--enable-sandbox` argument. Without this argument, windows
+omit the `--enable-sandbox` argument. Without this argument, windows
 created with `sandbox: true` will still have node.js disabled and communicate
 only via IPC, which by itself is already a gain from security POV.
 

docs/api/structures/notification-action.md

@@ -17,4 +17,4 @@ following criteria.
 * App is signed
 * App has it's `NSUserNotificationAlertStyle` set to `alert` in the `Info.plist`.
 
-If either of these requirements are not met the button simply won't appear.
+If either of these requirements are not met the button won't appear.

docs/api/synopsis.md

@@ -16,7 +16,7 @@ it should be only available in the main process. You need to be familiar with
 the concept of [main process vs. renderer process](../tutorial/application-architecture.md#main-and-renderer-processes)
 scripts to be able to use those modules.
 
-The main process script is just like a normal Node.js script:
+The main process script is like a normal Node.js script:
 
 ```javascript
 const {app, BrowserWindow} = require('electron')