Update function naming from CamelCase to camelCase,

to match what actually happens in the Arduino Universe

doc/CODING_STYLE.md

@@ -2024,14 +2024,14 @@ All such variables with static storage duration (i.e. statics and globals, see [
 
 > Regular functions have mixed case; accessors and mutators may be named like variables.
 
-Ordinarily, functions should start with a capital letter and have a capital letter for each new word (a.k.a. "[Camel Case][wikipedia:camel-case]" or "Pascal case"). Such names should not have underscores. Prefer to capitalize acronyms as single words (i.e. `StartRpc()`, not `StartRPC()`).
+Ordinarily, functions should start with a lower-case letter and have a capital letter for each new word (a.k.a. "[Camel Case][wikipedia:camel-case]" or "Pascal case"). Such names should not have underscores. Prefer to capitalize acronyms as single words (i.e. `startRpc()`, not `startRPC()`).
 
  [wikipedia:camel-case]: https://en.wikipedia.org/wiki/Camel_case
 
 ```c++
-AddTableEntry()
-DeleteUrl()
-OpenFileOrDie()
+addTableEntry()
+deleteUrl()
+openFileOrDie()
 ```
 
 (The same naming rule applies to class- and namespace-scope constants that are exposed as part of an API and that are intended to look like functions, because the fact that they're objects rather than functions is an unimportant implementation detail.)