diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/index.md b/docs/2._Services_Portfolio/Hardware_Portfolio/index.md
index 29f7c251..7ea1ddef 100644
--- a/docs/2._Services_Portfolio/Hardware_Portfolio/index.md
+++ b/docs/2._Services_Portfolio/Hardware_Portfolio/index.md
@@ -6,4 +6,4 @@ Whereas our Services section describes our ongoing operational infrastructure an
 
 "If I select Hardware Platform X for my beamline or accelerator subsystem, what exact level of hardware, software driver, UI, and operational support will the Controls Section provide?"
 
-Not all hardware connected to EPICS receives the same level of institutional support. Choosing a Tier 1 (Turnkey Standard) platform guarantees that Controls stocks spare parts on-site, builds and tests the crate, actively develops or maintains the EPICS driver, provides ready-to-use caQtDM screens, and supports hardware swaps during 24/7 Pikett shifts. Conversely, choosing specialized third-party or legacy hardware places spare-part stocking and physical diagnostics on the instrument group, with Controls providing integration via community drivers or configuration-only support.
+Not all hardware connected to EPICS receives the same level of institutional support. Choosing a Tier 1 (Turnkey Standard) platform guarantees that Controls stocks spare parts on-site, builds and tests the crate, actively develops or maintains the EPICS driver, provides ready-to-use caQtDM screens, and supports hardware swaps during 24/7 Pikett shifts. Conversely, choosing specialized third-party or legacy hardware places spare-part stocking and physical diagnostics on the end user, with Controls providing integration via community drivers or configuration-only support.
\ No newline at end of file