diff --git a/source/quick_start/operation_basics/provisioning_edge_cluster.rst b/source/quick_start/operation_basics/provisioning_edge_cluster.rst
index 201688242b..29ecf7e874 100644
--- a/source/quick_start/operation_basics/provisioning_edge_cluster.rst
+++ b/source/quick_start/operation_basics/provisioning_edge_cluster.rst
@@ -52,7 +52,7 @@ Step 1: Configure AWS
 
 As a first step, if you don’t already have one, create an account in AWS. AWS publishes a complete guide: `How do I create and activate a new AWS account? <https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/>`__
 
-After you have created your account, you’ll need to obtain the ``access_key`` and ``secret_key`` of a user with the necessary permissions to manage instances. The relevant AWS guide is `Configure tool authentication with AWS <https://docs.aws.amazon.com/powershell/latest/userguide/pstools-appendix-sign-up.html>`__.
+After you have created your account, you’ll need to obtain the ``access_key`` and ``secret_key`` of a user with the necessary permissions to manage instances. The relevant AWS guide is `Configure tool authentication with AWS <https://docs.aws.amazon.com/IAM/latest/UserGuide/access-keys-admin-managed.html>`__.
 
 Next, you need to choose the region where you want to deploy the new resources. You can check the available regions in AWS’s documentation: `Regions, Availability Zones, and Local Zones <https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html>`__.
 
@@ -71,7 +71,7 @@ To log in, point your browser to the OneProvision address:
 
     https://<FRONT-END IP>:2616/fireedge/provision
 
-In the log in screen, enter the credentials for user ``oneadmin``.
+In the log-in screen, enter the credentials for user ``oneadmin``.
 
 Sunstone will display the **OneProvision** screen:
 
@@ -105,7 +105,7 @@ Sunstone displays the **Provider template** screen, showing the **Provision type
 
 |image_provider_create_step1|
 
-Click **Next**. In the next screen you can enter a description for your provider:
+Click **Next**. In the next screen, you can enter a description for your provider:
 
 |image_provider_create_step2|
 
@@ -155,7 +155,7 @@ OneProvision now displays the **Provider** screen showing the available provider
 
 |
 
-In the next screen you can enter a description for your cluster, if desired:
+In the next screen, you can enter a description for your cluster, if desired:
 
 .. image:: /images/fireedge_cpi_provision_create3.png
     :align: center
@@ -212,7 +212,7 @@ To see a running log of the provision, click **Log**:
     
 Provisioning will take a few minutes. When it’s finished, the log will display the message ``Provision successfully created``, followed by the provision’s ID.
 
-At this point the Edge Cluster has been created, and is up and running. In the next step, we’ll verify that all of the specified resources for the provision (the host, datastore, network, and the cluster itself) have been correctly created and registered with OpenNebula.
+At this point, the Edge Cluster has been created and is up and running. In the next step, we’ll verify that all of the specified resources for the provision (the host, datastore, network, and the cluster itself) have been correctly created and registered with OpenNebula.
 
 
 Step 4: Validate the New Infrastructure
diff --git a/source/quick_start/usage_basics/running_kubernetes_clusters.rst b/source/quick_start/usage_basics/running_kubernetes_clusters.rst
index 7ca9187631..c9e5414269 100644
--- a/source/quick_start/usage_basics/running_kubernetes_clusters.rst
+++ b/source/quick_start/usage_basics/running_kubernetes_clusters.rst
@@ -559,4 +559,15 @@ In this case you can manually instruct the VMs to report ``READY`` to the OneGat
           3 oneadmin oneadmin OneKE 1.29                                                         08/30 12:35:21 RUNNING
 
 
+One or more VMs is Ready, but unreachable
+++++++++++++++++++++++++++++++++++++++
+
+In a similar situation as above when `onevm list`` shows all VMs running, but the service is still in ``DEPLOYING`` state, but the VM is not reachable through SSH (e.g. to run the ``onegate vm update`` command).
 
+In this case, we can try to scale down and up the role of the problematic VM from the Front-end UI:
+   #. Go to Services in the Front-end UI and select the OneKE Service
+   #. In the Roles tab choose the problematic VM's role (e.g. worker)
+   #. Scale the role to 0
+   #. Wait until shutdown of the VM, the scaling and cooldown period of the service finishes
+   #. Scale the role to 1
+   #. Verify if the problem is solved and the ``oneflow list`` reports the ``RUNNING`` state