From 721132c4dc04908c1d50af503565f65754d9613b Mon Sep 17 00:00:00 2001
From: metanoic <5554798+metanoic@users.noreply.github.com>
Date: Fri, 29 Jun 2018 13:56:51 -0500
Subject: [PATCH] Fix minor spelling/grammar in protocol doc

---
 docs/protocol.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/protocol.md b/docs/protocol.md
index 1a3bae4f..f916b1fe 100644
--- a/docs/protocol.md
+++ b/docs/protocol.md
@@ -3,13 +3,13 @@
 
 Communicating with an ODrive consists of a series of endpoint operations.
 An endpoint can theoretically be any kind data serialized in any way.
-There is a default seralization implementation for POD types; for custom types
-you must (de)seralize yourself. In the future we may provide a default seralizer
-for stucts.
+There is a default serialization implementation for POD types; for custom types
+you must (de)serialize yourself. In the future we may provide a default serializer
+for structs.
 The available endpoints can be enumerated by reading the JSON from endpoint 0
 and can theoretically be different for each communication interface (they are not in practice).
 
-Each endpoint operation can send bytes to one endpoint (referenced by it's ID)
+Each endpoint operation can send bytes to one endpoint (referenced by its ID)
 and at the same time receive bytes from the same endpoint. The semantics of
 these payloads are specific to each endpoint's type, the name of which is
 indicated in the JSON.