Fix spelling mistakes using codespell

This commit corrects various spelling mistakes throughout the
repository. The corrections were made automatically using `codespell`[1]
tool.

[1]: https://github.com/codespell-project/codespell

Change-Id: I965f52f9eae78bcad39a8d711f99bef7be4cbde0
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
diff --git a/yaml/xyz/openbmc_project/Control/Power/Cap.interface.yaml b/yaml/xyz/openbmc_project/Control/Power/Cap.interface.yaml
index 6b0ee09..1782e1f 100644
--- a/yaml/xyz/openbmc_project/Control/Power/Cap.interface.yaml
+++ b/yaml/xyz/openbmc_project/Control/Power/Cap.interface.yaml
@@ -41,7 +41,7 @@
           PowerCap value is normally less than or equal to the MinPowerCapValue.
           When the PowerCap is set to any value between MinSoftPowerCapValue and
           MinPowerCapValue an attempt will be made to maintain the cap but it
-          will not be guaranted.
+          will not be guaranteed.
 
     - name: ExceptionAction
       type: enum[self.ExceptionActions]
@@ -83,9 +83,9 @@
                 Hard Power Off system and log event.
 
           - name: LogEventOnly
-            decription: >
+            description: >
                 Log Event Only.
 
           - name: Oem
-            decription: >
+            description: >
                 OEM defined action.
diff --git a/yaml/xyz/openbmc_project/Control/Power/CapLimits.interface.yaml b/yaml/xyz/openbmc_project/Control/Power/CapLimits.interface.yaml
index 9e17801..a284218 100644
--- a/yaml/xyz/openbmc_project/Control/Power/CapLimits.interface.yaml
+++ b/yaml/xyz/openbmc_project/Control/Power/CapLimits.interface.yaml
@@ -26,4 +26,4 @@
           PowerCap value is normally less than or equal to the MinPowerCapValue.
           When the PowerCap is set to any value between MinSoftPowerCapValue and
           MinPowerCapValue an attempt will be made to maintain the cap but it
-          will not be guaranted.
+          will not be guaranteed.
diff --git a/yaml/xyz/openbmc_project/Control/Power/Mode.interface.yaml b/yaml/xyz/openbmc_project/Control/Power/Mode.interface.yaml
index 54fe794..d7a707b 100644
--- a/yaml/xyz/openbmc_project/Control/Power/Mode.interface.yaml
+++ b/yaml/xyz/openbmc_project/Control/Power/Mode.interface.yaml
@@ -35,24 +35,24 @@
           Possible Power Mode settings
       values:
           - name: BalancedPerformance
-            decription: >
+            description: >
                 The system performs at the highest speeds while utilization is
                 high and performs at reduced speeds when the utilization is low.
           - name: EfficiencyFavorPerformance
-            decription: >
+            description: >
                 The system performs at reduced speeds at all utilizations to
                 save power while attempting to maintain performance. This mode
                 differs from EfficiencyFavorPower in that more performance is
                 retained but less power is saved.
           - name: EfficiencyFavorPower
-            decription: >
+            description: >
                 The system performs at reduced speeds at all utilizations to
                 save power at the cost of performance. This mode differs from
                 PowerSaving in that more performance is retained and less power
                 is saved. This mode differs from EfficiencyFavorPerformance in
                 that less performance is retained but more power is saved.
           - name: MaximumPerformance
-            decription: >
+            description: >
                 This value shall indicate the system performs at the highest
                 speeds possible. This mode should be used when performance is
                 the top priority.
diff --git a/yaml/xyz/openbmc_project/Control/Power/Throttle.interface.yaml b/yaml/xyz/openbmc_project/Control/Power/Throttle.interface.yaml
index 5a33494..9ea0abd 100644
--- a/yaml/xyz/openbmc_project/Control/Power/Throttle.interface.yaml
+++ b/yaml/xyz/openbmc_project/Control/Power/Throttle.interface.yaml
@@ -32,7 +32,7 @@
                 The cause of the component being throttled is a fault detected
                 by management hardware or firmware
           - name: PowerLimit
-            decription: >
+            description: >
                 The cause of the component being throttled is a power limit.
           - name: ThermalLimit
             description: >
diff --git a/yaml/xyz/openbmc_project/Control/PowerSupplyRedundancy.interface.yaml b/yaml/xyz/openbmc_project/Control/PowerSupplyRedundancy.interface.yaml
index 432b2c2..1b82137 100644
--- a/yaml/xyz/openbmc_project/Control/PowerSupplyRedundancy.interface.yaml
+++ b/yaml/xyz/openbmc_project/Control/PowerSupplyRedundancy.interface.yaml
@@ -67,6 +67,6 @@
                 value, the status will show in progress.
           - name: completed
             description: >
-                For single ndoe system, the status always keep show completed.
+                For single node system, the status always keep show completed.
                 For multi-node system, only after all the nodes sync to same
                 value of the properties, the status will be completed.
diff --git a/yaml/xyz/openbmc_project/Control/ThermalMode.interface.yaml b/yaml/xyz/openbmc_project/Control/ThermalMode.interface.yaml
index 901c934..91a7c5d 100644
--- a/yaml/xyz/openbmc_project/Control/ThermalMode.interface.yaml
+++ b/yaml/xyz/openbmc_project/Control/ThermalMode.interface.yaml
@@ -14,7 +14,7 @@
       flags:
           - readonly
       description: >
-          An implemention specific list of supported modes that the thermal
+          An implementation specific list of supported modes that the thermal
           control application can be configured to provide for a platform.
     - name: Current
       type: string