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

---
 Conflicts-Group.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Conflicts-Group.md b/Conflicts-Group.md
index 7d0f35c..715dee4 100644
--- a/Conflicts-Group.md
+++ b/Conflicts-Group.md
@@ -3,9 +3,9 @@ Custom Anvil represent vanilla enchantment restriction by 1 concept called here
 
 ## General structure of a conflict group
 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)
+* 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)
 
 
 ## How do it work