fix: query string parameters are camelCased (#934)

* fix: query string parameters are camelCased

* review feedback

* fix: review feedback

Author: alexander-fenster

aip/general/0127.md

@@ -54,8 +54,10 @@ message CreateBookRequest {
 
   // The user-specified ID for the book.
   // When using HTTP/JSON, this field is populated based on a query string
-  // argument, such as `?book_id=foo`. This is the fallback for fields that
+  // argument, such as `?bookId=foo`. This is the fallback for fields that
   // are not included in either the URI or the body.
+  // Note that clients use camelCase format to communicate the field names
+  // to the service.
   string book_id = 3;
 }
 ```
@@ -127,6 +129,8 @@ rpc CreateBook(CreateBookRequest) returns (Book) {
 
 ## Changelog
 
+- **2022-08-18**: Added the comment that query string parameter names are
+  in camelCase.
 - **2021-01-06**: Added clarification around `body` and nested fields.
 - **2019-09-23**: Added a statement about request body encoding, and guidance
   discouraging `json_name`.