M #-: Review Operating Edge Cluster for style

Signed-off-by: Pedro Ielpi <[email protected]>

source/quick_start/operation_basics/operating_edge_cluster.rst

@@ -4,7 +4,13 @@
 Operating an Edge Cluster
 =========================
 
-In this guide you will see all the resources created in OpenNebula as a part of the Edge Cluster. These resources have all been created using the OneProvision GUI in AWS.
+In :ref:`Provisioning an Edge Cluster <first_edge_cluster>`, we used the OneProvision GUI to create an Edge Cluster in AWS.
+
+This page provides an overview of all resources created in OpenNebula during that deployment, which together comprise the Edge Cluster.
+
+All resources in the Edge Cluster are created from templates. Templates contain all of the information for the physical features of resources. For some templates, such as the network templates, users need to provide the logical attributes at the moment of instantiating the template, such as the IP or the address range.
+
+Below you will find brief descriptions for the resources that comprise the Edge Cluster, with examples of their visual representation in the Sunstone UI and links to complete references for each resource.
 
 Cluster
 ================================================================================
@@ -13,52 +19,52 @@ A cluster is the main object that groups all the physical resources and ensures
 
 |image_cluster|
 
-Check :ref:`this link <cluster_guide>` to get a full understanding of cluster management.
+For a complete overview of Cluster management, see :ref:`Clusters <cluster_guide>`.
 
 Hosts
 ================================================================================
 
-A Host is mainly anything that is able to run a VM, container or Micro VM. It is in charge of executing them and retrieves all of the monitoring information. A Host has two important attributes:
+A Host is any entity that is capable of running a VM or a container. Besides running them, it retrieves all monitoring information. A Host has two important attributes:
 
-* ``VM_MAD``: this indicates the virtualization technology that is going to be used.
-* ``IM_MAD``: this driver retrieves all the monitoring metrics from the host.
+* ``VM_MAD``: the virtualization technology used on the Host.
+* ``IM_MAD``: the driver that retrieves all monitoring metrics from the Host.
 
-The following screenshot shows the information about the Host. The important information here is:
+The screenshot below displays the information about the Host. The important information here is:
 
-* The **state** of the Host: as you can see it's in **MONITORED** state, meaning the Host is correctly being monitored.
-* The monitor metrics that can be found in the attributes list.
-* Extra information, such as the VMs running on it.
+* The **State** of the Host: **MONITORED** indicates that the Host is currently being monitored.
+* The **Attributes** section displays the monitoring metrics.
+* The tabs to the right of the **Info** tab display additional information, such as the VMs running on the Host.
 
 |image_host|
 
-The basic operations you can perform with the Host are:
+The basic operations you can perform on the Host are:
 
 * **Offline**: take the Host totally offline.
-* **Disable**: disable it, e.g., to perform maintenance operations.
-* **Enable**: enable it, so OpenNebula monitors it and it switches back to MONITORED state.
+* **Disable**: disable the Host, for example to perform maintenance operations.
+* **Enable**: enable the Host, so that OpenNebula monitors it and it switches back to MONITORED state.
 
-Check :ref:`this link <hosts>` to get a complete understanding of Host management.
+For a complete overview of Hosts management, see :ref:`Hists <hosts>`.
 
 Datastores
 ================================================================================
 
 There are two types of datastores:
 
-* **System**: this datastore contains the information of running VMs, such as disks or context CD-ROM.
-* **Image**: this datastore stores the images in your cloud.
+* **System**: contains the information of running VMs, such as disks or context CD-ROM.
+* **Image**: stores the images in your cloud.
 
-Each Edge Cluster contains two datastores, one system and one image. Both of them use the SSH replica driver to decrease VMs' deployment time using the cached images.
+Each Edge Cluster contains two datastores: one system and one image. Both of them use the SSH replica driver to decrease VMs’ deployment time using the images cached on the datastores.
 
 |image_datastore|
 
-Check :ref:`this link <datastores>` to get a sound overview of datastore management.
+For a complete overview of Datastore management, see :ref:`Datastores <datastores>`.
 
 .. _edge_public:
 
 Virtual Networks: Public
 ================================================================================
 
-A virtual network in OpenNebula basically resembles the physical network in the datacenter. Virtual Networks allow VMs to have connectivity between them and with the rest of the world. Each Edge Cluster has one public network with the number of the IPs chosen by the user (in Sunstone); this will allow VMs to have public connectivity so the user can connect to them.
+A virtual network in OpenNebula basically resembles the physical network in the data center. Virtual Networks allow VMs to have connectivity between them and with the rest of the world. Each Edge Cluster has one public network with the number of the IPs selected by the user in Sunstone. This allows VMs to have public connectivity so the user can connect to them.
 
 |image_public_net|
 
@@ -67,19 +73,13 @@ A virtual network in OpenNebula basically resembles the physical network in the
 Virtual Networks: Private
 ================================================================================
 
-A virtual network template contains all the physical information about the network as defined by the administrator. Users need to provide only the logical attributes when instantiating it, like the IP or the number of address ranges.
+As with the public network, a private network needs user input before instantiation, such as the IP or number of address ranges.
 
-The network uses driver VLXAN - BGP EVPN:
+The network uses driver VXLAN - BGP EVPN:
 
 |image_private_net|
 
-In order to instantiate it, you need to follow these steps:
-
-* Click on the virtual network template.
-* Click on the ``instantiate`` button.
-* Click on the ``+ address range`` to add all the address ranges you need.
-
-Check :ref:`this link <vn_templates>` to get a complete picture of virtual network templates management.
+For a complete overview, see :ref:`Virtual Network Templates <vn_templates>`.
 
 .. |image_cluster| image:: /images/edge_cluster.png
 .. |image_host| image:: /images/edge_host.png