From bdd63fd54d7a8ffcdf961450751fc6719ddfdd16 Mon Sep 17 00:00:00 2001
From: Sven Schmidt <0xsven@gmail.com>
Date: Tue, 30 Jun 2020 18:02:26 +0200
Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9A=20Fix=20typo=20in=20create-node=20?=
 =?UTF-8?q?docs=20(#693)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/create-node.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/create-node.md b/docs/create-node.md
index aa1939398..183c11c73 100644
--- a/docs/create-node.md
+++ b/docs/create-node.md
@@ -135,7 +135,7 @@ When a node can perform multiple operations like edit and delete some kind of en
 Some nodes may need a lot of options. Add only the very important ones to the top level and for all others, create an "Options" parameter where they can be added if needed. This ensures that the interface stays clean and does not unnecessarily confuse people. A good example of that would be the XML node.
 
 
-### Follow exiting parameter naming guideline
+### Follow existing parameter naming guideline
 
 There is not much of a guideline yet but if your node can do multiple things, call the parameter which sets the behavior either "mode" (like "Merge" and "XML" node) or "operation" like the most other ones. If these operations can be done on different resources (like "User" or "Order) create a "resource" parameter (like "Pipedrive" and "Trello" node)