Incorporated Jordan's comment

Author: pabel-rh

modules/developer-lightspeed/proc-changing-your-llm-provider.adoc

@@ -28,27 +28,17 @@ lightspeed:
       url: _<my_new_url>_
       token: _<my_new_token>_
 ----
-** Alternatively, you can set the `id`, `url`, and `token` values in a Kubernetes Secret and reference them using environment variables in your application configuration as shown in the following code:
-+
+** You can set the `id`, `url`, and `token` values in a Kubernetes Secret if you want and reference them as environment variables using the `envFrom` section.
 [source,yaml]
 ----
-env:
-  - name: _<my_new_url>_
-    valueFrom:
-      secretKeyRef:
-        name: my-secret
-        key: _<my_new_url>_
-  - name: _<my_new_provider>_
-    valueFrom:
-      secretKeyRef:
-        name: my-secret
-        key: _<my_new_provider>_
-  - name: _<my_new_token>_
-    valueFrom:
-      secretKeyRef:
-        name: my-secret
-        key: _<my_new_token>_
+containers:
+    - name: my-container
+      image: my-image
+      envFrom:
+        - secretRef:
+            name: my-secret
 ----
+
 * You can add new LLM providers by updating the `rcsconfig.yaml` file.
 .. In the `llm_providers` section within your `rcsconfig.yaml` file, add your new provider configuration below the mandatory dummy provider block as shown in the following code:
 +