From 2aba9bd33369256e4be6998a738bb570d2db8084 Mon Sep 17 00:00:00 2001
From: Vinodh N <45449393+globervinodhn@users.noreply.github.com>
Date: Sun, 17 Feb 2019 21:03:51 +0530
Subject: [PATCH] Update container-lifecycle-hooks for preStop - removed
 submodule website (#12498)

The changes are in line with one of the request for documentation update as per PR #55807 wherein it was observed that the preStop hook is not commissioned when the container is already in the terminated or completed state.

Braces removed as per the review comment. Multiple commits squashed

Braces removed as per the review comment

Update as per review, removed etc... and the statement is now cleaner
---
 .../en/docs/concepts/containers/container-lifecycle-hooks.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/containers/container-lifecycle-hooks.md b/content/en/docs/concepts/containers/container-lifecycle-hooks.md
index 3825868850..08d855732f 100644
--- a/content/en/docs/concepts/containers/container-lifecycle-hooks.md
+++ b/content/en/docs/concepts/containers/container-lifecycle-hooks.md
@@ -36,7 +36,7 @@ No parameters are passed to the handler.
 
 `PreStop`
 
-This hook is called immediately before a container is terminated.
+This hook is called immediately before a container is terminated due to an API request or management event such as liveness probe failure, preemption, resource contention and others. A call to the preStop hook fails if the container is already in terminated or completed state.
 It is blocking, meaning it is synchronous,
 so it must complete before the call to delete the container can be sent.
 No parameters are passed to the handler.