Better explain checking the lifetime

Author: sbernauer

modules/concepts/pages/operations/temporary_credentials_lifetime.adoc

@@ -69,9 +69,12 @@ Similar to the example above, users can configure the lifetime of temporary cred
 
 == Check the lifetime
 
-Pods are normally not restarted "randomly" by Stackable operators.
-Instead, when a temporary credential is added to a Pod, an annotation is added as well.
-It starts with `restarter.stackable.tech/expires-at.` and instructs the xref:commons-operator:index.adoc[commons-operator] to restart the Pod once the specified instant is reached.
+After configuring the lifetime as described above you could simply observe your stacklet for a week/month (or whatever your new lifetime is), to see if your changes take effect.
+However, it's much quicker to check at what point of time your Pods will be restarted next.
+
+Pods are not restarted "randomly" by Stackable operators, but in a predicable manner.
+When a temporary credential is added to a Pod, an annotation is added as well.
+It starts with `restarter.stackable.tech/expires-at.` and instructs the xref:commons-operator/restarter.adoc[restart-controller] to restart the Pod once the specified point in time is reached.
 
 Given the following Pod
 
@@ -84,5 +87,6 @@ metadata:
     restarter.stackable.tech/expires-at.ea77192c1184326d33e8ee32cfe921ea: "2024-12-05T15:49:10.043722965+00:00"
 ----
 
-You can always determine the timestamp the Pod will be restarted by the xref:commons-operator:index.adoc[commons-operator] by taking the earliest timestamp, `2024-12-05T14:03:47.131570189+00:00` in this case.
-This way you can verify that the changes you made to the temporary credentials lifetime take effect.
+You can always determine the instant the Pod will be restarted by the xref:commons-operator/restarter.adoc[restart-controller] by taking the earliest timestamp, `2024-12-05T14:03:47.131570189+00:00` in this case.
+
+You can use this timestamp to check if your changes have been applied as intended.