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

💄 Fix grammatical issues

Browse source
This commit is contained in:
Sam Saccone 2015-05-23 18:44:58 -04:00
parent 30d815e28f
commit a642782a00
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/api/content-tracing.md
View file

@ -2,7 +2,7 @@
The `content-trace` module is used to collect tracing data generated by the
underlying Chromium content module. This module does not include a web interface
so you need to open `chrome://tracing/` in Chrome browser and load the generated
so you need to open `chrome://tracing/` in a Chrome browser and load the generated
file to view the result.
```javascript
@ -26,7 +26,7 @@ Get a set of category groups. The category groups can change as new code paths
are reached.
Once all child processes have acked to the `getCategories` request, `callback`
is called back with an array of category groups.
is invoked with an array of category groups.
## tracing.startRecording(categoryFilter, options, callback)
@ -43,7 +43,7 @@ have acked to the `startRecording` request, `callback` will be called back.
`categoryFilter` is a filter to control what category groups should be
traced. A filter can have an optional `-` prefix to exclude category groups
that contain a matching category. Having both included and excluded
category patterns in the same list would not be supported.
category patterns in the same list is not supported.
Examples:
@ -107,12 +107,12 @@ Get the current monitoring traced data.
Child processes typically are caching trace data and only rarely flush and send
trace data back to the main process. That is because it may be an expensive
operation to send the trace data over IPC, and we would like to avoid much
operation to send the trace data over IPC, and we would like to avoid unneeded
runtime overhead of tracing. So, to end tracing, we must asynchronously ask all
child processes to flush any pending trace data.
Once all child processes have acked to the `captureMonitoringSnapshot` request,
`callback` will be called back with a file that contains the traced data.
the `callback` will be invoked with a file that contains the traced data.
## tracing.getTraceBufferUsage(callback)