fix: Refresh shoot hibernation How-To guide

In light of the new Kubernetes versions we now support
for shoot clusters, we refresh all screenshots and
update the prose.

docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md

@@ -5,7 +5,7 @@ description: How to hibernate a Gardener-based Kubernetes cluster
 
 There will be times when you won't be using your {{k8s_management_service}}-based cluster much, if at all.
 To save on costs, you can put the whole cluster in hibernation.
-If you do, then from that time on (and until you wake the cluster again), you will be paying *less* for the cluster.
+If you do, then from that time on and until you wake up the cluster again, you will be paying *less* for it.
 
 ## Prerequisites
 
@@ -16,14 +16,14 @@ If you've never done this before, please feel free to [follow this guide](create
 
 Fire up your favorite web browser and navigate to <https://{{gui_domain}}>.
 Make sure the vertical pane at the left-hand side of the page is in full view, then choose *Containers → [{{k8s_management_service}}](https://{{gui_domain}}/containers/gardener)*.
-In the main pane, you will see your {{k8s_management_service}} cluster.
-Click anywhere on its row for a detailed view of the various cluster characteristics.
+You will see your {{k8s_management_service}} cluster in the main pane.
+Click on its row for a detailed view of the various cluster characteristics.
 Bring up the *Status* tab and, in the *Constraints* section, check whether hibernation is possible.
-In the example below we have a shoot cluster based on Kubernetes 1.29, the latest supported at the time of this writing, and hibernation is indeed possible.
+For the shoot cluster in the example below, it is indeed possible.
 
 ![{{k8s_management_service}} cluster status](assets/shoot-hiber-01.png)
 
-To go ahead and actually hibernate the cluster, click the orange :material-dots-horizontal-circle: icon at the right-hand side of the cluster row.
+To hibernate the cluster, click the orange :material-dots-horizontal-circle: icon at the right-hand side of the cluster row.
 From the pop-up menu that appears, select *Hibernate Cluster*.
 
 ![Hibernate cluster](assets/shoot-hiber-02.png)
@@ -43,28 +43,28 @@ This fact will be indicated by the red :material-stop-circle: icon, again at the
 
 ![Cluster in hibernation](assets/shoot-hiber-05.png)
 
-From this point on, and as long as the cluster is in hibernation, any attempt to list the cluster nodes, e.g., via `kubectl`, will fail.
+From this point on, and as long as the cluster is in hibernation, any attempt to access it, e.g., via `kubectl`, will fail.
 
 ## Waking up a cluster in hibernation
 
 To wake up a cluster in hibernation, click the orange :material-dots-horizontal-circle: icon at the right-hand side of its row.
 From the pop-up menu that appears, select *Wake up Cluster*.
 
-![Wake up cluster](assets/shoot-hiber-06.png)
+![Wake up cluster](assets/shoot-wakeup-01.png)
 
-A big pop-up window labeled *About to wakeup a gardener shoot* appears, asking you to confirm that you want to wake the cluster.
+A big pop-up window labeled *About to wakeup a gardener shoot* appears, asking you to confirm that you want to wake up the cluster.
 Go ahead and click the red *Yes, Wakeup* button.
 
-![Confirm cluster wake-up](assets/shoot-hiber-07.png)
+![Confirm cluster wake-up](assets/shoot-wakeup-02.png)
 
 The cluster will start waking up.
 Again, the animated icon at the left-hand side of the cluster row marks the progress.
 
-![Cluster is awaking](assets/shoot-hiber-08.png)
+![Cluster is awaking](assets/shoot-wakeup-03.png)
 
 After a couple of minutes, the cluster will be fully awake.
-The fact will be indicated by the green :material-check-circle: icon, at the left-hand side of the cluster row.
+The fact will be indicated by the green :material-check-circle: icon at the left-hand side of the cluster row.
 
-![Cluster awake](assets/shoot-hiber-09.png)
+![Cluster awake](assets/shoot-wakeup-04.png)
 
-From that time on, the cluster will be fully operational and accessible again.
+From then on, the cluster will be fully operational and accessible again.