This is fine, but it would also be useful to show an example where some of the JSON fields were not a string, but an integer or a boolean, to show the case where not everything is a string value (and avoid user errors due to using, say, `"true"`  or `"42"` instead of `true` or `42`).... that of course in case there exist non-stringy settable parameters!