Merge "[codespell] doc,devstack and gate typos"

doc/source/admin/cpu-topologies.rst

@@ -778,7 +778,7 @@ governors on the fly, as explained below.
    supports scaling govenors before modifying the configuration option.
 
 If the strategy is set to ``governor``, a couple of config options are provided
-to define which exact CPU govenor to use for each of the up and down states :
+to define which exact CPU governor to use for each of the up and down states :
 
 - :oslo.config:option:`libvirt.cpu_power_governor_low` will define the governor
   to use for the powerdown state (defaults to ``powersave``)

doc/source/admin/pci-passthrough.rst

@@ -519,7 +519,7 @@ For the viommu attributes:
 
 * ``intremap``, ``caching_mode``, and ``iotlb``
   options for viommu (These attributes are driver attributes defined in
-  `Libvirt IOMMU Domain`_) will direcly enabled.
+  `Libvirt IOMMU Domain`_) will directly enabled.
 
 * ``eim`` will directly enabled if machine type is Q35.
   ``eim`` is driver attribute defined in `Libvirt IOMMU Domain`_.

doc/source/admin/resource-limits.rst

@@ -39,7 +39,7 @@ Libvirt enforces CPU limits in terms of *shares* and *quotas*, configured
 via :nova:extra-spec:`quota:cpu_shares` and :nova:extra-spec:`quota:cpu_period`
 / :nova:extra-spec:`quota:cpu_quota`, respectively. Both are implemented using
 the `cgroups cpu controller`__. Note that allowed values for *shares* are
-platform dependant.
+platform dependent.
 
 CPU shares are a proportional weighted share of total CPU resources relative to
 other instances. It does not limit CPU usage if CPUs are not busy. There is no
@@ -158,7 +158,7 @@ For example, to configure **outbound** traffic to an average of 262 Mbit/s
 .. note::
 
    The speed limit values in above example are specified in kilobytes/second,
-   whle the burst value is in kilobytes.
+   while the burst value is in kilobytes.
 
 VMWare
 ~~~~~~

doc/source/admin/scheduling.rst

@@ -1077,7 +1077,7 @@ to a negative number and the weighing has the opposite effect of the default.
 
 This weigher compares hosts and orders them based on their number of instances
 respectively. By default the weigher is doing nothing but you
-can change its behaviour by modifiying the value of
+can change its behaviour by modifying the value of
 :oslo.config:option:`filter_scheduler.num_instances_weight_multiplier`.
 A positive value will favor hosts with a larger number of instances (packing
 strategy) while a negative value will follow a spread strategy that will

doc/source/contributor/api-ref-guideline.rst

@@ -309,7 +309,7 @@ Parameter type
 ~~~~~~~~~~~~~~
 
 The parameters are defined in the parameter file (``parameters.yaml``).
-The type of parameters have to be one of followings:
+The type of parameters have to be one of following:
 
 * ``array``
 

doc/source/contributor/process.rst

@@ -76,7 +76,7 @@ used by many OpenStack projects, including the following steps.
 
 - Dependency Freeze
 
-  -  time to co-ordinate the final list of dependencies, and give packagers
+  -  time to coordinate the final list of dependencies, and give packagers
      time to package them
   -  generally it is also quite destabilising to take upgrades (beyond
      bug fixes) this late

doc/source/index.rst

@@ -160,7 +160,7 @@ the defaults from the :doc:`install guide </install/index>` will be sufficient.
 * :doc:`Running nova-api on wsgi <user/wsgi>`: Considerations for using a real
   WSGI container instead of the baked-in eventlet web server.
 
-.. # NOTE(amotoki): toctree needs to be placed at the end of the secion to
+.. # NOTE(amotoki): toctree needs to be placed at the end of the section to
    # keep the document structure in the PDF doc.
 .. toctree::
    :hidden:

doc/source/reference/update-provider-tree.rst

@@ -181,7 +181,7 @@ would become:
       provider_tree.update_inventory(nodename, inv_data)
 
 When reporting inventory for the standard resource classes ``VCPU``,
-``MEMORY_MB`` and ``DISK_GB``, implementors of ``update_provider_tree`` may
+``MEMORY_MB`` and ``DISK_GB``, implementers of ``update_provider_tree`` may
 need to set the ``allocation_ratio`` and ``reserved`` values in the
 ``inv_data`` dict based on configuration to reflect changes on the compute
 for allocation ratios and reserved resource amounts back to the placement