Update docs/security/smartcontracts.md

Author: kmurphypolygon

docs/security/smartcontracts.md

@@ -6,12 +6,12 @@ Smart contract codebases must be organized, readable, and understandable across
 
 Engineers tasked with developing such codebases follow industry-standard, secure coding practices and style guides, such as https://docs.soliditylang.org/en/latest/style-guide.html and https://github.com/coinbase/solidity-style-guide.
 
-## Internal Assessments
+## Internal assessments
 
-Polygon Labs application security teams are composed of Sr. & Staff security engineers that perform internal reviews on all code developed. This in-house expertise allows us to follow standard methodologies for audits using available tooling for static analyzing, line-by-line manual reviews, Fuzzing and Formal Verification where applicable.
+Polygon Labs application security teams are composed of Sr. & Staff security engineers that perform internal reviews on all code developed. This in-house expertise allows us to follow standard methodologies for audits using available tooling for static analyzing, line-by-line manual reviews, Fuzzing, and Formal Verification where applicable.
 
-## External Assessments
+## External assessments
 
-After internal reviews and based on a risk assessment, new smart contracts and major changes/upgrades are sent to reputable, tier 1 security consultancy organizations for a formal external security assessment. Polygon Labs periodically rotates vendors to ensure an unbiased view of the code.
+After internal reviews, and based on a risk assessment, new smart contracts and major changes/upgrades are sent to reputable, tier 1 security consultancy organizations for a formal external security assessment. Polygon Labs periodically rotates vendors to ensure an unbiased view of the code.
 
 Polygon Labs public reports are located here: [Security reports](reports.md)