aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/dev/chrome/commandbuffer.md
diff options
context:
space:
mode:
Diffstat (limited to 'site/dev/chrome/commandbuffer.md')
-rw-r--r--site/dev/chrome/commandbuffer.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/site/dev/chrome/commandbuffer.md b/site/dev/chrome/commandbuffer.md
index 2afa5c9194..b14a1e96ec 100644
--- a/site/dev/chrome/commandbuffer.md
+++ b/site/dev/chrome/commandbuffer.md
@@ -10,13 +10,13 @@ the command buffer as a shared library and thus no GYP/GN flags are
required.
The command buffer standalone shared library is built in a Chromium checkout
-by building the 'command_buffer_gles2' target. The command buffer should be
-built with the is_component_build in GN set to false. This will produce a .so,
+by building the `command_buffer_gles2` target. The command buffer should be
+built with the `is_component_build` in GN set to false. This will produce a .so,
.dylib, or .dll depending on the target OS. This should be copied alongside
the dm or nanobench executable built from a Skia repository.
-Both tools have a 'commandbuffer' config which can be used with the --config
+Both tools have a `commandbuffer` config which can be used with the `--config`
option to the tool and will run the tests or benchmarks using the command buffer
library. Unit tests in dm always run on all appropriate and available backends
-regardless of the --config flag.
+regardless of the `--config` flag.