Skip to content

Commit 2d45ef7

Browse files
jbamptonjbampton
authored
docs: fix spelling (#512)
1 parent b175c2c commit 2d45ef7

File tree

13 files changed

+20
-20
lines changed

13 files changed

+20
-20
lines changed

‎source/adminguide/accounts.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -904,8 +904,8 @@ password for a user:
904904
Using API Key and Secret Key based Authentication
905905
-------------------------------------------------
906906
Users can generate API key and Secret key to directly access CloudStack APIs.
907-
This authenctication method is used for programatically calling CloudStack APIs and thus helps in automation.
908-
The API key uniquely identifies the Account, while the Secret key is used to generate a secure singnature.
907+
This authentication method is used for programmatically calling CloudStack APIs and thus helps in automation.
908+
The API key uniquely identifies the Account, while the Secret key is used to generate a secure signature.
909909
When making an API call, the API key and signature are included along with the command and other parameters,
910910
and sent to the CloudStack API endpoint. For detailed information, refer to the CloudStack's Programmer Guide.
911911

‎source/adminguide/events/webhooks.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This allows users to consume event notifications without any external services
2121
such as an event streaming platforms.
2222

2323
Webhooks can be managed using both API and UI. CloudStack provides following
24-
APIs for webhhoks:
24+
APIs for webhooks:
2525

2626
.. cssclass:: table-striped table-bordered table-hover
2727

@@ -37,7 +37,7 @@ APIs for webhhoks:
3737
executeWebhookDelivery Executes a Webhook delivery
3838
====================== ===========================
3939

40-
In the UI, webhooks can be managed under *Tools > Webhhooks* menu.
40+
In the UI, webhooks can be managed under *Tools > Webhooks* menu.
4141

4242
|webhooks.png|
4343

‎source/adminguide/hosts.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -924,7 +924,7 @@ There are four stages in the KVM rolling maintenance process:
924924

925925
#. Pre-Flight stage: Pre-flight script (``PreFlight`` or ``PreFlight.sh`` or ``PreFlight.py``) runs on hosts before commencing the rolling maintenance. If pre-flight check scripts return an error from any host, then rolling maintenance will be cancelled with no actions taken, and an error returned. If there are no pre-flight scripts defined, then no checks will be done from the hosts.
926926

927-
#. Pre-Maintenace stage: Pre-maintenance script ((``PreMaintenance`` or ``PreMaintenance.sh`` or ``PreMaintenance.py``)) runs before a specific host is put into maintenance. If no pre-maintenance script is defined, then no pre-maintenance actions will be taken, and the management server will move straight to putting the host in maintenance followed by requesting that the agent runs the maintenance script.
927+
#. Pre-Maintenance stage: Pre-maintenance script ((``PreMaintenance`` or ``PreMaintenance.sh`` or ``PreMaintenance.py``)) runs before a specific host is put into maintenance. If no pre-maintenance script is defined, then no pre-maintenance actions will be taken, and the management server will move straight to putting the host in maintenance followed by requesting that the agent runs the maintenance script.
928928

929929
#. Maintenance stage: Maintenance script ((``Maintenance`` or ``Maintenance.sh`` or ``Maintenance.py``)) runs after a host has been put into maintenance. If no maintenance script is defined, or if the pre-flight or pre-maintenance scripts determine that no maintenance is required, then the host will not be put into maintenance, and the completion of the pre-maintenance scripts will signal the end of all maintenance tasks and the KVM agent will hand the host back to the management server. Once the maintenance scripts have signalled that it has completed, the host agent will signal to the management server that the maintenance tasks have completed, and therefore the host is ready to exit maintenance mode and any 'information' which was collected (such as processing times) will be returned to the management server.
930930

‎source/adminguide/nas_plugin.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Field Value
7676
Name A suitable name to represent the Backup Repository
7777
Address URL, in case of NFS <server IP>:/path
7878
Type NFS ( only NFS type in 4.20)
79-
label.mountopts Any mount point options to be passed while mouting this storage on the hypervisor.
79+
label.mountopts Any mount point options to be passed while mounting this storage on the hypervisor.
8080
Zone The zone in CloudStack with which this Backup Repository must be associated.
8181
=================== ========================
8282

‎source/adminguide/networking/dynamic_static_routing.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,7 @@ For more information, see `“CloudStack Kubernetes Service” <../plugins/cloud
253253

254254

255255
.. |manage-ipv4-subnets-for-zone.png| image:: /_static/images/manage-ipv4-subnets-for-zone.png
256-
:alt: Manage IPv4 subnets for zoone
256+
:alt: Manage IPv4 subnets for zone
257257

258258
.. |manage-ipv4-subnets-for-networks.png| image:: /_static/images/manage-ipv4-subnets-for-networks.png
259259
:alt: Manage IPv4 subnets for guest networks

‎source/adminguide/networking/ip_reservation_in_guest_networks.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ Limitations
9090
- Upgrading network offering which causes a change in CIDR (such as
9191
upgrading an offering with no external devices to one with external
9292
devices) IP Reservation becomes void if any. Reconfigure IP
93-
Reservation in the new re-implemeted network.
93+
Reservation in the new re-implemented network.
9494

9595

9696
Best Practices

‎source/adminguide/service_offerings.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -654,11 +654,11 @@ To create a system service offering:
654654
Network Throttling
655655
------------------
656656

657-
Network throttling is the process of controlling the network bandwith. CloudStack controls this
657+
Network throttling is the process of controlling the network bandwidth. CloudStack controls this
658658
behaviour of the guest networks in the cloud by using the network rate
659659
parameter. This parameter is defined as the default data transfer rate
660660
in Mbps (Megabits Per Second) allowed in a guest network. It defines the
661-
upper limits for network bandwith.
661+
upper limits for network bandwidth.
662662

663663
You can throttle the network bandwidth either to control the usage above
664664
a certain limit for some accounts, or to control network congestion in a

‎source/adminguide/templates.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -597,9 +597,9 @@ Attaching an ISO to a Instance
597597
.. |template-permissions-update-2.png| image:: /_static/images/template-permissions-update-2.png
598598
:alt: Sharing template with 2 specific projects
599599
.. |template-permissions-update-3.png| image:: /_static/images/template-permissions-update-3.png
600-
:alt: Revoking permissins from Account "user8"
600+
:alt: Revoking permissions from Account "user8"
601601
.. |template-permissions-update-4.png| image:: /_static/images/template-permissions-update-4.png
602-
:alt: Revoking permsissons from both projects previously added
602+
:alt: Revoking permissions from both projects previously added
603603
.. |template-permissions-update-5.png| image:: /_static/images/template-permissions-update-5.png
604604
:alt: Resetting (removing all) permissions
605605
.. |iso.png| image:: /_static/images/iso-icon.png

‎source/adminguide/templates/_import_ami.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,14 +102,14 @@ To import an AMI:
102102
none /sys sysfs defaults 0 0
103103
104104
#. Enable login via the console. The default console device in a
105-
XenServer system is xvc0. Ensure that etc/inittab and etc/securetty
105+
XenServer system is xvc0. Ensure that etc/inittab and etc/security
106106
have the following lines respectively:
107107

108108
.. code:: bash
109109
110110
# grep xvc0 etc/inittab
111111
co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
112-
# grep xvc0 etc/securetty
112+
# grep xvc0 etc/security
113113
xvc0
114114
115115
#. Ensure the ramdisk supports PV disk and PV network. Customize this

‎source/adminguide/ui.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -498,7 +498,7 @@ Example for adding custom plugins:
498498
Not all ant icons are supported at the moment. You will find a list of supported icons
499499
within the github repository in ui/src/core/lazy_lib/icons_use.js. To use an icon you
500500
need to transform the listed name. For example "PieChartOutlined" needs to be transformed
501-
to "pie-chart-outlined", "ReadOutlined" needs to be tranformed to "read-outlined".
501+
to "pie-chart-outlined", "ReadOutlined" needs to be transformed to "read-outlined".
502502

503503
For displaying a custom HTML in the plugin, HTML file can be stored in the CloudStack management server's web application directory on the server, i.e., */usr/share/cloudstack-management/webapp* and `path` can be set to the name of the file. For displaying a service or a web page, URL can be set as the `path` of the plugin.
504504

0 commit comments

Comments
 (0)