docs: clarify camelCase usage for badge URL parameters in badge-urls.md

Author: jNullj

doc/badge-urls.md

@@ -6,13 +6,14 @@
 - The `NOUN` part of the route is:
   - singular if the badge message represents a single entity, such as the current status of a build (e.g: `/build`), or a more abstract or aggregate representation of the thing (e.g.: `/coverage`, `/quality`)
   - plural if there are (or may) be many of the thing (e.g: `/dependencies`, `/stars`)
-- Parameters should always be part of the route if they are required to display a badge e.g: `:packageName`.
+- Parameters should always be part of the route if they are required to display a badge e.g: `:packageName` and should be camelCase.
 - Common optional params like, `:branch` or `:tag` should also be passed as part of the route.
 - Query string parameters should be used when:
   - The parameter is related to formatting. e.g: `/appveyor/tests/:user/:repo?compact_message`.
   - The parameter is for an uncommon optional attribute, like an alternate registry URL.
   - The parameter triggers application of alternative logic, like version semantics. e.g: `/github/v/tag/:user/:repo?sort=semver`.
   - Services which require a url/hostname parameter always should use a query string parameter to accept that value. e.g: `/discourse/topics?server=https://meta.discourse.org`.
+  - Similar to parameters, query string parameters should be camelCase e.g: 'labelColor' and not 'label_color'.
 
 It is convention to use the following standard routes and abbreviations across services: