Some corrections

Author: harikrishna-patnala

source/adminguide/extensions.rst

@@ -79,7 +79,7 @@ An Orchestrator extension enables CloudStack to delegate VM orchestration to an
    |extension.png|
 
 
-CloudStack provides in-built Orchestrator Extensions for Proxmox, Hyper-V, MaaS which work with Proxmox, Hyper-V and MaaS environments out of the box.
+CloudStack provides built-in Orchestrator Extensions for Proxmox, Hyper-V, and MaaS, which work with their respective environments out of the box.
 
 .. note::
    - When a CloudStack host linked to an orchestrator extension is placed into Maintenance mode, all running instances on the host will be stopped.

source/adminguide/extensions/inbuilt_extensions.rst

@@ -17,9 +17,9 @@ In-built Orchestrator Extensions
 ================================
 
 CloudStack provides in-built Orchestrator Extensions for Proxmox, Hyper-V and MaaS. These extensions work with Proxmox, Hyper-V and MaaS environments out of the box, and can also serve as reference implementations for anyone looking to develop new custom extensions.
-The Extension files are located at `/usr/share/cloudstack-management/extensions/Proxmox`, `/usr/share/cloudstack-management/extensions/HyperV` and `/usr/share/cloudstack-management/extensions/MaaS` respectively.
+The Extension files are located in `/usr/share/cloudstack-management/extensions/`, under the subdirectories `Proxmox`, `HyperV`, and `MaaS`.
 The Proxmox Extension is written in shell script, while the Hyper-V and MaaS Extensions are written in python.
-All of these Extensions support some custom actions in addition to the standard VM actions like deploy, start, stop, reboot, status and delete.
+Proxmox and Hyper-V Extensions support some custom actions in addition to the standard VM actions like deploy, start, stop, reboot, status and delete.
 After installing or upgrading CloudStack, in-built Extensions will show up in the Extensions section in UI.
 
    |built-in-extensions.png|
@@ -29,7 +29,7 @@ After installing or upgrading CloudStack, in-built Extensions will show up in th
 Proxmox
 ^^^^^^^^
 
-The Proxmox CloudStack Extension is written in shell script and communicates with the Proxmox Cluster using the `Proxmox VE API`_ over HTTPS.
+The Proxmox CloudStack Extension is written in shell script and communicates with the Proxmox Cluster using the `Proxmox VE API <https://pve.proxmox.com/wiki/Proxmox_VE_API>`_ over HTTPS."
 
 Before using the Proxmox Extension, ensure that the Proxmox Datacenter is configured correctly and accessible to CloudStack.
 
@@ -270,7 +270,7 @@ Firewall Rules, Port Forwarding, and other networking features seamlessly throug
 MaaS
 ^^^^^^^^
 
-The MaaS CloudStack Extension is written in python script and communicates with the Canonical MaaS `https://canonical.com/maas`_ using the MaaS APIs `https://canonical.com/maas/docs/api`_.
+The MaaS CloudStack Extension is written in python script and communicates with `Canonical MaaS <https://canonical.com/maas>`_ using the `MaaS APIs <https://canonical.com/maas/docs/api>`_.
 
 Before using the MaaS Extension, ensure that the Canonical MaaS Service is configured correctly with servers added into it and accessible to CloudStack.
 
@@ -279,7 +279,7 @@ Get the API key from MaaS
 
 If not already set up, create a new API Key in the MaaS UI by navigating to left column under `admin > API keys`.
 
-Existing `MAAS consumer` token can used or a new API key can be generated by clicking `Generate MAAS API Key` button
+Existing `MAAS consumer` token can be used or a new API key can be generated by clicking the `Generate MAAS API Key` button
 
    |MaaS-add-token.png|
 
@@ -323,8 +323,7 @@ To set up the MaaS Extension, follow these steps in CloudStack:
 
 #. **Deploy Instance**
 
-   Deploy an Instance using the Template created above. Optionally, provide the detail `vm_name` to specify the name of the VM in MaaS.
-   Otherwise, the CloudStack Instance's internal name is used. The Instance will be provisioned on a randomly selected MaaS machine.
+   Deploy an Instance using the Template created above. The Instance will be provisioned on a randomly selected MaaS machine.
 
    |MaaS-deploy-instance.png|