Change category from 'mandatory' to 'required'

Author: rcseacord

src/coding-guidelines/values.rst

@@ -8,15 +8,15 @@ Values
 
 .. guideline:: Do not create values from uninitialized memory
    :id: gui_uyp3mCj77FS8
-   :category: mandatory
+   :category: required
    :status: draft
    :release: <TODO>
    :fls: fls_6lg0oaaopc26
    :decidability: undecidable
    :scope: system
    :tags: undefined-behavior, unsafe
 
-   A program shall not create a typed value from uninitialized memory.
+   Do not create a typed value from uninitialized memory.
    Types that explicitly permit an uninitialized state (e.g., ``MaybeUninit<T>`` or a union that includes ``()``) may hold uninitialized bytes as values,
    but reading any specific typed field still requires initialized and valid bytes. 
 
@@ -30,7 +30,7 @@ Values
       :id: rat_kjFRrhpS8Wu6
       :status: draft
 
-      Rust’s memory model treats all types as having an invariant that all bytes must be initialized before a value may be constructed.
+      Rust’s memory model requires that all bytes are initialized before a typed value may be constructed.
       Reading uninitialized memory:
 
       - creates undefined behavior for most types,