diff --git a/designs/device-tree-gpio-naming.md b/designs/device-tree-gpio-naming.md
index 2abd1d0..845fc8a 100644
--- a/designs/device-tree-gpio-naming.md
+++ b/designs/device-tree-gpio-naming.md
@@ -24,8 +24,8 @@
 
 ## Background and References
 The kernel [documentation][2] has a good summary of the GPIO subsystem. The
-specific field used to name the GPIO's in the DTS is `gpio-line-names`.
-This [patch][3] shows an example of naming the GPIO's for a system.
+specific field used to name the GPIOs in the DTS is `gpio-line-names`.
+This [patch][3] shows an example of naming the GPIOs for a system.
 
 GPIOs are used for arbitrary things. It's pretty hard to have a coherent naming
 scheme in the face of a universe of potential use-cases.
@@ -35,17 +35,17 @@
 emerge.
 
 ## Requirements
-- Ensure common function GPIO's within OpenBMC use the same naming convention
+- Ensure common function GPIOs within OpenBMC use the same naming convention
 
 ## Proposed Design
 Below are the standard categories. The "Pattern" in each section describes the
 naming convention and then the sub bullets list the common GPIO names to
 be used (when available on an OpenBMC system). This naming convention must be
-followed for all common GPIO's.
+followed for all common GPIOs.
 
-This list below includes all common GPIO's within OpenBMC. Any OpenBMC
-system which provides one of the below GPIO's must name it as listed in
-this document. This document must be updated as new common GPIO's are added.
+This list below includes all common GPIOs within OpenBMC. Any OpenBMC
+system which provides one of the below GPIOs must name it as listed in
+this document. This document must be updated as new common GPIOs are added.
 
 ### LEDs
 Pattern: `led-*`
@@ -116,7 +116,7 @@
 has changed since the last reboot. If it has, it indicates that a factory reset
 should be performed.
 
-### POWER Specific GPIO's
+### POWER Specific GPIOs
 Below are GPIO names specific to the POWER processor based servers.
 
 #### Special