From a153f87fba26d7099926fd9f65feb954b461db77 Mon Sep 17 00:00:00 2001
From: Boaz Poolman <boaz_skater@hotmail.com>
Date: Sat, 14 Oct 2023 17:49:31 +0200
Subject: [PATCH] docs: Fix issue in readme

---
 README.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index c2570a6..f1b2b1c 100644
--- a/README.md
+++ b/README.md
@@ -346,14 +346,6 @@ Example:
 
 > `required:` NO | `type:` array
 
-#### JSON fields
-
-This property can accept an array of field names from the type. It is meant to specify the JSON fields on the type so the plugin can better format the field values when calculating the config difference.
-
-###### Key: `jsonFields`
-
-> `required:` NO | `type:` array
-
 #### Components
 
 This property can accept an array of component names from the type. Strapi Components can be included in the export/import process. With "." nested components can also be included in the process.
@@ -364,11 +356,19 @@ customTypes: [{
   uid: 'name',
   components: ['ParentComponentA', 'ParentComponentA.ChildComponent', 'ParentComponentB']
 }],
+```
 
 ###### Key: `components`
 
 > `required:` NO | `type:` array
 
+#### JSON fields
+
+This property can accept an array of field names from the type. It is meant to specify the JSON fields on the type so the plugin can better format the field values when calculating the config difference.
+
+###### Key: `jsonFields`
+
+> `required:` NO | `type:` array
 
 ## 🔍 Naming convention
 All the config files written in the sync directory have the same naming convention. It goes as follows: