diff --git a/designs/boot-progress.md b/designs/boot-progress.md
index b514baf..18852a5 100644
--- a/designs/boot-progress.md
+++ b/designs/boot-progress.md
@@ -87,7 +87,7 @@
   appropriately in both IPMI and PLDM based stacks
   - It is the responsibility of the IPMI or PLDM implementation to update
     the `BootProgress` property on D-Bus
-  - It is the responsiblity the phosphor-state-manager to update the
+  - It is the responsibility the phosphor-state-manager to update the
     `BootProgressLastUpdate` property on D-Bus when it sees `BootProgress`
     updated
 - Ensure the new Redfish `LastState` and `LastStateTime` properties
diff --git a/designs/management-console/VMI_Certificate_Exchange.md b/designs/management-console/VMI_Certificate_Exchange.md
index bf1cce3..d848ad5 100644
--- a/designs/management-console/VMI_Certificate_Exchange.md
+++ b/designs/management-console/VMI_Certificate_Exchange.md
@@ -225,7 +225,7 @@
   D-bus property and updates the Status property to Complete in the Dbus object.
 - Create new interface SignCSR in webserver which takes CSR string as input and returns
   certificate string.This interface calls SignCSR dbus method and looks for Status
-  property changed singal to verify status.Reads ClientCertificate property content and
+  property changed signal to verify status.Reads ClientCertificate property content and
   return certificate string.
 - On completion of serving the sign CSR request, respective dbus object will be deleted
   before returning certificate string to client.
diff --git a/designs/management-console/service-discovery.md b/designs/management-console/service-discovery.md
index 3491fba..cadf4f4 100644
--- a/designs/management-console/service-discovery.md
+++ b/designs/management-console/service-discovery.md
@@ -39,7 +39,7 @@
 service file with the given data. We are enhancing this infrastructure to add
 the vendor-specific information in the avahi service file(under txt-record).
 
-Followings commits implements the behaviour.
+Following commits implements the behaviour.
 
  https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/22950
  https://gerrit.openbmc-project.xyz/c/openbmc/meta-ibm/+/22951
diff --git a/designs/mctp/mctp-kernel.md b/designs/mctp/mctp-kernel.md
index ac19dee..77394ec 100644
--- a/designs/mctp/mctp-kernel.md
+++ b/designs/mctp/mctp-kernel.md
@@ -77,7 +77,7 @@
 
 A network defines a unique address space for MCTP endpoints by endpoint-ID
 (described by DSP0236, section 3.2.31). A network has a user-visible identifier
-to allow refernces from userspace. Route definitions are specific to one
+to allow references from userspace. Route definitions are specific to one
 network.
 
 Interfaces are associated with one network. A network may be associated with one
diff --git a/designs/mctp/mctp-userspace.md b/designs/mctp/mctp-userspace.md
index 3b051c5..c21e95a 100644
--- a/designs/mctp/mctp-userspace.md
+++ b/designs/mctp/mctp-userspace.md
@@ -6,7 +6,7 @@
 MCTP design description, background and requirements.
 
 This document describes a userspace implementation of MCTP
-infrastructure, allowing a straightforward mechnism of supporting MCTP
+infrastructure, allowing a straightforward mechanism of supporting MCTP
 messaging within an OpenBMC system.
 
 ## Proposed Design
diff --git a/designs/multihost-ipmi-design.md b/designs/multihost-ipmi-design.md
index ee43d19..98a2871 100644
--- a/designs/multihost-ipmi-design.md
+++ b/designs/multihost-ipmi-design.md
@@ -177,7 +177,7 @@
 +--------------------------------------------+
 ```
 In the above diagram one instance of netipmid runs per host. Each instance
-is tied to one virtual ethernet interface, The virutal interface ID can be
+is tied to one virtual ethernet interface, The virtual interface ID can be
 used to make a devIndex. This represents the HostId.
 
 ## Alternatives Considered
diff --git a/designs/phosphor-audit.md b/designs/phosphor-audit.md
index 6d7b8b8..0418c9c 100644
--- a/designs/phosphor-audit.md
+++ b/designs/phosphor-audit.md
@@ -327,7 +327,7 @@
 
  * Exec application via 'system' call.
  * The code for directed handling type inside handler itself.
-   As example for 'net ipmi' in case of unsuccesful user login inside handler:
+   As example for 'net ipmi' in case of unsuccessful user login inside handler:
    * Sends a notification to administrator.
    * echo heartbeat > /sys/class/leds/alarm_red/trigger
 
diff --git a/development/dev-environment.md b/development/dev-environment.md
index 082683d..e2afbe4 100644
--- a/development/dev-environment.md
+++ b/development/dev-environment.md
@@ -193,12 +193,12 @@
 
   yocto has tools for building and running qemu. These tools avoid some of the
   configuration issues that come from downloading a prebuilt image, and
-  mofifying binaries. Using yocto qemu also uses the [TAP
+  modifying binaries. Using yocto qemu also uses the [TAP
   interface](https://www.kernel.org/doc/Documentation/networking/tuntap.txt)
   which some find be more stable. This is particularly useful when debugging
   at the application level.
 
-  - set up a bmc build enviroment
+  - set up a bmc build environment
   ```
   source setup romulus myBuild/build
   ```