add more detail to doc

Author: pfmackin

docs-source/content/userguide/managing-domains/domain-lifecycle/restarting.md

@@ -202,7 +202,11 @@ If you've created a new image that is not rolling compatible, and you've changed
 
 * **Managed Coherence Server safe shutdown**.
 
-    If the domain is configued to use Coherence Clusters, then the Operator will automatically wait until the Coherence HAStatus MBean attribute
-    indicates that it is safe to shutdown the server.  If, for some reason, the Operator is not able to access the Coherence MBean then the server
-    will not be shutdown until the domain timeoutSeconds expires.  To minimize any possibility of cache data loss, you should increase
-    the timeoutSeconds value to a large number, for example: 15 minutes.
+    If the domain is configured to use Coherence Clusters, then you will need to increase the Kubernetes graceful timeout value.  
+    When a server is shutdown, Coherence needs time to recover partitions and rebalance the cluster before it is safe to shutdown a second server.
+    Using the Kubernetes graceful termination feature, the Operator will automatically wait until the Coherence HAStatus MBean attribute 
+    indicates that it is safe to shutdown the server.  However, once graceful termination timeout expires, the pod will be deleted regardless. 
+    Therefore, it is important to set the domain yaml timeoutSeconds to a large enough value to prevent the server from shutting down before 
+    Coherence is safe. Furthermore, if the Operator is not able to access the Coherence MBean then the server will not be shutdown 
+    until the domain timeoutSeconds expires.  To minimize any possibility of cache data loss, you should increase the timeoutSeconds 
+    value to a large number, for example: 15 minutes.