diff --git a/knowledge base/awx.md b/knowledge base/awx.md
index 6cef6c2..c9f6818 100644
--- a/knowledge base/awx.md
+++ b/knowledge base/awx.md
@@ -9,23 +9,12 @@
## Deployment
-
-Incomplete ARM64 image collection
-
-Consider using only AMD64 nodes to host the containers for AWX.
-
-As of 2024-04-11, AWX does **not** appear to provide ARM64 images for all its containers.
-One'll need to build their own missing ARM64 images and specify those during deployment. Good luck!
-
-
+> ### Incomplete ARM64 image collection
+>
+> Consider using only AMD64 nodes to host the containers for AWX.
+>
+> As of 2024-04-11, AWX does **not** appear to provide ARM64 images for all its containers.
+> One'll need to build their own missing ARM64 images and specify those during deployment. Good luck with that!
Starting from version 18.0, the [AWX Operator][operator's documentation] is the preferred way to install AWX.
It is meant to provide a Kubernetes-native installation method for AWX via an AWX Custom Resource Definition (CRD).
@@ -224,8 +213,10 @@ kubectl delete ns 'awx'
[Guide][basic install]
-
- 1. ARM, Mac OS X, minikube, kustomize: failed: ARM images for AWX not available
+
+
+ 1. ARM, Mac OS X, minikube, kustomize: failed: ARM images for AWX not available
+
```sh
$ minikube start --cpus=4 --memory=6g --addons=ingress
@@ -286,8 +277,7 @@ $ # (ノಠ益ಠ)ノ彡┻━┻
```
-
-
+
2. AMD64, OpenSUSE Leap 15.5, minikube, kustomize
```sh
@@ -362,7 +352,7 @@ $ minikube kubectl -- delete -k '.'
[Guide][helm install on existing cluster]
-
+
1. AMD64, OpenSUSE Leap 15.5, minikube, helm
```sh
@@ -431,7 +421,7 @@ $ minikube kubectl -- delete ns 'awx'
Run: kustomized helm chart
-
+
1. AMD64, OpenSUSE Leap 15.5, minikube