Adjust awkward grammar

Author: olaservo

docs/docs/learn/client-concepts.mdx

@@ -139,7 +139,7 @@ For a complete implementation of a server that respects roots, see the [filesyst
 
 #### Design Philosophy
 
-Roots serve as a coordination mechanism between clients and servers, not a security boundary. The specification requires servers to "SHOULD respect root boundaries," not "MUST enforce" them, because servers run code the client cannot control. This design is pragmatic: clients enforce security while roots communicate intent.
+Roots serve as a coordination mechanism between clients and servers, not a security boundary. The specification requires that servers "SHOULD respect root boundaries," and not that they "MUST enforce" them, because servers run code the client cannot control. This design is pragmatic: clients enforce security while roots communicate intent.
 
 Roots work best when servers are trusted or vetted, users understand their advisory nature, and the goal is preventing accidents rather than stopping malicious behavior. They excel at context scoping (telling servers where to focus), accident prevention (helping well-behaved servers stay in bounds), and workflow organization (such as managing project boundaries automatically).