The documentation uses both 'MS Teams' and 'Microsoft Teams' inconsistently across many files. 'Microsoft Teams' is the official product name and is used in formal references (configuration-reference.md, channels/index.md), while 'MS Teams' appears in ~20 locations across inline lists, channel docs, and tool references.
Examples of inconsistency
docs/tools/plugin.md:71: Plugin table header says 'Microsoft Teams' but the link text says 'MS Teams'docs/channels/msteams.md: Uses 'MS Teams' throughoutdocs/gateway/configuration-reference.md:572: Uses 'Microsoft Teams'docs/tools/index.md:451,455,456: Uses 'MS Teams'docs/cli/message.md:12,36: Uses 'MS Teams'
Recommendation
Standardize on 'Microsoft Teams' for formal/full references and decide if 'MS Teams' is acceptable as shorthand in space-constrained contexts (inline lists, table cells). Currently the usage is inconsistent even within the same page.
The documentation uses both 'MS Teams' and 'Microsoft Teams' inconsistently across many files. 'Microsoft Teams' is the official product name and is used in formal references (configuration-reference.md, channels/index.md), while 'MS Teams' appears in ~20 locations across inline lists, channel docs, and tool references.
Examples of inconsistency
docs/tools/plugin.md:71: Plugin table header says 'Microsoft Teams' but the link text says 'MS Teams'docs/channels/msteams.md: Uses 'MS Teams' throughoutdocs/gateway/configuration-reference.md:572: Uses 'Microsoft Teams'docs/tools/index.md:451,455,456: Uses 'MS Teams'docs/cli/message.md:12,36: Uses 'MS Teams'Recommendation
Standardize on 'Microsoft Teams' for formal/full references and decide if 'MS Teams' is acceptable as shorthand in space-constrained contexts (inline lists, table cells). Currently the usage is inconsistent even within the same page.