diff --git a/docs/development/machine_error_codes.md b/docs/development/machine_error_codes.md
index 62cbc0ae52..156806f3fb 100644
--- a/docs/development/machine_error_codes.md
+++ b/docs/development/machine_error_codes.md
@@ -392,7 +392,7 @@ A Provider can OPTIONALLY implement this driver call. Else should return a `UNIM
 This driver call will be called by the MCM to get the `VolumeIDs` for the list of `PersistentVolumes (PVs)` supplied.
 This OPTIONAL (but recommended) driver call helps in serailzied eviction of pods with PVs while draining of machines. This implies applications backed by PVs would be evicted one by one, leading to shorter application downtimes.
 
-- On succesful returnal of a list of `Volume-IDs` for all supplied `PVSpecs`, the Provider MUST reply `0 OK`.
+- On successful returnal of a list of `Volume-IDs` for all supplied `PVSpecs`, the Provider MUST reply `0 OK`.
 - The `GetVolumeIDsResponse` is expected to return a repeated list of `strings` consisting of the `VolumeIDs` for `PVSpec` that could be extracted.
 - If for any `PV` the Provider wasn't able to identify the `Volume-ID`, the provider MAY chose to ignore it and return the `Volume-IDs` for the rest of the `PVs` for whom the `Volume-ID` was found.
 - Getting the `VolumeID` from the `PVSpec` depends on the Cloud-provider. You can extract this information by parsing the `PVSpec` based on the `ProviderType`
@@ -522,4 +522,4 @@ This string MAY be surfaced by MCM to end users.
 
 ### Deploying
 * **Recommended:** The MCM and Provider are typically expected to run as two containers inside a common `Pod`.
-* However, for the security reasons they could execute on seperate Pods provided they have a secure way to exchange data between them.
+* However, for the security reasons they could execute on seperate Pods provided they have a secure way to exchange data between them.
\ No newline at end of file