diff --git a/src/content/docs/style-guide/capitalization/product-capability-feature-usage.mdx b/src/content/docs/style-guide/capitalization/product-capability-feature-usage.mdx
index 6918f947b2e..9fb39e58686 100644
--- a/src/content/docs/style-guide/capitalization/product-capability-feature-usage.mdx
+++ b/src/content/docs/style-guide/capitalization/product-capability-feature-usage.mdx
@@ -9,7 +9,15 @@ In general, we use [title case](https://en.wikipedia.org/wiki/Title_case) for ou
 
 In general, outside of these product and UI guidelines, use sentence case capitalization.
 
-Do not use acronyms specific to or coined by New Relic externally; only use industry-recognized acronyms such as APM externally.
+## Acronyms
+
+In general, we follow the [Microsoft Writing Style Guide recommendations](https://learn.microsoft.com/en-us/style-guide/acronyms) for acronyms, with one exception. Unlike Microsoft style, a few of our product, capability, and feature names are used as acronyms—after spelling out in the first occurrence. For example, New Relic Application Performance Monitoring (New Relic APM) and New Relic Query Language (NRQL).
+
+The following are a few key guidelines when using acronyms:
+* Spell out the first occurrence of the acronym followed by the acronym in parentheses.
+* Lowercase all words when spelling out the acronym, except for proper nouns.  
+* Avoid using the acronym in a title or heading, even if it's the first occurrence. Exception: For brevity, it may be necessary to use an acronym in the first occurrence in a title or heading for space considerations.
+* Don't use acronyms specific to or coined by New Relic externally; only use industry-recognized acronyms such as APM externally.
 
 <Callout variant="important">
   Find capitalization guidelines for [user types](/docs/style-guide/word-choice/user-related-language-guidelines#styles) and [product editions](/docs/style-guide/word-choice/pricing-language-guidelines#style-format).