From 892c2655266050d2b68957a4025ee5ea7791c5a6 Mon Sep 17 00:00:00 2001
From: alexcrea <42614139+alexcrea@users.noreply.github.com>
Date: Sun, 14 Jul 2024 16:31:01 +0200
Subject: [PATCH] Updated Conflicts Group (markdown)

---
 Conflicts-Group.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Conflicts-Group.md b/Conflicts-Group.md
index 715dee4..e47782e 100644
--- a/Conflicts-Group.md
+++ b/Conflicts-Group.md
@@ -2,10 +2,10 @@
 Custom Anvil represent vanilla enchantment restriction by 1 concept called here "Conflict Group" sometimes just called "conflict".
 
 ## General structure of a conflict group
-Conflict groups contain: \
+Conflict groups contain:
 * A list of enchantment (will be called "conflict enchantments". Alternatively called "enchantments" in the config file). \
 * A list of material group that will not be affected by the conflict (will be called "conflict material groups". Alternatively called "notAffectedGroups" in the config file). \
-* And the number of enchantment in the previously mentioned enchantment list an item need to contain before the conflict is considered active (will be called "maxBeforeConflict". Alternatively called "maxEnchantmentBeforeConflict" in the config file)
+* The number of enchantments in the previously mentioned enchantment list an item need to contain before the conflict is considered active (will be called "maxBeforeConflict". Alternatively called "maxEnchantmentBeforeConflict" in the config file)
 
 
 ## How do it work