diff --git a/onlp/applications/attributes.md b/onlp/applications/attributes.md
index 3042eec3..b001cb86 100644
--- a/onlp/applications/attributes.md
+++ b/onlp/applications/attributes.md
@@ -21,7 +21,7 @@ At a minimum this is supported by the Chassis OID to return the system identific
 Any OID that has an ONIE identifier (for example a pluggable module) should also support this attribute.
 
 ### The Asset Attribute
-The ONIE information structure is defined by the available TLV values defined in the ONIE [specification](https://opencomputeproject.github.io/onie/design-spec/hw_requirements.html)
+The ONIE information structure is defined by the available TLV values defined in the [ONIE specification](https://opencomputeproject.github.io/onie/design-spec/hw_requirements.html)
 
 The fields of the ```onlp_asset_info_t``` structure are defined by the ONLP API and evolve over time.
 This attribute should be implemented at a minimum by the Chassis OID to return important system information (like firmware revisions).
diff --git a/onlp/applications/sfp.md b/onlp/applications/sfp.md
index 52d11d83..9d9d7dd1 100644
--- a/onlp/applications/sfp.md
+++ b/onlp/applications/sfp.md
@@ -18,10 +18,10 @@ There are several useful fields in this structure:
 While calling ```onlp_sfp_info_get``` is sufficient to identify the inserted module there are several operational APIs provided to manage it.
 
 * Change the control signal status
-** Enable TX_DISABLE
-** Disable LP_MODE
+  Enable TX_DISABLE
+  Disable LP_MODE
 * Generic Read/Write Operations
-** Perform I2C byte and word reads on the given module (any device address).
+  Perform I2C byte and word reads on the given module (any device address).
 
 ## SFP Documentation