docs(orchestrator) fix architecture issue, billing app can't be scalable

subjects/devops/orchestrator/README.md

@@ -83,23 +83,22 @@ You must store your passwords and credentials as a K8s secrets.
 
 ### Node.js apps
 
-Your Node.js applications must be deployed as a deployment and they must be scaled horizontally automatically, depending on CPU consumption.
+This Node.js applications must be deployed as a deployment and they must be scaled horizontally automatically, depending on CPU consumption.
 
 - `api-gateway`:
   max replication: 3
   min replication: 1
   cpu percent trigger: 60%
 
-- `billing-app`:
-  max replication: 3
-  min replication: 1
-  cpu percent trigger: 60%
-
 - `inventory-app`:
   max replication: 3
   min replication: 1
   cpu percent trigger: 60%
 
+This Node.js application must be deployed as StatefulSet:
+
+- `billing-app`
+
 ### Databases
 
 Your databases must be deployed as StatefulSet in your K3s cluster, and you must create volumes that enable containers to move across infrastructure without losing the data.

subjects/devops/orchestrator/audit/README.md

@@ -136,15 +136,14 @@ user:~$
    min replication: 1
    cpu percent trigger: 60%
 
-2. `billing-app`:
+2. `inventory-app`:
    max replication: 3
    min replication: 1
    cpu percent trigger: 60%
 
-3. `inventory-app`:
+This Node.js application must be deployed as StatefulSet:
-   max replication: 3
+
-   min replication: 1
+1. `billing-app`
-   cpu percent trigger: 60%
 
 ###### Do all apps deploy with the correct configuration?