diff --git a/yaml/xyz/openbmc_project/BIOSConfig/Password.interface.yaml b/yaml/xyz/openbmc_project/BIOSConfig/Password.interface.yaml
index ba0f823..5f8d5e7 100644
--- a/yaml/xyz/openbmc_project/BIOSConfig/Password.interface.yaml
+++ b/yaml/xyz/openbmc_project/BIOSConfig/Password.interface.yaml
@@ -29,4 +29,4 @@
     - name: PasswordInitialized
       type: boolean
       description: >
-          To indicate BIOS password related details are recevied or not.
+          To indicate BIOS password related details are received or not.
diff --git a/yaml/xyz/openbmc_project/BIOSConfig/README.md b/yaml/xyz/openbmc_project/BIOSConfig/README.md
index 5e00e0a..84ca76e 100644
--- a/yaml/xyz/openbmc_project/BIOSConfig/README.md
+++ b/yaml/xyz/openbmc_project/BIOSConfig/README.md
@@ -22,11 +22,11 @@
 - `SetAttribute` -To set the particular BIOS attribute with new value.
 - `GetAttribute` -To get the bios attribute current and pending values.
 
-Properites:
+Properties:
 
 - `ResetBIOSSettings` - To reset the BIOS settings based on the Reset Flag.
 - `BaseBiosTable` - To store all bios attributes details.
-- `PendingAttributes` - To store pending bios Atrributes list.
+- `PendingAttributes` - To store pending bios Attributes list.
 
 ### Interface xyz.openbmc_project.BIOSConfig.Password
 
@@ -36,7 +36,7 @@
 
 - `ChangePassword` - To change BIOS setup password.
 
-Properities:
+Properties:
 
 - `PasswordInitialized` - To indicate BIOS password related details are received
   or not.
diff --git a/yaml/xyz/openbmc_project/Certs/README.md b/yaml/xyz/openbmc_project/Certs/README.md
index d013d7d..ab76598 100644
--- a/yaml/xyz/openbmc_project/Certs/README.md
+++ b/yaml/xyz/openbmc_project/Certs/README.md
@@ -90,7 +90,7 @@
 
 - BMC updates the private key associated to CSR for any new CSR request.
 - BMC upload process automatically appends certificate file with system CSR
-  private key, for the service which requirs certificate and key.
+  private key, for the service which requires certificate and key.
 - CSR based Certificate validation is alway's based on private key in the
   system.
 
@@ -168,7 +168,7 @@
 
 - certificate manager should provide interface to delete the existing
   certificate.
-- Incase of server type certificate deleting a signed certificate will create a
+- In case of server type certificate deleting a signed certificate will create a
   new self signed certificate and will install the same.
 
 ### Boot process
@@ -176,7 +176,7 @@
 - certificate management instances should be created based on the system
   configuration.
 
-- Incase of no Https certificate or invalid Https certificate, certificate
+- In case of no Https certificate or invalid Https certificate, certificate
   manager should update the https certificate with self signed certificate.
 
 ### Repository
@@ -237,22 +237,22 @@
   set with error details, if success response message is set with the replaced
   certificate details.
 
-#### Bootup
+#### Boot up
 
-- During bootup certificate objects created for the existing certificates.
+- During boot up certificate objects created for the existing certificates.
 
 ### Errors thrown by Certificate Manager
 
 - NotAllowed exception thrown if Install method invoked with a certificate
   already existing. At present only one certificate per server and client
   certificate type is allowed.
-- InvalidCertificate excption thrown for validation errors.
+- InvalidCertificate exception thrown for validation errors.
 
 #### Certificate Deletion
 
 - For server and client certificate type the certificate deletion is not
   allowed. In case of authority certificate type the delete option is acceptable
-  and can be done on individial certificates, for example:
+  and can be done on individual certificates, for example:
 
 ```plain
 url: redfish/v1/Managers/bmc/Truststore/Certificates/1
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
diff --git a/yaml/xyz/openbmc_project/Dump/Entry.interface.yaml b/yaml/xyz/openbmc_project/Dump/Entry.interface.yaml
index fcb275e..e7f38f9 100644
--- a/yaml/xyz/openbmc_project/Dump/Entry.interface.yaml
+++ b/yaml/xyz/openbmc_project/Dump/Entry.interface.yaml
@@ -22,7 +22,7 @@
             type: string
             description: >
                 The location to offload dump file, error InvalidArgument will be
-                returned if the URI is not well formated.
+                returned if the URI is not well formatted.
       errors:
           - xyz.openbmc_project.Common.File.Error.Open
           - xyz.openbmc_project.Common.File.Error.Write
diff --git a/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml b/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml
index 08b33a8..daf19d9 100644
--- a/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml
+++ b/yaml/xyz/openbmc_project/Dump/Entry/FaultLog.interface.yaml
@@ -20,6 +20,6 @@
       description: >
           This is intended to be a unique identifier, depending on Type, to
           reference the primary fault data log but is not intended otherwise to
-          be programatically interpreted (e.g. string parsing)
+          be programmatically interpreted (e.g. string parsing)
       flags:
           - const
diff --git a/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml b/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml
index c75fd29..9b94f63 100644
--- a/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml
+++ b/yaml/xyz/openbmc_project/Dump/Entry/System.interface.yaml
@@ -3,7 +3,7 @@
 
     System dumps are dump of the host memory and hardware states generated
     during a failure in the host firmware. This can be a huge dump stored in the
-    host memory, the BMC doesnt store this dump but stream this dump to an
+    host memory, the BMC doesn't store this dump but stream this dump to an
     external client based on the offload request. Apart from system generated
     system dump, users can also request for this kind of dump.
 
diff --git a/yaml/xyz/openbmc_project/Inventory/Connector/Slot.interface.yaml b/yaml/xyz/openbmc_project/Inventory/Connector/Slot.interface.yaml
index c19d4ae..c98f4b2 100644
--- a/yaml/xyz/openbmc_project/Inventory/Connector/Slot.interface.yaml
+++ b/yaml/xyz/openbmc_project/Inventory/Connector/Slot.interface.yaml
@@ -1,4 +1,4 @@
 description: >
     Implement to provide slot connector attributes. An slot component is a
     swappable component that can be removed by a user and considered
-    field-replaceable. The slot compoment represents a PCIe slot connections.
+    field-replaceable. The slot component represents a PCIe slot connections.
diff --git a/yaml/xyz/openbmc_project/Inventory/Decorator/CLEI.interface.yaml b/yaml/xyz/openbmc_project/Inventory/Decorator/CLEI.interface.yaml
index 9647bd9..6c4a601 100644
--- a/yaml/xyz/openbmc_project/Inventory/Decorator/CLEI.interface.yaml
+++ b/yaml/xyz/openbmc_project/Inventory/Decorator/CLEI.interface.yaml
@@ -1,6 +1,6 @@
 description: >
     Implement to indicate an item with a defined Common Language Equipment
-    Identifer (CLEI) number.
+    Identifier (CLEI) number.
 
 properties:
     - name: CLEINumber
diff --git a/yaml/xyz/openbmc_project/Inventory/Item/README.md b/yaml/xyz/openbmc_project/Inventory/Item/README.md
index 8280658..a80b4a2 100644
--- a/yaml/xyz/openbmc_project/Inventory/Item/README.md
+++ b/yaml/xyz/openbmc_project/Inventory/Item/README.md
@@ -6,7 +6,7 @@
 accessed, such as a board, a chassis and a drive. Some objects are embedded in
 other objects, such as a BMC embedded in a board, or a core in a CPU. The DBus
 interfaces in this directory describe the DBus representation of those physical
-objects. A graph consisting of Inventory objects as vertexes and Association as
+objects. A graph consisting of Inventory objects as vertices and Association as
 edges can be constructed that represents the relationship between different
 parts (such as chassis, drive, sensors, etc) of the system.
 
diff --git a/yaml/xyz/openbmc_project/Led/README.md b/yaml/xyz/openbmc_project/Led/README.md
index 7bc2df5..1f5d37c 100644
--- a/yaml/xyz/openbmc_project/Led/README.md
+++ b/yaml/xyz/openbmc_project/Led/README.md
@@ -87,10 +87,10 @@
 
 ## Mandatory groups
 
-It is mandatory that all implementations provide definitions of atleast 2 groups
-namely; **bmc_booted** and **power_on**. Those would be asserted post reaching
-BMCReady and PowerOn respecively. It is fine to have no LEDs in those groups but
-the group as such is deemed required.
+It is mandatory that all implementations provide definitions of at least 2
+groups namely; **bmc_booted** and **power_on**. Those would be asserted post
+reaching BMCReady and PowerOn respectively. It is fine to have no LEDs in those
+groups but the group as such is deemed required.
 
 Example: The Group yaml may just be;
 
diff --git a/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml b/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml
index d867fa2..fd10b11 100644
--- a/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml
+++ b/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml
@@ -44,7 +44,7 @@
     - name: configured_by
       description: >
           Endpoints exposed by platform configuration should host a
-          configured_by assocation back to the object that drove the endpoint's
+          configured_by association back to the object that drove the endpoint's
           existence.
       reverse_name: configures
       required_endpoint_interfaces:
diff --git a/yaml/xyz/openbmc_project/MCTP/README.md b/yaml/xyz/openbmc_project/MCTP/README.md
index 0d3f5cf..6b10a8f 100644
--- a/yaml/xyz/openbmc_project/MCTP/README.md
+++ b/yaml/xyz/openbmc_project/MCTP/README.md
@@ -20,7 +20,7 @@
 
 The D-Bus object path for MCTP endpoints are named
 `xyz/openbmc_project/mctp/<NetworkId>/<EID>` where NetworkId is the locally
-defined [network identfier][1] the endpoint is part of and EID is the endpoint
+defined [network identifier][1] the endpoint is part of and EID is the endpoint
 ID. This aids in the enumeration of the endpoints belonging to an MCTP network.
 The D-Bus object implements the `xyz.openbmc_project.MCTP.Endpoint` interface.
 The object may also optionally implement `xyz.openbmc_project.Common.UUID`
@@ -35,7 +35,7 @@
 different MCTP Networks. If the implementation supports the optional MCTP
 network ID then it is exposed on the D-Bus. The D-Bus object path is
 `xyz/openbmc_project/mctp/<NetworkId>` where NetworkId is the locally defined
-[network identfier][1] and implements the `xyz.openbmc_project.Common.UUID`
+[network identifier][1] and implements the `xyz.openbmc_project.Common.UUID`
 interface and the UUID property is the MCTP network ID.
 
 [1]:
diff --git a/yaml/xyz/openbmc_project/Metric/Value.interface.yaml b/yaml/xyz/openbmc_project/Metric/Value.interface.yaml
index 23973da..9c9d3c1 100644
--- a/yaml/xyz/openbmc_project/Metric/Value.interface.yaml
+++ b/yaml/xyz/openbmc_project/Metric/Value.interface.yaml
@@ -102,7 +102,7 @@
           - name: ReadWriteStorage
             description: >
                 The available read write storage. This storage path has been
-                explicity added to the interface file as it gets used in BMCWeb
+                explicitly added to the interface file as it gets used in BMCWeb
                 and free storage metric gets exposed via Redfish.
             value: storage/rw
           - name: RebootCount
diff --git a/yaml/xyz/openbmc_project/Network/Client.interface.yaml b/yaml/xyz/openbmc_project/Network/Client.interface.yaml
index 3ad4d6a..539b4b0 100644
--- a/yaml/xyz/openbmc_project/Network/Client.interface.yaml
+++ b/yaml/xyz/openbmc_project/Network/Client.interface.yaml
@@ -1,7 +1,7 @@
 description: >
     This defines the network endpoint. Application which wants to keep the
     network endpoint info can use this interface. e.g: Network endpoint could be
-    SNMP mangers or LDAP servers etc.
+    SNMP managers or LDAP servers etc.
 properties:
     - name: Address
       type: string
diff --git a/yaml/xyz/openbmc_project/Network/EthernetInterface.interface.yaml b/yaml/xyz/openbmc_project/Network/EthernetInterface.interface.yaml
index f39fd13..addaaf7 100644
--- a/yaml/xyz/openbmc_project/Network/EthernetInterface.interface.yaml
+++ b/yaml/xyz/openbmc_project/Network/EthernetInterface.interface.yaml
@@ -58,7 +58,7 @@
           DHCP provisioning is not enabled for name server configuration. As an
           implementation option this may also be used in addition to DHCP
           provided addresses, or in cases where the DHCP server provides no DNS
-          assigments.
+          assignments.
       errors:
           - xyz.openbmc_project.Common.Error.InvalidArgument
     - name: NTPServers
diff --git a/yaml/xyz/openbmc_project/Smbios/MDR_V2.interface.yaml b/yaml/xyz/openbmc_project/Smbios/MDR_V2.interface.yaml
index 4582ac2..23d8afd 100644
--- a/yaml/xyz/openbmc_project/Smbios/MDR_V2.interface.yaml
+++ b/yaml/xyz/openbmc_project/Smbios/MDR_V2.interface.yaml
@@ -61,7 +61,7 @@
           - name: status
             type: boolean
             description: >
-                Need to continue directory transmisson or not.
+                Need to continue directory transmission or not.
       errors:
           - self.Error.InvalidParameter
 
@@ -99,7 +99,7 @@
           - name: timeStamp
             type: uint32
             description: >
-                Timestamp determinded by the agent.
+                Timestamp determined by the agent.
       returns:
           - name: status
             type: boolean
diff --git a/yaml/xyz/openbmc_project/Software/Image.errors.yaml b/yaml/xyz/openbmc_project/Software/Image.errors.yaml
index c2fda85..ae1806e 100644
--- a/yaml/xyz/openbmc_project/Software/Image.errors.yaml
+++ b/yaml/xyz/openbmc_project/Software/Image.errors.yaml
@@ -5,6 +5,6 @@
 - name: InternalFailure
   description: The operation failed internally during processing the image.
 - name: ImageFailure
-  description: An error occured processing the image.
+  description: An error occurred processing the image.
 - name: BusyFailure
   description: The device is busy during the update.
diff --git a/yaml/xyz/openbmc_project/Software/README.md b/yaml/xyz/openbmc_project/Software/README.md
index 66ed4a3..8309acd 100644
--- a/yaml/xyz/openbmc_project/Software/README.md
+++ b/yaml/xyz/openbmc_project/Software/README.md
@@ -103,7 +103,7 @@
 have the same string in its `Inventory.Decorator.Compatible` interface. These
 strings shall be of the following format:
 
-- `<org>.Software.Element.<identifer>.Type.<type>`
+- `<org>.Software.Element.<identifier>.Type.<type>`
 
 Where:
 
diff --git a/yaml/xyz/openbmc_project/Software/Update.interface.yaml b/yaml/xyz/openbmc_project/Software/Update.interface.yaml
index 4191c1f..b2f11d1 100644
--- a/yaml/xyz/openbmc_project/Software/Update.interface.yaml
+++ b/yaml/xyz/openbmc_project/Software/Update.interface.yaml
@@ -1,10 +1,10 @@
 description: >
-    Interface for performing code update for various firwmare entities.
+    Interface for performing code update for various firmware entities.
 
 methods:
     - name: StartUpdate
       description: >
-          Start a firware update to be performed asynchronously.
+          Start a firmware update to be performed asynchronously.
       parameters:
           - name: Image
             type: unixfd
diff --git a/yaml/xyz/openbmc_project/State/Decorator/Availability.interface.yaml b/yaml/xyz/openbmc_project/State/Decorator/Availability.interface.yaml
index 75f6bcc..b28eaba 100644
--- a/yaml/xyz/openbmc_project/State/Decorator/Availability.interface.yaml
+++ b/yaml/xyz/openbmc_project/State/Decorator/Availability.interface.yaml
@@ -1,5 +1,5 @@
 description: >
-    Implement to indicate the availablity status of the object
+    Implement to indicate the availability status of the object
 properties:
     - name: Available
       type: boolean
diff --git a/yaml/xyz/openbmc_project/User/Manager.interface.yaml b/yaml/xyz/openbmc_project/User/Manager.interface.yaml
index 4cc0ab0..34fda33 100644
--- a/yaml/xyz/openbmc_project/User/Manager.interface.yaml
+++ b/yaml/xyz/openbmc_project/User/Manager.interface.yaml
@@ -59,7 +59,7 @@
 
     - name: GetUserInfo
       description: >
-          Get user properites. If its local user, method returns
+          Get user properties. If its local user, method returns
              -user privilege
              -user groups
              -user enabled state
diff --git a/yaml/xyz/openbmc_project/VirtualMedia/MountPoint.interface.yaml b/yaml/xyz/openbmc_project/VirtualMedia/MountPoint.interface.yaml
index 34e3efa..75c3728 100644
--- a/yaml/xyz/openbmc_project/VirtualMedia/MountPoint.interface.yaml
+++ b/yaml/xyz/openbmc_project/VirtualMedia/MountPoint.interface.yaml
@@ -1,5 +1,5 @@
 description: >
-    Defines the object configuration like mounting mode, image paths, timouts
+    Defines the object configuration like mounting mode, image paths, timeouts
     etc.
 
 properties: