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

docs: fix spelling and grammar errors (#18910)

Browse source
This commit is contained in:
Charles Kerr 2019-06-21 16:19:21 -05:00 • committed by GitHub
parent bef9610f6a
commit 792f6b246c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
18 changed files with 40 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/api/structures/cpu-usage.md
View file

@ -2,6 +2,6 @@
* `percentCPUUsage` Number - Percentage of CPU used since the last call to getCPUUsage.
First call returns 0.
* `idleWakeupsPerSecond` Number - The number of average idle cpu wakeups per second
* `idleWakeupsPerSecond` Number - The number of average idle CPU wakeups per second
since the last call to getCPUUsage. First call returns 0. Will always return 0 on
Windows.

4
docs/api/structures/ipc-main-event.md
View file

@ -1,7 +1,7 @@
# IpcMainEvent Object extends `Event`
* `frameId` Integer - The ID of the renderer frame that sent this message
* `returnValue` any - Set this to the value to be returned in a syncronous message
* `returnValue` any - Set this to the value to be returned in a synchronous message
* `sender` WebContents - Returns the `webContents` that sent the message
* `reply` Function - A function that will send an IPC message to the renderer frame that sent the original message that you are currently handling. You should use this method to "reply" to the sent message in order to guaruntee the reply will go to the correct process and frame.
* `reply` Function - A function that will send an IPC message to the renderer frame that sent the original message that you are currently handling. You should use this method to "reply" to the sent message in order to guarantee the reply will go to the correct process and frame.
* `...args` any[]

2
docs/api/structures/trace-config.md
View file

@ -21,7 +21,7 @@
with the trace.
* `memory_dump_config` Object (optional) - if the
`disabled-by-default-memory-infra` category is enabled, this contains
optional additional configuration for data callection. See the [Chromium
optional additional configuration for data collection. See the [Chromium
memory-infra docs][memory-infra docs] for more information.
An example TraceConfig that roughly matches what Chrome DevTools records: