fix AmoniK spelling

AEP/aep-00005.md

@@ -23,21 +23,21 @@ Updating or proposing alternative solutions for various components within the cu
 
 # Specifications
 
-First, we define the input variables that are expected from Armonik. These variables are essentially the outputs that are generated by the modules. We commonly refer to these variables as environment variables. Kubernetes defines three different approaches to populate these variables: using environment variable methods, configmaps, secrets, and volume mounts.
+First, we define the input variables that are expected from ArmoniK. These variables are essentially the outputs that are generated by the modules. We commonly refer to these variables as environment variables. Kubernetes defines three different approaches to populate these variables: using environment variable methods, configmaps, secrets, and volume mounts.
 
 ## Approach
 
-Our approach is to have an infrastructure built on a modular basis.  We will first define all the modules Armonik needs.
+Our approach is to have an infrastructure built on a modular basis.  We will first define all the modules ArmoniK needs.
 
-We classify these modules into two categories: internal and external components. The internal components are a part of Armonik such as the compute plane, while the external components like MongoDB database are required for Armonik to function.
+We classify these modules into two categories: internal and external components. The internal components are a part of ArmoniK such as the compute plane, while the external components like MongoDB database are required for ArmoniK to function.
 
 The internal components modules depend on external components either to function or to be created.
 
 Modules outputs ---> ArmoniK
 
 ```mermaid
     graph LR
-    A[External module 1] -- outputs --> B(Armonik)
+    A[External module 1] -- outputs --> B(ArmoniK)
     C[External module ...] -- outputs --> B
     D[External module n] -- outputs --> B