removes "tmpfs is cleared on node reboot"

I believe the statement is confusing since we are in the emptyDir section of the documentation.  

If a Node is restarted then all pods that resided on that node will be rescheduled onto another Node.  Rescheduled pods will have an empty volume  whether you choose emptyDir.medium "Memory" or not.

content/en/docs/concepts/storage/volumes.md

@@ -244,9 +244,8 @@ The `emptyDir.medium` field controls where `emptyDir` volumes are stored. By
 default `emptyDir` volumes are stored on whatever medium that backs the node
 such as disk, SSD, or network storage, depending on your environment. If you set
 the `emptyDir.medium` field to `"Memory"`, Kubernetes mounts a tmpfs (RAM-backed
-filesystem) for you instead.  While tmpfs is very fast, be aware that unlike
-disks, tmpfs is cleared on node reboot and any files you write count against
-your container's memory limit.
+filesystem) for you instead.  While tmpfs is very fast, be aware that, unlike
+disks, files you write count against your container's memory limit.
 
 
 A size limit can be specified for the default medium, which limits the capacity