Skip to content

doc: revise Style Guide

Rodrigo Muino Tomonari requested to merge github/fork/Trott/style-guide-revisions into master

Most important change here is to point people to the YAML material in the docs rather than the previous way we indicated versions that introduced or deprecated APIs.

Otherwise, a bunch of stylistic changes, mostly to keep things concise and direct.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports