Propose fix some typos (#11905)

This commit is contained in:
John Eismeier 2018-02-13 00:18:27 -05:00 committed by shelley vohr
parent 546bd6da5e
commit 8d55334016
9 changed files with 11 additions and 11 deletions

View file

@ -194,7 +194,7 @@ Returns:
[`NSUserActivity.activityType`][activity-type]. [`NSUserActivity.activityType`][activity-type].
* `userInfo` Object - Contains app-specific state stored by the activity. * `userInfo` Object - Contains app-specific state stored by the activity.
Emitted when [Handoff][handoff] is about to be resumed on another device. If you need to update the state to be transferred, you should call `event.preventDefault()` immediatelly, construct a new `userInfo` dictionary and call `app.updateCurrentActiviy()` in a timely manner. Otherwise the operation will fail and `continue-activity-error` will be called. Emitted when [Handoff][handoff] is about to be resumed on another device. If you need to update the state to be transferred, you should call `event.preventDefault()` immediately, construct a new `userInfo` dictionary and call `app.updateCurrentActiviy()` in a timely manner. Otherwise the operation will fail and `continue-activity-error` will be called.
### Event: 'new-window-for-tab' _macOS_ ### Event: 'new-window-for-tab' _macOS_

View file

@ -189,7 +189,7 @@ feature. We are still not aware of the security implications of exposing some
electron renderer APIs to the preload script, but here are some things to electron renderer APIs to the preload script, but here are some things to
consider before rendering untrusted content: consider before rendering untrusted content:
- A preload script can accidentaly leak privileged APIs to untrusted code. - A preload script can accidentally leak privileged APIs to untrusted code.
- Some bug in V8 engine may allow malicious code to access the renderer preload - Some bug in V8 engine may allow malicious code to access the renderer preload
APIs, effectively granting full access to the system through the `remote` APIs, effectively granting full access to the system through the `remote`
module. module.

View file

@ -187,7 +187,7 @@ The `proxyBypassRules` is a comma separated list of rules described below:
Examples: Examples:
"127.0.1", "[0:0::1]", "[::1]", "http://[::1]:99" "127.0.1", "[0:0::1]", "[::1]", "http://[::1]:99"
* `IP_LITERAL "/" PREFIX_LENGHT_IN_BITS` * `IP_LITERAL "/" PREFIX_LENGTH_IN_BITS`
Match any URL that is to an IP literal that falls between the Match any URL that is to an IP literal that falls between the
given range. IP range is specified using CIDR notation. given range. IP range is specified using CIDR notation.
@ -319,7 +319,7 @@ Clears the host resolver cache.
#### `ses.allowNTLMCredentialsForDomains(domains)` #### `ses.allowNTLMCredentialsForDomains(domains)`
* `domains` String - A comma-seperated list of servers for which * `domains` String - A comma-separated list of servers for which
integrated authentication is enabled. integrated authentication is enabled.
Dynamically sets whether to always send credentials for HTTP NTLM or Negotiate Dynamically sets whether to always send credentials for HTTP NTLM or Negotiate

View file

@ -1112,7 +1112,7 @@ with native view, which developers have very limited control of. With the
the devtools in it, including `BrowserWindow`, `BrowserView` and `<webview>` the devtools in it, including `BrowserWindow`, `BrowserView` and `<webview>`
tag. tag.
Note that closing the devtools does not destory the `devToolsWebContents`, it Note that closing the devtools does not destroy the `devToolsWebContents`, it
is caller's responsibility to destroy `devToolsWebContents`. is caller's responsibility to destroy `devToolsWebContents`.
An example of showing devtools in a `<webview>` tag: An example of showing devtools in a `<webview>` tag:

View file

@ -225,7 +225,7 @@ and intend to stay there).
* `capacity` Integer * `capacity` Integer
Attemp to set the capacity of resource cache for the renderer process in bytes Attempt to set the capacity of resource cache for the renderer process in bytes
Note if current cached resource size is larger than newly specified capacity, Electron Note if current cached resource size is larger than newly specified capacity, Electron
will schedule to prune cached resources until it reaches below new capacity. will schedule to prune cached resources until it reaches below new capacity.

View file

@ -2,7 +2,7 @@
1. Get the version of crashpad that we're going to use. 1. Get the version of crashpad that we're going to use.
- `libcc/src/third_party/crashpad/README.chromium` will have a line `Revision:` with a checksum - `libcc/src/third_party/crashpad/README.chromium` will have a line `Revision:` with a checksum
- We need to check out the correponding branch. - We need to check out the corresponding branch.
- Clone Google's crashpad (https://chromium.googlesource.com/crashpad/crashpad) - Clone Google's crashpad (https://chromium.googlesource.com/crashpad/crashpad)
- `git clone https://chromium.googlesource.com/crashpad/crashpad` - `git clone https://chromium.googlesource.com/crashpad/crashpad`
- Check out the branch with the revision checksum: - Check out the branch with the revision checksum:

View file

@ -3,7 +3,7 @@
## Discussion ## Discussion
One upgrade issue is building all of Electron with a single copy One upgrade issue is building all of Electron with a single copy
of V8 to ensure compatability. This is important because of V8 to ensure compatibility. This is important because
upstream Node and [libchromiumcontent](upgrading-chromium.md) upstream Node and [libchromiumcontent](upgrading-chromium.md)
both use their own versions of V8. both use their own versions of V8.

View file

@ -130,4 +130,4 @@ npm install --verbose electron
``` ```
If you need to force a re-download of the asset and the SHASUM file set the If you need to force a re-download of the asset and the SHASUM file set the
`force_no_cache` enviroment variable to `true`. `force_no_cache` environment variable to `true`.

View file

@ -89,7 +89,7 @@ improve the security of your application.
Any resources not included with your application should be loaded using a Any resources not included with your application should be loaded using a
secure protocol like `HTTPS`. In other words, do not use insecure protocols secure protocol like `HTTPS`. In other words, do not use insecure protocols
like `HTTP`. Similarly, we recommed the use of `WSS` over `WS`, `FTPS` over like `HTTP`. Similarly, we recommend the use of `WSS` over `WS`, `FTPS` over
`FTP`, and so on. `FTP`, and so on.
### Why? ### Why?
@ -432,7 +432,7 @@ Advanced users of Electron can enable experimental Chromium features using the
### Why? ### Why?
Experimental features are, as the name suggests, experimental and have not been Experimental features are, as the name suggests, experimental and have not been
enabled for all Chromium users. Futhermore, their impact on Electron as a whole enabled for all Chromium users. Furthermore, their impact on Electron as a whole
has likely not been tested. has likely not been tested.
Legitimate use cases exist, but unless you know what you are doing, you should Legitimate use cases exist, but unless you know what you are doing, you should