TBR: reader: syncbase: s/yncGroup/yncgroup/

With this change, we establish a convention of treating
"syncgroup" as a single, common (non-proper) noun.

The main motivation for this change was consistency, for
a term that's used widely across our codebase and docs.

Arguments for "Syncgroup" over "SyncGroup" were:
- it's "Syncbase", not "SyncBase"
- we'd probably like to use "syncgroup" rather than
"sync_group" in snake-case text, e.g. in filenames like
"syncgroup_test.go"; using "SyncGroup" for camel-case
text would make these two inconsistent (Nick pointed
this out)
- avoids ambiguity about capitalization at the start of a
sentence vs. inside a sentence ("SyncGroup" vs.
"syncgroup"?)

(Note, I discussed this change with Bindu, Raja, and Nick
before making it.)

I mainly used 'find -exec perl -pi -e' to prepare this
change, plus manual inspection and tweaks. The main
painful part was updating lots of comments in the Syncbase
implementation to use "syncgroup" instead of "Syncgroup"
where that was the intended usage.

MultiPart: 9/11

Change-Id: Iec77c5e821f1315af1f6290f5fa148bd6014d867
1 file changed
tree: a9bd30688fdc53fc19265ccd5a15cedef20b3652
  1. android/
  2. web/
  3. .gitignore
  4. .jiriignore
  5. AUTHORS
  6. CONTRIBUTING.md
  7. CONTRIBUTORS
  8. LICENSE
  9. Makefile
  10. PATENTS
  11. README.md
  12. VERSION
README.md

Reader

An example multi-device PDF reader built using Vanadium on both the web and Android platforms. The web version requires use of the Vanadium Chrome extension.

All apps exchange information using Syncbase. Details of the various projects can be found in their respective directories.