diff --git a/phosphor-power-sequencer/README.md b/phosphor-power-sequencer/README.md
index 80a85ba..4783cc0 100644
--- a/phosphor-power-sequencer/README.md
+++ b/phosphor-power-sequencer/README.md
@@ -10,12 +10,12 @@
 
 ## JSON Configuration Files
 
-Configuration files are stored in the `config_files` directory.
-See the [Configuration File README](config_files/README.md) for details on the
-format of power sequencer configuration files.
+Configuration files are stored in the `config_files` directory. See the
+[Configuration File README](config_files/README.md) for details on the format of
+power sequencer configuration files.
 
 ## Source Files
 
-Source files are stored in the `src` directory.
-See the [Source Files README](src/README.md) for details on the design of the
+Source files are stored in the `src` directory. See the
+[Source Files README](src/README.md) for details on the design of the
 application source.
diff --git a/phosphor-power-sequencer/config_files/README.md b/phosphor-power-sequencer/config_files/README.md
index a5c3ed5..8e8dbc1 100644
--- a/phosphor-power-sequencer/config_files/README.md
+++ b/phosphor-power-sequencer/config_files/README.md
@@ -11,6 +11,7 @@
 configuration file.
 
 Example file name:
+
 ```
 UCD90320Monitor_mysystem.json
 ```
@@ -18,11 +19,12 @@
 ## File Format
 
 The configuration consists of an array of `rails` and an array of `pins`. Both
-`rails` and `pins` use a `name` element. The name element should be mnemonic
-and unique. If the BMC system utilizes the openpower-pels extension, then it
-will be used as an index into the `phosphor-logging` Message Registry.
+`rails` and `pins` use a `name` element. The name element should be mnemonic and
+unique. If the BMC system utilizes the openpower-pels extension, then it will be
+used as an index into the `phosphor-logging` Message Registry.
 
 Example 'rails' array with 'name' elements:
+
 ```
 "rails": [
     { "name": "12.0V" },
@@ -30,10 +32,11 @@
 ]
 ```
 
-The `pins` array also uses a `line` element which is the GPIO line number
-of the pgood pin in the power sequencer device.
+The `pins` array also uses a `line` element which is the GPIO line number of the
+pgood pin in the power sequencer device.
 
 Example 'pins' array with 'name' and 'line' elements:
+
 ```
 "pins": [
     {
@@ -54,6 +57,7 @@
 system or that a not present part would not cause a pgood failure.
 
 Example 'rails' array element including 'presence' element:
+
 ```
 {
     "name": "VCS1",
@@ -62,6 +66,7 @@
 ```
 
 Example 'pins' array element including 'presence' element:
+
 ```
 {
     "name": "VPCIE",
diff --git a/phosphor-power-sequencer/config_files/UCD90320Monitor_ibm,rainier.json b/phosphor-power-sequencer/config_files/UCD90320Monitor_ibm,rainier.json
index b489db2..f184c45 100644
--- a/phosphor-power-sequencer/config_files/UCD90320Monitor_ibm,rainier.json
+++ b/phosphor-power-sequencer/config_files/UCD90320Monitor_ibm,rainier.json
@@ -1,100 +1,100 @@
 {
     "rails": [
         {
-           "name": "12.0V"
+            "name": "12.0V"
         },
         {
-           "name": "5.0V_USB"
+            "name": "5.0V_USB"
         },
         {
-           "name": "5.0V_DASD"
+            "name": "5.0V_DASD"
         },
         {
-           "name": "3.3VA"
+            "name": "3.3VA"
         },
         {
-           "name": "3.3VB"
+            "name": "3.3VB"
         },
         {
-           "name": "1.5V"
+            "name": "1.5V"
         },
         {
-           "name": "1.1V"
+            "name": "1.1V"
         },
         {
-           "name": "VDDA_DCM0"
+            "name": "VDDA_DCM0"
         },
         {
-           "name": "VDDB_DCM0"
+            "name": "VDDB_DCM0"
         },
         {
-           "name": "VDDA_DCM1"
+            "name": "VDDA_DCM1"
         },
         {
-           "name": "VDDB_DCM1"
+            "name": "VDDB_DCM1"
         },
         {
-           "name": "12.0VCS"
+            "name": "12.0VCS"
         },
         {
-           "name": "3.3VCS"
+            "name": "3.3VCS"
         },
         {
-           "name": "1.1V_Current"
+            "name": "1.1V_Current"
         },
         {
-           "name": "5.0V_USB_Current"
+            "name": "5.0V_USB_Current"
         },
         {
-           "name": "5.0V_DASD_Current"
+            "name": "5.0V_DASD_Current"
         },
         {
-           "name": "12.0VN"
+            "name": "12.0VN"
         },
         {
-           "name": "12.0VP"
+            "name": "12.0VP"
         },
         {
-           "name": "12.0VQ"
+            "name": "12.0VQ"
         },
         {
-           "name": "12.0VR"
+            "name": "12.0VR"
         },
         {
-           "name": "ThermalDiode1"
+            "name": "ThermalDiode1"
         },
         {
-           "name": "ThermalDiode2"
+            "name": "ThermalDiode2"
         },
         {
-           "name": "ThermalDiode3"
+            "name": "ThermalDiode3"
         },
         {
-           "name": "ThermalDiode4"
+            "name": "ThermalDiode4"
         },
         {
-           "name": "VDN_DCM0"
+            "name": "VDN_DCM0"
         },
         {
-           "name": "VDN_DCM1"
+            "name": "VDN_DCM1"
         },
         {
-           "name": "VCS_DCM0"
+            "name": "VCS_DCM0"
         },
         {
-           "name": "VCS_DCM1"
+            "name": "VCS_DCM1"
         },
         {
-           "name": "VIO_DCM0"
+            "name": "VIO_DCM0"
         },
         {
-           "name": "VIO_DCM1"
+            "name": "VIO_DCM1"
         },
         {
-           "name": "VPCIE_DCM0"
+            "name": "VPCIE_DCM0"
         },
         {
-           "name": "VPCIE_DCM1"
+            "name": "VPCIE_DCM1"
         }
     ],
 
diff --git a/phosphor-power-sequencer/src/README.md b/phosphor-power-sequencer/src/README.md
index 21e6f3f..faabc60 100644
--- a/phosphor-power-sequencer/src/README.md
+++ b/phosphor-power-sequencer/src/README.md
@@ -27,9 +27,9 @@
 
 The `state` property is set to initiate a power on or power off sequence. The
 power good `pgood` property reflects the power state of the chassis. At power on
-time the `pgood` will lag the 'state` as the power sequencer performs its
-processing. The same lag will occur on a requested power off. Loss of `pgood`
-without a `state` change request indicates a pgood failure.
+time the `pgood` will lag the
+'state`as the power sequencer performs its processing. The same lag will occur on a requested power off. Loss of`pgood`without a`state`
+change request indicates a pgood failure.
 
 ### PowerSequencerMonitor