Merge branch 'master' of https://github.com/Microsoft/AMBROSIA

microsoft · Jun 26, 2019 · d2910c1 · d2910c1
2 parents 9e754d8 + 88af8fe
commit d2910c1
Showing 1 changed file with 7 additions and 7 deletions.
diff --git a/CONTRIBUTING/AMBROSIA_client_network_protocol.md b/CONTRIBUTING/AMBROSIA_client_network_protocol.md
@@ -109,16 +109,16 @@ Message types and associated data which may be sent to or received by services:
 
  * 0 - Incoming RPC (Received):
 
-  - Byte 0 of data is reserved (RPC or return value), and is currently always set to 0 (RPC).
-  - Next is a variable length int (ZigZagInt) which is a method ID.
-  - The next byte is a reserved byte (Fire and forget or Async/Await) and is currently always set to 1 (Fare and Forget).
-  - The remaining bytes are the serialized arguments packed tightly.
+   - Byte 0 of data is reserved (RPC or return value), and is currently always set to 0 (RPC).
+   - Next is a variable length int (ZigZagInt) which is a method ID.
+   - The next byte is a reserved byte (Fire and forget or Async/Await) and is currently always set to 1 (Fire and Forget).
+   - The remaining bytes are the serialized arguments packed tightly.
 
  * 0 - Outgoing RPC (Sent):
 
-  - First is a variable length int (ZigZagInt) which is the length of the destination service.
-  - Next are the actual bytes for the name of the destination service.
-  - Next follow all four fields listed above under "Incoming RPC".
+   - First is a variable length int (ZigZagInt) which is the length of the destination service.
+   - Next are the actual bytes for the name of the destination service.
+   - Next follow all four fields listed above under "Incoming RPC".
 
 That is, an Outgoing RPC is just an incoming RPC with two extra fields on the front.