From fc09c5024c6883a3e8a0f7b245b3787c24da44c2 Mon Sep 17 00:00:00 2001 From: Jimmy99 Date: Wed, 6 Apr 2016 13:15:58 +0200 Subject: [PATCH] Update 08.4.md typographical errors and improved readability --- en/08.4.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/en/08.4.md b/en/08.4.md index 2259d222..24c20109 100644 --- a/en/08.4.md +++ b/en/08.4.md @@ -29,12 +29,12 @@ Normally, an RPC call from client to server has the following ten steps: Go has official support for RPC in its standard library on three levels, which are TCP, HTTP and JSON RPC. Note that Go RPC is not like other traditional RPC systems. It requires you to use Go applications on both client and server sides because it encodes content using Gob. -Functions of Go RPC have must abide by the following rules for remote access, otherwise the corresponding calls will be ignored. +Functions of Go RPC must abide by the following rules for remote access, otherwise the corresponding calls will be ignored. -- Functions are exported (capitalize). -- Functions have to have two arguments with exported types. +- Functions are exported (capitalized). +- Functions must have two arguments with exported types. - The first argument is for receiving from the client, and the second one has to be a pointer and is for replying to the client. -- Functions have to have a return value of error type. +- Functions must have a return value of error type. For example: