Update guidelines to reference using the design system as the "standard"

[Spark450]

Describe the problem

Background We have observed variability in how teams reference and utilize the design system across different projects. To ensure consistency and high quality in design across all digital interfaces, it's critical to update our content guidelines to reflect the design system as a "standard" that must be adhered to, rather than a recommendation.

Acceptance Criteria Review and revise all existing documentation to incorporate firm language that communicates the design system is the "standard".

Additional context

No response