Explain root cause and resolution of issue

.wordlist.txt

@@ -179,7 +179,6 @@ sharding
 src
 ssz
 stakers
-stateful
 subnet
 subnets
 tcp

docs/pages/faqs.md

@@ -1,18 +1,21 @@
 # Frequently Asked Questions
+
 This section of the documentation will cover common questions and encounters often asked by users and developers.
 
 ## Troubleshooting Lodestar
 
 ### Using Kubernetes
 <!-- prettier-ignore-start -->
 ???+ note "Unknown arguments error on Kubernetes"
-    Lodestar does not handle environment variables well when prefixed with `LODESTAR` by default. You may encounter issues such as:
+    Lodestar reads all environment variables prefixed with `LODESTAR` and will try to parse
+    them similar to command line arguments, meaning any unknown argument will cause an error.
     ```
-    ✖ Unknown arguments: datadir, servicePort, servicePortEthConsensusP2p, 
+    ✖ Unknown arguments: servicePort, servicePortEthConsensusP2p,
     port9000Tcp, port9000TcpPort, port9000TcpProto, port9000TcpAddr, serviceHost
     ```
-    The stateful set and other predefined environment variables should not use `LODESTAR`, which will break the deployment.
+    The additional arguments are present because Kubernetes automatically creates environment
+    variables based on the name (`metadata.name`) defined in the `StatefulSet` or `Deployment`.
+    To resolve the issue, this name has to be changed to something that does not begin with `lodestar`.
 
-    Reference Issue:
-    [https://github.com/ChainSafe/lodestar/issues/6045](https://github.com/ChainSafe/lodestar/issues/6045)
-<!-- prettier-ignore-end -->
+    Reference Issue: [#6045](https://github.com/ChainSafe/lodestar/issues/6045)
+<!-- prettier-ignore-end -->