Changes to site documentation

Mostly just formatting fixes with a few grammatical changes.

Two real notable changes:
  - Removed references to SkGLCanvas from Tips & FAQ and replaced with
    references to `SkDevice` and `SkSurface`.
  - Deleted deprecated "Quick Start Guides" folder

Docs-Preview: https://skia.org/?cl=92361
Bug: skia:
Change-Id: Ief790b1c2bae8fe0e39aa8d66c79f80560d18c9e
Reviewed-on: https://skia-review.googlesource.com/92361
Reviewed-by: Heather Miller <hcm@google.com>
Reviewed-by: Joe Gregorio <jcgregorio@google.com>
Commit-Queue: Joe Gregorio <jcgregorio@google.com>

3 files changed, 10 insertions, 10 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.
 
diff --git a/site/dev/chrome/multi_repo_trybots.md b/site/dev/chrome/multi_repo_trybots.md
index 4c6f09da45..34a8d96f12 100644
--- a/site/dev/chrome/multi_repo_trybots.md
+++ b/site/dev/chrome/multi_repo_trybots.md
@@ -67,7 +67,7 @@ possible to patch the files manually by adding the following to
       },
 
 Then, copy all 'out of tree' files into \<chromium>/src/patch/, using the same
-directory structure used by Chromium. When 'gclient runhooks' is run, the files
+directory structure used by Chromium. When `gclient runhooks` is run, the files
 in \<chromium>/src/patch/ will be copied to and overwrite corresponding files in
 \<chromium>/src/. For example, if changing \<skia>/include/core/SkPath.h, place
 a copy of the modified SkPath.h at
@@ -80,5 +80,5 @@ https://crrev.com/1866773002/#ps20001 .
 Try the patch
 -------------
 After committing a \<chromium>/src/DEPS or \<chromium>/src/patch/ change
-locally, 'git cl upload' can be used in the usual way. Be sure to add
-'COMMIT=false' to the issue description to avoid accidentally checking it in.
+locally, `git cl upload` can be used in the usual way. Be sure to add
+`COMMIT=false` to the issue description to avoid accidentally checking it in.
diff --git a/site/dev/chrome/repo.md b/site/dev/chrome/repo.md
index 545f154a2a..eaa658571a 100644
--- a/site/dev/chrome/repo.md
+++ b/site/dev/chrome/repo.md
@@ -6,9 +6,9 @@ To work on Skia inside a Chromium checkout, run the following:
     cd chromium/src/third_party/skia
     python tools/git-sync-deps
 
-This command does a minimal "just sync the DEPS" emulation of gclient sync for
-Skia into chromium/src/third_party/skia/third_party.  After that, make dm or
-./gyp_skia && ninja -C out/Debug dm in chromium/src/third_party/skia will get
+This command does a minimal "just sync the DEPS" emulation of `gclient sync` for
+Skia into chromium/src/third_party/skia/third_party.  After that, `make dm` or
+`./gyp_skia && ninja -C out/Debug dm` in chromium/src/third_party/skia will get
 you rolling.
 
 We no longer recommend the .gclient file manipulation to have Chromium DEPS also