fix(rst-files): fixed spelling mistakes

Author: r-annie

source/adminguide/accounts.rst

@@ -676,7 +676,7 @@ For GitHub, please follow the instructions mentioned here `"Setting up OAuth 2.0
 In any OAuth 2.0 configuration admin has to use the redirect URI "http://<management server IP>:<port>/#/verifyOauth"
 
 .. Note:: [Google OAuth 2.0 redirect URI] :
-          Google OAuth 2.0 configuration wont accept '#' in the URI, please use "http://<management server Domain>:<port>/?verifyOauth"
+          Google OAuth 2.0 configuration won't accept '#' in the URI, please use "http://<management server Domain>:<port>/?verifyOauth"
           Google does not accept direct IP address in the redirect URI, it must be a domain. As a workaround one can add the management
           server IP to host table in the local system and assign a domain, something like "management.cloud". In that redirect URI looks like
           "http://management.cloud:8080/?verifyOauth"

source/adminguide/backup_and_recovery.rst

@@ -92,7 +92,7 @@ Backup Offerings
 ------------------
 
 Admins can import an external provider's backup offerings using UI or API for a
-particular zone, as well as manage a backup offering's lifecyle. Admins can also
+particular zone, as well as manage a backup offering's lifecycle. Admins can also
 specify if a backup offering allows user-defined backup schedules and ad-hoc
 backups. Users can list and consume the imported backup offerings, only root admins can import or
 delete offerings.

source/adminguide/events/webhooks.rst

@@ -80,8 +80,8 @@ To create a webhook:
    -  **Payload URL**. The payload URL of the Webhook. All events for the
       webhook will posted on this URL.
 
-   -  **SSL Verification**. An otional parameter to specify whether the HTTP
-      POST requests for event notications must be sent with strict SSL
+   -  **SSL Verification**. An optional parameter to specify whether the HTTP
+      POST requests for event notifications must be sent with strict SSL
       verification request when a HTTPS payload URL is used.
 
    -  **Secret Key**. An option secret key parameter which can be used to sign
@@ -123,7 +123,7 @@ configurations:
 
 
 CloudStack allows retrieving recent deliveries for a webhook with details such
-as event, headers, payload, respose, success, duration, etc.
+as event, headers, payload, response, success, duration, etc.
 In the UI, these can be accessed under Recent deliveries tab in the Webhook
 detail view.
 The user can redeliver an existing delivery. To check the working of the
@@ -155,7 +155,7 @@ as the payload. The following custom headers are sent with the request:
    -  **X-CS-Event**. Event for for which the webhook delivery is made.
 
    -  **User-Agent**. In the format - *CS-Hookshot/<ACCOUNT_ID>*. Here
-      ACCOUNT_ID is the ID of the account which trigerred the event.
+      ACCOUNT_ID is the ID of the account which triggered the event.
 
    -  **X-CS-Signature**. HMAC SHA256 signature created using the webhook
       secret key and the delivery payload. It is sent only when secret key
@@ -171,7 +171,7 @@ Working with HTTPS webhook payload URL with self-signed certificate
 
       openssl req -x509 -newkey rsa:4096 -nodes -out cert.pem -keyout key.pem -days 365
 
-#. Copy the genereated cert.pem to the management server(s).
+#. Copy the generated cert.pem to the management server(s).
 
 #. Import the certificate for JDK on the management server(s)
 

source/adminguide/host_and_storage_tags.rst

@@ -154,7 +154,7 @@ In Apache CloudStack 4.19 and prior, cloud operators are only able to set tags o
 
 Implicit host tags feature is supported since Apache CloudStack 4.20. With the feature, Cloud operators can easily set the
 implicit host tags per host based on the server configurations. For example, based on the following hardware devices and
-softwares which can be fetched by commands, scripts or tools:
+software which can be fetched by commands, scripts or tools:
 
 - CPU architecture and model
 - Network card type and speed

source/adminguide/hosts.rst

@@ -164,7 +164,7 @@ migrated to other Hosts. To remove a Host from the cloud:
 
 #. Use the UI option to remove the node.
 
-   Then you may power down the Host, re-use its IP address, re-install
+   Then you may power down the Host, reuse its IP address, re-install
    it, etc
 
 
@@ -472,7 +472,7 @@ To change the over-provisioning factors for an existing cluster:
 
 #. Fill in your desired over-provisioning multipliers in the fields CPU
    overcommit factor and RAM overcommit factor. The value which is
-   intially shown in these fields is the default value inherited from
+   initially shown in these fields is the default value inherited from
    the global configuration settings.
 
    .. note::
@@ -595,7 +595,7 @@ The former behaviour also is supported — VLAN is randomly allocated to a
 network from the VNET range of the physical network when the network
 turns to Implemented state. The VLAN is released back to the VNET pool
 when the network shuts down as a part of the Network Garbage Collection.
-The VLAN can be re-used either by the same network when it is
+The VLAN can be reused either by the same network when it is
 implemented again, or by any other network. On each subsequent
 implementation of a network, a new VLAN can be assigned.
 
@@ -676,7 +676,7 @@ management server(s).
 The ``outofbandmanagement.sync.poolsize`` is the maximum number of ipmitool
 background power state scanners that can run at a time. Based on the maximum
 number of hosts you've, you can increase/decrease the value depending on how much
-stress your management server host can endure. It will take atmost number of
+stress your management server host can endure. It will take at most number of
 total out-of-band-management enabled hosts in a round *
 ``outofbandmanagement.action.timeout`` / ``outofbandmanagement.sync.poolsize`` seconds
 to complete a background power-state sync scan in a single round.
@@ -703,7 +703,7 @@ power management actions but in the UI a warning is displayed.
 Security
 --------
 
-Starting 4.11, CloudStack has an inbuilt certicate authority (CA) framework and
+Starting 4.11, CloudStack has an inbuilt certificate authority (CA) framework and
 a default 'root' CA provider which acts as a self-signed CA. The CA framework
 participates in certificate issuance, renewal, revocation, and propagation of
 certificates during setup of a host. This framework is primary used to

source/adminguide/locale/pot/hosts.pot

@@ -262,7 +262,7 @@ msgstr ""
 
 #: ../../hosts.rst:171
 # 400a182ceace4cef87ffe6c731ea45cd
-msgid "Then you may power down the Host, re-use its IP address, re-install it, etc"
+msgid "Then you may power down the Host, reuse its IP address, re-install it, etc"
 msgstr ""
 
 #: ../../hosts.rst:176
@@ -545,7 +545,7 @@ msgstr ""
 
 #: ../../hosts.rst:410
 # 4574765089c64df0a53ffd4b0d9052a0
-msgid "Fill in your desired over-provisioning multipliers in the fields CPU overcommit factor and RAM overcommit factor. The value which is intially shown in these fields is the default value inherited from the global configuration settings."
+msgid "Fill in your desired over-provisioning multipliers in the fields CPU overcommit factor and RAM overcommit factor. The value which is initially shown in these fields is the default value inherited from the global configuration settings."
 msgstr ""
 
 #: ../../hosts.rst:421
@@ -772,7 +772,7 @@ msgstr ""
 
 #: ../../hosts.rst:530
 # 47af367fd0e74e9c98c07d5fd93d9a6a
-msgid "The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be re-used either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned."
+msgid "The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be reused either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned."
 msgstr ""
 
 #: ../../hosts.rst:538

source/adminguide/locale/pot/management.pot

@@ -298,7 +298,7 @@ msgstr ""
 
 #: ../../management.rst:345
 # 653fb8fc18ea4f17ab01fe630ed6783b
-msgid "CloudStack generates a syslog message for every alert. Each syslog message incudes the fields alertType, message, podId, dataCenterId, and clusterId, in the following format. If any field does not have a valid value, it will not be included."
+msgid "CloudStack generates a syslog message for every alert. Each syslog message includes the fields alertType, message, podId, dataCenterId, and clusterId, in the following format. If any field does not have a valid value, it will not be included."
 msgstr ""
 
 #: ../../management.rst:354

source/adminguide/locale/pot/networking/inter_vlan_routing.pot

@@ -38,7 +38,7 @@ msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:37
 # dca4c4be393c4d7bbcda75f49ffc8efc
-msgid "The administrator can deploy a set of VLANs and allow users to deploy VMs on these VLANs. A guest VLAN is randomly alloted to an account from a pre-specified set of guest VLANs. All the VMs of a certain tier of an account reside on the guest VLAN allotted to that account."
+msgid "The administrator can deploy a set of VLANs and allow users to deploy VMs on these VLANs. A guest VLAN is randomly allotted to an account from a pre-specified set of guest VLANs. All the VMs of a certain tier of an account reside on the guest VLAN allotted to that account."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:43

source/adminguide/locale/pot/networking/ip_reservation_in_guest_networks.pot

@@ -68,7 +68,7 @@ msgstr ""
 
 #: ../../networking/ip_reservation_in_guest_networks.rst:60
 # 0710411bb18c4764970dffcc49fe5dab
-msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgid "You cannot apply IP Reservation if any VM is allotted with an IP address that is outside the Guest VM CIDR."
 msgstr ""
 
 #: ../../networking/ip_reservation_in_guest_networks.rst:63

source/adminguide/locale/pot/networking/virtual_private_cloud_config.pot

@@ -1547,7 +1547,7 @@ msgstr ""
 #: ../../networking/virtual_private_cloud_config.rst:1165
 # 2e6d402ef3d044488597c6501ca6749d
 # f974a014675745ceae4ebb19113bc49e
-msgid "Naviagte to Service Offerings and choose Network OfferingPublic IP Addresses."
+msgid "Navigate to Service Offerings and choose Network OfferingPublic IP Addresses."
 msgstr ""
 
 #: ../../networking/virtual_private_cloud_config.rst:961