Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 21 Packages Projects Releases Wiki Activity

Hyphenate "brick-by-brick" for consistency (#36611)

Browse Source 
The last instance is hyphenated, and I believe this is how we've been
using it internally.
This commit is contained in:
Steven Palmesano
2025-12-05 17:41:14 +09:00
committed by GitHub
parent 84de32d882
commit ac5cf2ef26
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/the-mdm-mirgration-reality.md
+2 -2
View File
@@ -21,7 +21,7 @@ It’s easy to think that device reassignment equals *“done.”* It doesn’t.
## Key steps for a successful migration
To navigate this complexity and ensure a smooth, low-disruption transition, follow a structured **brick by brick** approach:
To navigate this complexity and ensure a smooth, low-disruption transition, follow a structured **brick-by-brick** approach:
1. **Audit and rationalize:**
Document every setting, policy, app, and scope within your old MDM. Use this opportunity to shed unnecessary policies and define your desired end state for the new MDM.
@@ -41,7 +41,7 @@ To navigate this complexity and ensure a smooth, low-disruption transition, foll
Migration gets easier with Apple’s new tools, but it still takes real work. If you’re planning a move and want help working through the details, we’ve done this many times and are happy to share what we’ve learned.
Our **brick by brick** approach focuses on auditing your current setup, carefully staging the new one, and keeping the transition clean and predictable.
Our **brick-by-brick** approach focuses on auditing your current setup, carefully staging the new one, and keeping the transition clean and predictable.
If you’re considering a migration and want to avoid surprises, let us know. We can share more about how the brick-by-brick method works.