From d8b43ac3db7520c26e0dc9efea747430c4d8bf63 Mon Sep 17 00:00:00 2001
From: Allen Houchins <32207388+allenhouchins@users.noreply.github.com>
Date: Thu, 10 Apr 2025 16:43:12 -0500
Subject: [PATCH] Update teams.md (#28080)

Updated casing on team names.
---
 articles/teams.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/articles/teams.md b/articles/teams.md
index d786831c55..19fe65dff6 100644
--- a/articles/teams.md
+++ b/articles/teams.md
@@ -21,8 +21,8 @@ Fleet's best practice teams:
 - `☁️ Servers`: Security team's production servers.
 - `☁️🐣 Servers (canary)`: Security team's test servers.
 - `Compliance exclusions`: All contributors' test work computers or virtual machines (VMs). Used for validating workflows for Fleet customers or reproducing bugs in the Fleet product.
-- `📱🏢 Company-owned Mobile Devices`: iPhones and iPads purchased by the organization that enroll to Fleet automatically via Apple Business Manager. For example, iPhones used by iOS Engineers or conference room iPads.
-- `📱🔐 Personal Mobile Devices`: End users' personal Android devices or iPhones, like those enrolled through a BYOD program, that have access to company resources.
+- `📱🏢 Company-owned mobile devices`: iPhones and iPads purchased by the organization that enroll to Fleet automatically via Apple Business Manager. For example, iPhones used by iOS Engineers or conference room iPads.
+- `📱🔐 Personal mobile devices`: End users' personal Android devices or iPhones, like those enrolled through a BYOD program, that have access to company resources.
 
 If some of your hosts don't fit into the teams listed above, consider their purpose. This will help determine their risk and compliance requirements, which in turn define their security baseline and appropriate team in Fleet. If these hosts have distinct compliance needs and security baselines, it's advisable to create a new team in Fleet.