diff --git a/docs/control/README.md b/docs/control/README.md
index 39fa080..321912b 100644
--- a/docs/control/README.md
+++ b/docs/control/README.md
@@ -121,7 +121,7 @@
 This file consists of an array of fan objects representing the fan FRUs in the
 system.
 
-```
+```json
 [
     {
         "name": "fan0",
@@ -139,7 +139,7 @@
 
 This file contains parameters specific to the zone.
 
-```
+```json
 [
     {
         "name": "0",
@@ -159,7 +159,7 @@
 This file defines the groups that events.json will use in its actions. Groups
 consist of one or more D-Bus object paths and a name.
 
-```
+```json
 [
    {
      "name": "fan inventory",
@@ -183,7 +183,7 @@
 This file contains the fan control events, where each event can contain groups,
 trigger, and actions.
 
-```
+```json
 {
   [
     {
@@ -222,7 +222,7 @@
 The JSON data format does not support comments. However, the library used by
 code to parse the JSON does support '//' as a comment:
 
-```
+```json
 // This is a comment.
 {
    ...
@@ -231,7 +231,7 @@
 
 Alternatively, a comment attribute can be used:
 
-```
+```json
 {
   "comment": "This is a comment."
   ...
diff --git a/docs/control/debug.md b/docs/control/debug.md
index d3f9bf7..4eec15c 100644
--- a/docs/control/debug.md
+++ b/docs/control/debug.md
@@ -16,7 +16,7 @@
 
 It can be printed with:
 
-```
+```text
 fanctl query_dump -s flight_recorder
 ```
 
@@ -28,7 +28,7 @@
 
 It can be printed with:
 
-```
+```text
 fanctl query_dump -s objects
 ```
 
@@ -39,20 +39,20 @@
 
 Print the full entries of all temp sensors in the cache:
 
-```
+```text
 fanctl query_dump -s objects -n sensors/temperature
 ```
 
 Print just the Value properties of all temperature sensors in the cache:
 
-```
+```text
 fanctl query_dump -s objects -n sensors/temperature -p Value
 ```
 
 This allows one to do something like find all Functional property values that
 are false:
 
-```
+```text
 fanctl query_dump -s objects -p Functional | grep -B 1 false
 ```
 
@@ -63,7 +63,7 @@
 
 It can be printed with:
 
-```
+```text
 fanctl query_dump -s zones
 ```
 
@@ -73,7 +73,7 @@
 
 They can be printed with:
 
-```
+```text
 fanctl query_dump -s parameters
 ```
 
@@ -84,7 +84,7 @@
 
 It can be printed with:
 
-```
+```text
 fanctl query_dump -s services
 ```
 
@@ -95,6 +95,6 @@
 
 It can be printed with:
 
-```
+```text
 fanctl query_dump -s events
 ```
diff --git a/docs/control/events.md b/docs/control/events.md
index 9c15014..9482ead 100644
--- a/docs/control/events.md
+++ b/docs/control/events.md
@@ -16,36 +16,36 @@
 
 ## Example
 
-```
+```json
 [
-   {
-     "name": "fan(s) missing",
-     "groups": [
-       {
-         "name": "fan inventory",
-         "interface": "xyz.openbmc_project.Inventory.Item",
-         "property": { "name": "Present" }
-       }
-     ],
-     "triggers": [
-       {
-         "class": "init",
-         "method": "get_properties"
-       },
-       {
-         "class": "signal",
-         "signal": "properties_changed"
-       }
-     ],
-     "actions": [
-       {
-         "name": "count_state_before_target",
-         "count": 1,
-         "state": false,
-         "target": 15000
-       }
-     ]
-   }
+  {
+    "name": "fan(s) missing",
+    "groups": [
+      {
+        "name": "fan inventory",
+        "interface": "xyz.openbmc_project.Inventory.Item",
+        "property": { "name": "Present" }
+      }
+    ],
+    "triggers": [
+      {
+        "class": "init",
+        "method": "get_properties"
+      },
+      {
+        "class": "signal",
+        "signal": "properties_changed"
+      }
+    ],
+    "actions": [
+      {
+        "name": "count_state_before_target",
+        "count": 1,
+        "state": false,
+        "target": 15000
+      }
+    ]
+  }
 ]
 ```
 
@@ -68,7 +68,7 @@
 
 ## Groups
 
-```
+```json
 "groups": [
     {
         "name": "<name>",
@@ -104,10 +104,10 @@
 After invoking the configured method, any actions configured for this trigger
 will run.
 
-```
+```json
 {
-    "class": "init",
-    "method": "<method>"
+  "class": "init",
+  "method": "<method>"
 }
 ```
 
@@ -124,10 +124,10 @@
 Signal triggers subscribe to certain D-Bus signals for each member of its
 configured group. After handling the signal, any configured actions are run.
 
-```
+```json
 {
-    "class": "signal",
-    "signal": "<signal>"
+  "class": "signal",
+  "signal": "<signal>"
 }
 ```
 
@@ -160,12 +160,12 @@
 
 Timer triggers run actions after the configured type of timer expires.
 
-```
+```json
 {
-    "class": "timer",
-    "type": "<type>",
-    "interval": "<interval>",
-    "preload_groups": "<true/false>"
+  "class": "timer",
+  "type": "<type>",
+  "interval": "<interval>",
+  "preload_groups": "<true/false>"
 }
 ```
 
@@ -188,10 +188,10 @@
 
 Parameter triggers run actions after a parameter changes.
 
-```
+```json
 {
-    "class": "parameter",
-    "parameter": "<parameter>"
+  "class": "parameter",
+  "parameter": "<parameter>"
 }
 ```
 
@@ -204,10 +204,10 @@
 PowerOn triggers run when the power turns on. Functionally, they behave like an
 init trigger.
 
-```
+```json
 {
-    "class": "poweron",
-    "method": "<method>"
+  "class": "poweron",
+  "method": "<method>"
 }
 ```
 
@@ -220,10 +220,10 @@
 PowerOff triggers run when the power turns off. Functionally, they behave like
 an init trigger.
 
-```
+```json
 {
-    "class": "poweroff",
-    "method": "<method>"
+  "class": "poweroff",
+  "method": "<method>"
 }
 ```
 
@@ -274,16 +274,18 @@
 The group values can be compared to either a value hardcoded in the JSON, or a
 parameter value.
 
-```
+```json
 {
-    "name": "set_net_increase_target",
-    "groups": [{
-        "name": "pcie temps",
-        "interface": "xyz.openbmc_project.Sensor.Value",
-        "property": { "name": "Value" }
-      }],
-    "state": 70.0,
-    "delta": 255
+  "name": "set_net_increase_target",
+  "groups": [
+    {
+      "name": "pcie temps",
+      "interface": "xyz.openbmc_project.Sensor.Value",
+      "property": { "name": "Value" }
+    }
+  ],
+  "state": 70.0,
+  "delta": 255
 }
 ```
 
@@ -298,16 +300,18 @@
 
 2. Requests an increase of the largest calculated delta value, if there is one.
 
-```
+```json
 {
-    "name": "set_net_increase_target",
-    "groups": [{
-        "name": "proc0 core temps",
-        "interface": "xyz.openbmc_project.Sensor.Value",
-        "property": { "name": "Value" }
-      }],
-    "state_parameter_name": "proc_0_core_dvfs_increase_temp",
-    "delta": 300
+  "name": "set_net_increase_target",
+  "groups": [
+    {
+      "name": "proc0 core temps",
+      "interface": "xyz.openbmc_project.Sensor.Value",
+      "property": { "name": "Value" }
+    }
+  ],
+  "state_parameter_name": "proc_0_core_dvfs_increase_temp",
+  "delta": 300
 }
 ```
 
@@ -335,18 +339,19 @@
 The group values can be compared to either a value hardcoded in the JSON, or a
 parameter value.
 
-```
+```json
 {
-    "name": "set_net_decrease_target",
-    "groups": [{
-        "name": "pcie temps",
-        "interface": "xyz.openbmc_project.Sensor.Value",
-        "property": { "name": "Value" }
-      }],
-    "state": 65.0,
-    "delta": 80
+  "name": "set_net_decrease_target",
+  "groups": [
+    {
+      "name": "pcie temps",
+      "interface": "xyz.openbmc_project.Sensor.Value",
+      "property": { "name": "Value" }
+    }
+  ],
+  "state": 65.0,
+  "delta": 80
 }
-
 ```
 
 The above config uses a hardcoded state value:
@@ -360,16 +365,18 @@
 
 2. Requests a decrease of the smallest calculated delta value, if there is one.
 
-```
+```json
 {
-    "name": "set_net_decrease_target",
-    "groups": [{
-        "name": "proc 0 core temps",
-        "interface": "xyz.openbmc_project.Sensor.Value",
-        "property": { "name": "Value" }
-      }],
-    "state_parameter_name": "proc_0_core_dvfs_decrease_temp",
-    "delta": 50
+  "name": "set_net_decrease_target",
+  "groups": [
+    {
+      "name": "proc 0 core temps",
+      "interface": "xyz.openbmc_project.Sensor.Value",
+      "property": { "name": "Value" }
+    }
+  ],
+  "state_parameter_name": "proc_0_core_dvfs_decrease_temp",
+  "delta": 50
 }
 ```
 
@@ -391,13 +398,13 @@
 are at a configured state. Once the number of members at the given state falls
 below the configured count, the floor hold is released.
 
-```
+```json
 {
-    "name": "count_state_floor",
-    "count": 2,
-    "state": false,
-    "floor": 18000,
-    "delay": 3
+  "name": "count_state_floor",
+  "count": 2,
+  "state": false,
+  "floor": 18000,
+  "delay": 3
 }
 ```
 
@@ -412,12 +419,12 @@
 are at a configured state. Once the number of members at the given state falls
 below the configured count, active fan target changes are allowed.
 
-```
+```json
 {
-    "name": "count_state_before_target",
-    "count": 1,
-    "state": false,
-    "target": 18000
+  "name": "count_state_before_target",
+  "count": 1,
+  "state": false,
+  "target": 18000
 }
 ```
 
@@ -440,35 +447,34 @@
 values within certain ranges, where the key group chooses the set of tables in
 which to check the remaining group values.
 
-```
+```json
 {
   "name": "mapped_floor",
   "key_group": "ambient temp",
   "default_floor": 5555,
   "fan_floors": [
-   {
-     "key": 25,
-     "default_floor": 4444,
-     "floor_offset_parameter": "ambient_25_altitude_offset",
-     "floors": [
-       {
-         "parameter": "pcie_floor_index",
-         "floors": [
-           { "value": 1, "floor": 2000 },
-           { "value": 2, "floor": 3000 },
-           { "value": 3, "floor": 4000 },
-           { "value": 4, "floor": 5000 },
-           { "value": 5, "floor": 6000 }
-         ]
-       },
-       {
-         "group": "power save",
-         "floors": [
-            { "value": true, "floor": 1000 }
-         ]
-       }
-     ]
-   }
+    {
+      "key": 25,
+      "default_floor": 4444,
+      "floor_offset_parameter": "ambient_25_altitude_offset",
+      "floors": [
+        {
+          "parameter": "pcie_floor_index",
+          "floors": [
+            { "value": 1, "floor": 2000 },
+            { "value": 2, "floor": 3000 },
+            { "value": 3, "floor": 4000 },
+            { "value": 4, "floor": 5000 },
+            { "value": 5, "floor": 6000 }
+          ]
+        },
+        {
+          "group": "power save",
+          "floors": [{ "value": true, "floor": 1000 }]
+        }
+      ]
+    }
+  ]
 }
 ```
 
@@ -498,7 +504,7 @@
 For example, the following says the single member of the 'cpu 0' group must have
 its Model property be equal to "1234" for the action to run:
 
-```
+```json
     "groups": [{
         "name": "cpu 0",
         "interface": "xyz.openbmc_project.Inventory.Decorator.Asset",
@@ -521,15 +527,17 @@
 group is missing. Once all services are functional and providing all the group
 data again, active fan target changes are allowed.
 
-```
+```json
 {
-    "name": "set_target_on_missing_owner",
-    "groups": [{
-        "name": "fan inventory",
-        "interface": "xyz.openbmc_project.Inventory.Item",
-        "property": { "name": "Present" }
-      }],
-    "target": 18000
+  "name": "set_target_on_missing_owner",
+  "groups": [
+    {
+      "name": "fan inventory",
+      "interface": "xyz.openbmc_project.Inventory.Item",
+      "property": { "name": "Present" }
+    }
+  ],
+  "target": 18000
 }
 ```
 
@@ -544,13 +552,13 @@
 it will either revert to temperature control or activate the next-highest target
 remaining in its list of locks.
 
-```
+```json
 {
-    "name": "override_fan_target",
-    "count": 1,
-    "state": false,
-    "fans": [ "fan0", "fan1", "fan2", "fan3" ],
-    "target": 10000
+  "name": "override_fan_target",
+  "count": 1,
+  "state": false,
+  "fans": ["fan0", "fan1", "fan2", "fan3"],
+  "target": 10000
 }
 ```
 
@@ -574,11 +582,11 @@
 - The PCIe cards with the following properties: Function0DeviceId,
   Function0VendorId, Function0SubsystemId, Function0SubsystemVendorId
 
-```
+```json
 {
-    "name": "pcie_card_floors",
-    "use_config_specific_files": true,
-    "settle_time": 2
+  "name": "pcie_card_floors",
+  "use_config_specific_files": true,
+  "settle_time": 2
 }
 ```
 
@@ -604,14 +612,16 @@
 The `requested target base` value is the base value to apply a target delta to.
 By default, it's the current zone target unless modified by this action.
 
-```
+```json
 {
-    "name": "set_request_target_base_with_max",
-    "groups": [{
-        "name": "fan targets",
-        "interface": "xyz.openbmc_project.Fan.Target",
-        "property": { "name": "Target" }
-      }]
+  "name": "set_request_target_base_with_max",
+  "groups": [
+    {
+      "name": "fan targets",
+      "interface": "xyz.openbmc_project.Fan.Target",
+      "property": { "name": "Target" }
+    }
+  ]
 }
 ```
 
@@ -624,14 +634,14 @@
 value can be modified before storing it if the JSON specifies a valid modifier
 expression.
 
-```
+```json
 {
-   "name": "set_parameter_from_group_max",
-   "parameter_name": "proc_0_throttle_temp",
-   "modifier": {
-     "expression": "minus",
-     "value": 4
-   }
+  "name": "set_parameter_from_group_max",
+  "parameter_name": "proc_0_throttle_temp",
+  "modifier": {
+    "expression": "minus",
+    "value": 4
+  }
 }
 ```
 
@@ -680,27 +690,28 @@
 
 Consider the following action config:
 
-```
+```json
 {
-    "name": "call_actions_based_on_timer",
-    "timer": {
-        "interval": 5000000,
-        "type": "oneshot"
-    },
-    "actions": [{
-        "name": "test"
-    }]
+  "name": "call_actions_based_on_timer",
+  "timer": {
+    "interval": 5000000,
+    "type": "oneshot"
+  },
+  "actions": [
+    {
+      "name": "test"
+    }
+  ]
 }
-
 ```
 
 If its group configuration has a property value listed, like:
 
-```
+```json
 {
-    "name": "fan inventory",
-    "interface": "xyz.openbmc_project.Inventory.Item",
-    "property": { "name": "Present", "value": true }
+  "name": "fan inventory",
+  "interface": "xyz.openbmc_project.Inventory.Item",
+  "property": { "name": "Present", "value": true }
 }
 ```
 
@@ -710,11 +721,11 @@
 
 If the group configuration has no property value listed, like:
 
-```
+```json
 {
-    "name": "fan inventory",
-    "interface": "xyz.openbmc_project.Inventory.Item",
-    "property": { "name": "Present" }
+  "name": "fan inventory",
+  "interface": "xyz.openbmc_project.Inventory.Item",
+  "property": { "name": "Present" }
 }
 ```
 
@@ -730,23 +741,23 @@
 This allows an action to run with the latest values in the cache without having
 to subscribe to propertiesChanged for them all.
 
-```
+```json
 {
-   "name": "get_managed_objects",
-   "groups": [
-     {
-       "name": "proc temps",
-       "interface": "xyz.openbmc_project.Sensor.Value",
-       "property": { "name": "Value" }
-     }
-   ],
-   "actions": [
-     {
-       "name": "set_net_increase_target",
-       "state": 30,
-       "delta": 100
-     }
-   ]
+  "name": "get_managed_objects",
+  "groups": [
+    {
+      "name": "proc temps",
+      "interface": "xyz.openbmc_project.Sensor.Value",
+      "property": { "name": "Value" }
+    }
+  ],
+  "actions": [
+    {
+      "name": "set_net_increase_target",
+      "state": 30,
+      "delta": 100
+    }
+  ]
 }
 ```
 
@@ -763,7 +774,7 @@
 
 Subtract the `value` field from the passed in value.
 
-```
+```json
 "modifier": {
     "expression": "minus",
     "value": 4
@@ -779,7 +790,7 @@
 `default_value` field supplied, then that will be returned if the argument is
 greater than the `arg_value` of the last row.
 
-```
+```json
 "modifier": {
   "operator": "less_than",
   "default_value": 10000,
diff --git a/docs/control/fanctl/README.md b/docs/control/fanctl/README.md
index e0bcf9b..0a38371 100644
--- a/docs/control/fanctl/README.md
+++ b/docs/control/fanctl/README.md
@@ -23,7 +23,7 @@
 
 ## Usage
 
-```
+```text
 NAME
   fanctl - Manually control, get fan tachs, view status, reload config,
   and resume automatic control of all fans within a chassis.
@@ -76,7 +76,7 @@
 
   > fanctl get
 
-  ```
+  ```text
   > fanctl get
   TARGET SENSOR    TARGET(RPM)   FEEDBACK SENSOR    FEEDBACK(RPM)
   ===============================================================
@@ -98,7 +98,7 @@
 
   > fanctl status
 
-  ```
+  ```text
   Fan Control Service State   : loaded, inactive(dead)
 
   CurrentBMCState     : xyz.openbmc_project.State.BMC.BMCState.Ready
diff --git a/docs/control/fans.md b/docs/control/fans.md
index 28763ed..94a906c 100644
--- a/docs/control/fans.md
+++ b/docs/control/fans.md
@@ -2,7 +2,7 @@
 
 ## JSON Example
 
-```
+```json
 [
     {
         "name": "fan0",
diff --git a/docs/control/groups.md b/docs/control/groups.md
index 4391ddc..f13413e 100644
--- a/docs/control/groups.md
+++ b/docs/control/groups.md
@@ -8,16 +8,13 @@
 
 ## JSON example
 
-```
+```json
 [
   {
-     "name": "occ objects",
-     "service": "org.open_power.OCC.Control",
-     "members": [
-       "/org/open_power/control/occ0",
-       "/org/open_power/control/occ1"
-     ]
-   }
+    "name": "occ objects",
+    "service": "org.open_power.OCC.Control",
+    "members": ["/org/open_power/control/occ0", "/org/open_power/control/occ1"]
+  }
 ]
 ```
 
diff --git a/docs/control/zones.md b/docs/control/zones.md
index 71a8aab..40a4bcd 100644
--- a/docs/control/zones.md
+++ b/docs/control/zones.md
@@ -7,7 +7,7 @@
 
 ## JSON Example
 
-```
+```json
 {
   "name": "0",
   "poweron_target": 18000,
diff --git a/docs/monitor/README.md b/docs/monitor/README.md
index 34a746b..626916b 100644
--- a/docs/monitor/README.md
+++ b/docs/monitor/README.md
@@ -113,7 +113,7 @@
 includes creating error logs and/or powering off the system for a configured
 number of fans that are missing or nonfunctional.
 
-```
+```json
 {
   "fans": [
     {
@@ -178,7 +178,7 @@
 
 Example:
 
-```
+```json
 {
   "comments": [
    "Fan monitoring configuration of X-number of fans",
diff --git a/docs/monitor/method.md b/docs/monitor/method.md
index 38da92f..9d2858e 100644
--- a/docs/monitor/method.md
+++ b/docs/monitor/method.md
@@ -28,7 +28,7 @@
   - Time(in seconds) that each fan sensor must be calculated within range of a
     current target before being marked functional.
 
-```
+```text
 "method": "timebased",
 "allowed_out_of_range_time": 30,
 "functional_delay": 5
@@ -39,7 +39,8 @@
 this method being used.**
 
 - This is equivalent to above:
-  ```
+
+  ```text
   "allowed_out_of_range_time": 30,
   "functional_delay": 5
   ```
@@ -65,7 +66,7 @@
 - `count_interval` - The interval, in seconds, to check the feedback speed and
   increment/decrement the counter. Defaults to 1s if not present.
 
-```
+```text
 "method": "count",
 "count_interval": 5,
 "sensors": [
diff --git a/docs/presence/eeprom.md b/docs/presence/eeprom.md
index 006a48b..535f074 100644
--- a/docs/presence/eeprom.md
+++ b/docs/presence/eeprom.md
@@ -20,7 +20,7 @@
 The I2C bus and address string of the form BB-AAAA that is used by the I2C
 subsystem in sysfs.
 
-```
+```text
 "bus_address": "3-0050"
 ```
 
@@ -28,7 +28,7 @@
 
 The name of the eeprom driver in sysfs.
 
-```
+```text
 "driver_name": "at24"
 ```
 
@@ -38,7 +38,7 @@
 driver to the device in case the device takes some time to initialize after
 being plugged into power. If no delay is required, a value of zero can be used.
 
-```
+```text
 "bind_delay_ms": 1000
 ```
 
diff --git a/docs/presence/methods.md b/docs/presence/methods.md
index f840052..58c4d94 100644
--- a/docs/presence/methods.md
+++ b/docs/presence/methods.md
@@ -18,7 +18,7 @@
 determine fan presence. This is the name of the fan tach sensor located under
 the `/xyz/openbmc_project/sensors/fan_tach/` D-Bus path.
 
-```
+```text
 "type": "tach",
 "sensors": [
   "fan0_0"
@@ -32,7 +32,7 @@
 device tree bindings, where the event number is provided via the `key`
 attribute.
 
-```
+```text
 "type": "gpio",
 "key": 1,
 "physpath": "/sys/bus/i2c/devices/1-0001",