From 65af30194cf2a849c72f7ea47122f5f56e3f51aa Mon Sep 17 00:00:00 2001
From: QuentinN42 <quentin@lieumont.fr>
Date: Wed, 15 Mar 2023 15:40:28 -0700
Subject: [PATCH] refactor: rewording

Signed-off-by: QuentinN42 <quentin@lieumont.fr>
---
 docs/security/index.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/security/index.rst b/docs/security/index.rst
index 744b39ab..c1d4f035 100644
--- a/docs/security/index.rst
+++ b/docs/security/index.rst
@@ -2,9 +2,10 @@
 Security consideration
 ======================
 
-It is crucial to follow security best practices while deploying a GraphQL application to production.
-GraphQL APIs are inherently prone to various security risks, but they can be reduced by taking appropriate precautions.
-Neglecting to do so can expose the API to vulnerabilities like credential leakage or denial of service attacks.
+As GraphQL is a query language, it allows users to use a wider pannel of inputs than traditional REST APIs.
+Due to this feature, GraphQL APIs are inherently prone to various security risks, but they can be reduced by taking
+appropriate precautions. Neglecting them can expose the API to vulnerabilities like credential leakage or denial of
+service attacks.
 
 
 In this section, we will discuss the most common security risks and how to mitigate them.