From 7e16543b9dbe6771017730199b62e2b99c18803e Mon Sep 17 00:00:00 2001
From: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com>
Date: Thu, 21 Jul 2022 08:58:21 +0100
Subject: [PATCH] Update configure-pod-configmap.md

---
 .../configure-pod-container/configure-pod-configmap.md   | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md b/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
index 11959ff8f2..b6679980ad 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
@@ -678,8 +678,8 @@ data:
 ### Optional ConfigMaps
 
 In a Pod, or pod template, you can mark a reference to a ConfigMap as _optional_.
-If the ConfigMap is non-existent, the mounted volume will be empty.
-If the ConfigMap exists, but the referenced key is non-existent the path will be absent beneath the mount point.
+If the ConfigMap is non-existent, the configuration for which it provides data in the Pod (e.g. environment variable, mounted volume) will be empty.
+If the ConfigMap exists, but the referenced key is non-existent the data is also empty.
 
 #### Optional ConfigMap in environment variables
 
@@ -739,10 +739,7 @@ spec:
   restartPolicy: Never
 ```
 
-If you run this pod, and there is no ConfigMap named `no-config`, the output is:
-
-```shell
-```
+If you run this pod, and there is no ConfigMap named `no-config`, the mounted volume will be empty.
 
 ### Mounted ConfigMaps are updated automatically