From 8ef4e2b50c8db94e340081094494ff9d4ff16637 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= <dan@kosli.com>
Date: Wed, 21 Jan 2026 14:42:44 +0100
Subject: [PATCH] docs: remove tilde in naming conventions

---
 .../plan_organizational_structure/naming_conventions/_index.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs.kosli.com/content/implementation_guide/phase_2/plan_organizational_structure/naming_conventions/_index.md b/docs.kosli.com/content/implementation_guide/phase_2/plan_organizational_structure/naming_conventions/_index.md
index 771326eda..ff3bd7420 100644
--- a/docs.kosli.com/content/implementation_guide/phase_2/plan_organizational_structure/naming_conventions/_index.md
+++ b/docs.kosli.com/content/implementation_guide/phase_2/plan_organizational_structure/naming_conventions/_index.md
@@ -22,7 +22,7 @@ The general guidelines should be considered best practices for all naming conven
 
 
 1. **Choose Delimiter**: Choose a delimiter that works for your and stick with it consistently.</br>
-For example hyphen `-`, underscore `_`, tilde `~` or dot `.`. </br>
+For example hyphen `-`, underscore `_`, or dot `.`. </br>
 Avoid mixing delimiters within the same naming scheme.
 2. **Choose case style for elements**: Choose a meaningful case style across elements (e.g., PascalCase, camelCase, snake_case) and use it consistently. Avoid spaces and clashes with delimiters.
 3. **Keep it concise**: Shorter names are easier to read and remember. Aim for concise but descriptive names.