diff --git a/doc/guides/collaborator-guide.md b/doc/guides/collaborator-guide.md
index b8189cfd3d3f4e..2791d2a2e508ed 100644
--- a/doc/guides/collaborator-guide.md
+++ b/doc/guides/collaborator-guide.md
@@ -30,7 +30,7 @@
   * [Technical HOWTO](#technical-howto)
   * [Troubleshooting](#troubleshooting)
   * [I made a mistake](#i-made-a-mistake)
-  * [Long term support](#long-term-support)
+  * [Long Term Support](#long-term-support)
     * [What is LTS?](#what-is-lts)
     * [How are LTS branches managed?](#how-are-lts-branches-managed)
     * [How can I help?](#how-can-i-help)
@@ -737,7 +737,7 @@ git push upstream master
     change.
   * Post to `#node-dev` (IRC) if you force push.
 
-### Long term support
+### Long Term Support
 
 #### What is LTS?
 
diff --git a/doc/guides/technical-values.md b/doc/guides/technical-values.md
index 1f074409dbe680..b86f2243896147 100644
--- a/doc/guides/technical-values.md
+++ b/doc/guides/technical-values.md
@@ -43,7 +43,7 @@ Some key elements of this include:
 * Stable releases on a predictable schedule
 * A strong safety net, including testing how changes
   in Node.js affect popular packages
-* Careful consideration of what goes into long term support (LTS) releases
+* Careful consideration of what goes into Long Term Support (LTS) releases
 
 ### 3 - Operational qualities
 We value keeping Node.js safe, performant, and lightweight.