Update graph/patterns/enums.md

OlgaPodo · dkershaw10 · web-flow · commit 400d7ca8d0e6 · 2024-06-27T15:26:49.000-04:00
Co-authored-by: Dan Kershaw [MSFT] &lt;dkershaw10@users.noreply.github.com&gt;
diff --git a/graph/patterns/enums.md b/graph/patterns/enums.md
@@ -130,4 +130,4 @@ With such enum, customers can select multiple values in a single field:
 
 `displayMethod = tip | alert`
 
-In cases where two properties want to use the same *conceptual* `EnumType`, but one property is a collection while the other is single-values, the model should have *two* duplicate `EnumType`s, marking one as a flags enum and making its name the plural form of the non-flags enum.
+In cases where two properties want to use the same *conceptual* `EnumType`, but one property is a collection while the other is single-values, the model should define *two* separate `EnumType`s, one being a non-flags enum with a singular name and the other marked as a flags enum with its name being the plural form of the non-flags enum.

Original file line number	Diff line number	Diff line change
`@@ -130,4 +130,4 @@ With such enum, customers can select multiple values in a single field:`
`130`	`130`
`131`	`131`	`displayMethod = tip \| alert`
`132`	`132`
`133`		-In cases where two properties want to use the same conceptual `EnumType`, but one property is a collection while the other is single-values, the model should have two duplicate `EnumType`s, marking one as a flags enum and making its name the plural form of the non-flags enum.
	`133`	+In cases where two properties want to use the same conceptual `EnumType`, but one property is a collection while the other is single-values, the model should define two separate `EnumType`s, one being a non-flags enum with a singular name and the other marked as a flags enum with its name being the plural form of the non-flags enum.