Fixing formatting

docs/specs/subblocks.md

@@ -27,18 +27,18 @@ be ignored if received. If the _subType_ field is missing then it should default
   See [pointset event](../../tests/schemas/events_pointset/example.json)) as example. Messages
   with a defaulted `event` type represent raw telemetry from the device, while an explicit `event`
   type means the messages has been processed by the intermediate pipeline in some form.
-* **state**: Device state for this subblock. Unlike a
+* `state`: Device state for this subblock. Unlike a
   [comprehensive device state message](../../tests/schemas/state/example.json)
   this message contains information _only_ for a single subblock. Used for reporting any 'sticky'
   state from a device that has been processed and separated out by the UDMIS pipeline. A specical
   _subFolder_ of `update` indicates a complete state message and should generally be ignored by
   consuming applications.
-* **config**: A confirmed device config update for this subblock. Unlike a
+* `config`: A confirmed device config update for this subblock. Unlike a
   [comprehensive device config message](../../tests/schemas/config/example.json)
   this message contains information _only_ for a single subblock. This message is injected after
   the config update has been applied to the device as an effective confirmation of an applied
   config change.
-* **model**: Model-based description of this device(so does not correspond to any to/from device
+* `model`: Model-based description of this device(so does not correspond to any to/from device
   message). This message is generated by various tools (such as `registrar`) that manipulate the
   cloud-based provisioning and setup of the device. Generally, this is a live reflection of the
   device's `site_model` contents.
@@ -55,5 +55,5 @@ of interest (and values not relevant to any given application should be ignored)
 * `gateway`: How devices are connected together in a logical structure to proxy information from
   legacy (non-UDMI) fieldbus protocols.
 * `discovery`: Raw information from on-prem discovery about on-prem configuration and setup.
-* cloud: How a device is represented or connects to cloud infrastructure (e.g. the authentication
+* `cloud`: How a device is represented or connects to cloud infrastructure (e.g. the authentication
   key type).