Correct typos

Author: eproxus

eeps/eep-0001.md

@@ -272,7 +272,7 @@ versions of the EEP are posted to erlang-questions.  Both headers
 should be in dd-mmm-yyyy format, e.g. 14-Aug-2009.
 
 Standards Track EEPs must have a Erlang-Version header which indicates
-the version of Erlang that the feature will or has be released with.  
+the version of Erlang that the feature will or has be released with.
 Process EEPs do not need a Erlang-Version header. The version must be
 in the same format as the git tag scheme of Erlang/OTP project.
 
@@ -306,7 +306,7 @@ want to submit corrections to the [EEP repository](https://github.com/erlang/eep
 When in doubt about where to send your changes, please check first
 with the EEP author and/or EEP editor.
 
-EEP authors can update EEPs by submitting changes to thei pull requests.
+EEP authors can update EEPs by submitting changes to their pull requests.
 
 Transferring EEP Ownership
 ==========================

eeps/eep-0033.md

@@ -129,7 +129,7 @@ See the [Markdown][] Syntax for general formatting syntax.  On top of
 this Markdown EEPs has these requirements:
 
 The first lines of the EEP is for EEP index generator parsing and the
-Markdow preprocessing so it must look like the first 10 lines of
+Markdown preprocessing so it must look like the first 10 lines of
 [this file][eep.md], with that specific style of horizontal rule
 and header 2 title.  Your EEP may have more or less header lines.