From 4799b421240ee6c3200f788de53c2addbaf97e99 Mon Sep 17 00:00:00 2001 From: Rohan Santhosh Kumar <181558744+Rohan5commit@users.noreply.github.com> Date: Mon, 27 Apr 2026 10:40:42 +0800 Subject: [PATCH] docs: fix enum guidance typo --- graph/patterns/enums.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/graph/patterns/enums.md b/graph/patterns/enums.md index 080435af..d5db72b1 100644 --- a/graph/patterns/enums.md +++ b/graph/patterns/enums.md @@ -69,7 +69,7 @@ By using an evolvable enum, instead, all we need to do is to add new members: ``` -Similarly speaking, if you find yourself using a `nullable` Enum, that is a indication that maybe what you are trying to model is something that has 3 states and an enum is more appropraite. For instance, let's assume we have a boolean property called `syncEnabled`, where `null` means that the value is undefined and inherited from the general tenant configuration. Instead of modelling like a boolean: +Similarly speaking, if you find yourself using a `nullable` Enum, that is a indication that maybe what you are trying to model is something that has 3 states and an enum is more appropriate. For instance, let's assume we have a boolean property called `syncEnabled`, where `null` means that the value is undefined and inherited from the general tenant configuration. Instead of modelling like a boolean: ```xml