fix: review changes

Author: Bemilie

serverless/containers/reference-content/containers-limitations.mdx

@@ -95,3 +95,11 @@ incoming requests for up to 24 hours. After this period, the container in error
 longer be served until a successful deployment is made. This ensures temporary service continuity, but it is important
 to monitor and resolve deployment issues promptly, as the fallback is not intended to provide long-term version control
 or rollback capabilities.
+
+Below is an example than illustrates this behavior:
+
+* Time +0H: The first container is deployed and works correctly.
+* Time +1H: The container is redeployed, but the deployment fails, and the container ends up in an error state.
+* Time +2H: Despite the failed deployment, the first container is still handling incoming requests.
+* Time +25H: The 24-hour window expires, and both the first working container and the failed container are removed,
+leading to service disruption until a new successful deployment is made.

serverless/functions/reference-content/functions-limitations.mdx

@@ -64,3 +64,11 @@ incoming requests for up to 24 hours. After this period, the function in error w
 longer be served until a successful deployment is made. This ensures temporary service continuity, but it is important
 to monitor and resolve deployment issues promptly, as the fallback is not intended to provide long-term version control
 or rollback capabilities.
+
+Below is an example than illustrates this behavior:
+
+* Time +0H: The first function is deployed and works correctly.
+* Time +1H: The function is redeployed, but the deployment fails, and the function ends up in an error state.
+* Time +2H: Despite the failed deployment, the first function is still handling incoming requests.
+* Time +25H: The 24-hour window expires, and both the first working function and the failed function are removed,
+leading to service disruption until a new successful deployment is made.