diff --git a/docpage/docs/Component.md b/docpage/docs/Component.md
index 7dd275cd..7861df54 100644
--- a/docpage/docs/Component.md
+++ b/docpage/docs/Component.md
@@ -6,10 +6,6 @@ sidebar_position: 5
 
 The component subsection is used in all Elements like Kafka, OSCAR, and the Generic one. A component alters the workflow's operation by employing Apache NiFi Processors. The Processor's name, execution time and the node on which it runs (ALL or PRIMARY) must be indicated.
 
-## Importance of Process Names
-
-To make effective adjustments, it is necessary to know the names of the Processors that comprise the ProcessGroup. This knowledge enables targeted changes, ensuring that the workflow operates as intended.
-
 
 ## Time Execution
 
diff --git a/docpage/docs/Connections.md b/docpage/docs/Connections.md
index 2b970118..c814760b 100644
--- a/docpage/docs/Connections.md
+++ b/docpage/docs/Connections.md
@@ -4,9 +4,9 @@ sidebar_position: 7
 
 # Connections
 
-The Connections section defines the links between Sources and Destinations. It is declared at the same level as Source and Destination, and you have to use the identifier name of the Element to create the connection.The use of [Alterations](/docs/Alterations) does not affect the connection between the elements; the connection is made transparently.
+The Connections section defines the links between Sources and Destinations. It is declared at the same level as Source and Destination, and you have to use the identifier name of the Element to create the connection. The use of [Alterations](/docs/Alterations) does not affect the connection between the elements; the connection is made transparently.
 
-Connections play a crucial role in managing the flow of data between different elements of the workflow, ensuring the order and integrity of the data. By utilizing Connections, workflows can be designed in a modular fashion, allowing for easy modifications—such as adding or removing components—without disrupting the overall flow.
+Connections play a crucial role in managing the flow of data between different elements of the workflow, ensuring the order and integrity of the data. By utilizing Connections, workflows can be designed in a modular fashion, allowing for easy modifications, such as adding or removing components, without disrupting the overall flow.
 
 ```
   OSCAR:
diff --git a/docpage/docs/Generic.md b/docpage/docs/Generic.md
index 90dd9b43..a4367082 100644
--- a/docpage/docs/Generic.md
+++ b/docpage/docs/Generic.md
@@ -12,7 +12,7 @@ The generic section creates a custom workflow by providing a ProcessGroup file (
 
 DCNiOS creates the specified workflow in Apache NiFi using the .json file, substitutes the environment variables, and uses the same configuration characteristics as other Elements such as Connections and Components. Additionally, make the connections with other Elements. Thus, the declarative .yaml file has the following structure:
 
-- An identifier name of the process. It must be unique. Required.
+- An identifier name of the Element (ProcessGrop in NiFi). It must be unique. Required.
 - The path of your ProcessGroup (.json file).Required.
 - The variables that compose the workflow (as a list).