Correct typos

eeps/eep-0034.md

@@ -31,7 +31,7 @@ When communicating with end points implemented by other party it is
 not always possible to suggest that packet length is present in
 big endian format or that it is 4 bytes.  Today with 64-bit machine
 showing up it may even be possible that we soon find protocols sending
-plain machin dependent 64-bit words as packet length descriptors.
+plain machine dependent 64-bit words as packet length descriptors.
 
 
 
@@ -42,20 +42,20 @@ This EEP suggest to extend the packet bytes to the range 0-8.  Note
 that the internal maximum packet size is not affected by this EEP,
 only the format of the packet size indicator.
 
-Further more a negative range is suggested to signal little endian
-formated size indicator in range -1 .. -8.  The `{packet,-1}` is
+Furthermore a negative range is suggested to signal little endian
+formated size indicator in range -1 .. -8.  `{packet,-1}` is
 equivalent with `{packet,1}`.  The number of packets bytes prefixed is
 thus `abs(PBytes)` where `PBytes` is in range -8 .. 8.
 
 This EEP also suggest a fixed size packet mode, expressed as `{packet,
 {size,N}}`.  This mode acts much like `{packet,0}` in regards to
 packet bytes, no packet bytes are used.  The difference is that, in
-`{active,true}` or `{active,once}` mode, while `{packet,0}` collectes
+`{active,true}` or `{active,once}` mode, while `{packet,0}` collects
 any data available, the `{packet,{size,N}}` mode collects exacly `N`
 bytes before passing it on to the "owner" process.  Suggested
-implementation minium limitiations for `N` is unsigned 16-bit,
-resulting in a minium size of 1 and and maximum size of 65535.  A
-packet size of less than 1 should always result in badarg error.
+implementation minimum limitations for `N` is unsigned 16-bit,
+resulting in a minimum size of 1 and and maximum size of 65535.  A
+packet size of less than 1 should always result in a badarg error.
 
 
 
@@ -70,14 +70,14 @@ The packet types suggest by this EEP are:
 
 -   `{packet,{size,N}}`  
     `N` is in range > 0 and the maximum `N` is implementation 
-    dependant but never less then 65535.
+    dependent but never less then 65535.
 
 
 
 Backward compatiblity
 =====================
 
-The author of this EEP have implemented this proposal in the
+The author of this EEP has implemented this proposal in the
 Erlang/OTP standard git release, and has not found any backwards
 compatiblity problems.  The files affected by this proposal
 implementation are: `inet_drv.c`, `packet_parser.c`, `packet_parser.h`