mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

Fixed typos

Browse source
This commit is contained in:
Pascal Borreli 2014-05-07 07:34:53 +01:00
parent c12ba5d221
commit 831c7f5924
9 changed files with 21 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/api/app.md
View file

@ -23,7 +23,7 @@ Under most cases you should just do everything in `ready` event.
## Event: ready
Emitted when atom-shell has done everything initializaiton.
Emitted when atom-shell has done everything initialization.
## Event: window-all-closed

10
docs/api/browser-window.md
View file

@ -68,12 +68,12 @@ An example of enable node integration in iframe with `node-integration` set to
<iframe src="http://jandan.net"></iframe>
```
And in atom-shell, the security limitaion of iframe is stricter than normal
And in atom-shell, the security limitation of iframe is stricter than normal
browser, by default iframe is sandboxed with all permissions except the
`allow-same-origin`, which means iframe could not access parent's js context.
If you want to enable things like `parent.window.process.exit()` in iframe,
you should explictly set `sandbox` to `none`:
you should explicitly set `sandbox` to `none`:
```html
<iframe sandbox="none" src="https://github.com"></iframe>
@ -118,7 +118,7 @@ remove the reference to the window and avoid using it anymore.
### Event: 'unresponsive'
Emiited when the web page becomes unresponsive.
Emitted when the web page becomes unresponsive.
### Event: 'responsive'
@ -126,7 +126,7 @@ Emitted when the unresponsive web page becomes responsive again.
### Event: 'blur'
Emiited when window loses focus.
Emitted when window loses focus.
### Class Method: BrowserWindow.getAllWindows()
@ -155,7 +155,7 @@ Get the `WebContents` of devtools of this window.
Force closing the window, the `unload` and `beforeunload` event won't be emitted
for the web page, and `close` event would also not be emitted for this window,
but it would gurrantee the `closed` event to be emitted.
but it would guarantee the `closed` event to be emitted.
You should only use this method when the web page has crashed.

2
docs/api/protocol.md
View file

@ -1,7 +1,7 @@
# protocol
The `protocol` module can register a new protocol or intercept an existing
protocol, so you can custom the response to the requests for vairous protocols.
protocol, so you can custom the response to the requests for various protocols.
An example of implementing a protocol that has the same effect with the
`file://` protocol: