From a278d7ee81404c2a0c8eb28d197ae3b3355d89ae Mon Sep 17 00:00:00 2001
From: kasjankotyniarsp <77441363+kasjankotyniarsp@users.noreply.github.com>
Date: Tue, 3 Oct 2023 14:07:42 +0000
Subject: [PATCH] Just testing

---
 docs/guides/getting_started/Key-Concepts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guides/getting_started/Key-Concepts.md b/docs/guides/getting_started/Key-Concepts.md
index 05c2cae86..410559299 100644
--- a/docs/guides/getting_started/Key-Concepts.md
+++ b/docs/guides/getting_started/Key-Concepts.md
@@ -31,7 +31,7 @@ The general idea is that the more often you stick to our conventions, the less t
 
 Voucherify doesn't want to enforce any rigid structures. After all, the only required action is to call the redemption method and provide something to redeem. We believe this approach should give your team the freedom and flexibility to respond to opportunities and changing demands.
 
-## Voucherify objects
+## Voucherify objects Test
 
 When you visit Voucherify [API reference](ref:introduction-1), you'll notice that the platform provides CRUD endpoints for every object which takes part in the promotion workflow. Let's run through the most important ones.