From 1e80a36061d52155c5a8fddb56228c820d100288 Mon Sep 17 00:00:00 2001
From: Luca Favatella <luca.favatella@erlang-solutions.com>
Date: Thu, 8 Jun 2017 13:56:15 +0100
Subject: [PATCH] Correct documentation of semantics of `strict` option

See https://github.com/talentdeficit/jsx/blob/2.8.2/src/jsx_config.erl#L78
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 108a125..9f72709 100644
--- a/README.md
+++ b/README.md
@@ -440,7 +440,7 @@ additional options beyond these. see
         escape sequences not adhering to the json spec result in a `badarg` error
     
     any combination of these can be passed to **jsx** by using `{strict, [strict_option()]}`.
-    `strict` is equivalent to `{strict, [comments, utf8, single_quotes, escapes]}` 
+    `strict` is equivalent to `{strict, [comments, trailing_commas, utf8, single_quotes, escapes]}`
 
 - `return_tail`