From 08c542b030795d43bed5a4039f5d408a26404ebe Mon Sep 17 00:00:00 2001
From: Ethan Honzik <105084033+EthanHonzikSPS@users.noreply.github.com>
Date: Mon, 22 Jul 2024 14:53:19 -0500
Subject: [PATCH] Dpe 135 naming rules (#88)
Removed reference to rule that doesn't existing in naming.md
---------
Signed-off-by: Ethan Honzik <105084033+EthanHonzikSPS@users.noreply.github.com>
Co-authored-by: Brandon Sahadeo <50463922+brandonsahadeo@users.noreply.github.com>
---
standards/naming.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/standards/naming.md b/standards/naming.md
index ff18749..c1accd9 100644
--- a/standards/naming.md
+++ b/standards/naming.md
@@ -30,7 +30,7 @@ When you consider the names to use for your path, endpoints and other components
- Names **MUST** be different for different concepts.
- Overly general names that are ambiguous within the context of the API and the larger ecosystem of APIs **MUST** be avoided (i.e. "identity", "notification-service", etc). They can lead to a misunderstanding of API concepts. Rather, choose specific names that accurately describe the API concept. - This is particularly important for names that define first-order API elements, such as resources. There is no definitive list of names to avoid, as every name must be evaluated in the context of other names.
- Names that may conflict with keywords in common programming languages **SHOULD NOT** be used.
-- Names **SHOULD** use abbreviations instead of long form names.
+- Names **SHOULD** use abbreviations instead of long form names.
## Text