From e46c7883e1dbcc8d6c1b40f00ddb1dc200e55dfb Mon Sep 17 00:00:00 2001 From: Fred Miller Date: Wed, 24 Oct 2018 15:29:12 +0800 Subject: [PATCH] Fix broken parentheses --- specification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification.md b/specification.md index 340c10a..5a78191 100644 --- a/specification.md +++ b/specification.md @@ -40,7 +40,7 @@ The header part is encoded using the 'ascii' encoding. This includes the '\r\n' ### Content Part Contains the actual content of the message. The content part of a message uses [JSON-RPC](http://www.jsonrpc.org/) to describe requests, responses and notifications. The content part is encoded using the charset provided in the Content-Type field. It defaults to `utf-8`, which is the only encoding supported right now. -Prior versions of the protocol used the string constant `utf8` which is not a correct encoding constant according to [specification](http://www.iana.org/assignments/character-sets/character-sets.xhtml)). For backwards compatibility it is highly recommended that a client and a server treats the string `utf8` as `utf-8`. +(Prior versions of the protocol used the string constant `utf8` which is not a correct encoding constant according to [specification](http://www.iana.org/assignments/character-sets/character-sets.xhtml).) For backwards compatibility it is highly recommended that a client and a server treats the string `utf8` as `utf-8`. ### Example: