From 86059084b7420224364634d71e7da6001775112f Mon Sep 17 00:00:00 2001
From: Edgar Bonet <linux@edgar-bonet.org>
Date: Wed, 15 May 2019 11:49:47 +0200
Subject: [PATCH] Fix two typos in value-types.html

---
 spec12/value-types.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/spec12/value-types.html b/spec12/value-types.html
index bf1ee33..762544f 100644
--- a/spec12/value-types.html
+++ b/spec12/value-types.html
@@ -86,7 +86,7 @@ <h3><a name="noop-use"></a>Usage</h3>
 
 There is no equivalent to <em>no-op</em> value in the original <a href="http://json.org/">JSON specification</a>.
 
-The <em>NO-OP</em> value is meant to be a <strong>valueless </strong>value; meaning it can be added to the <strong>elements of a container</strong> and when parsed by the receiver, the <em>no-op</em> values are simply skipped and carry know meaningful value with them.
+The <em>NO-OP</em> value is meant to be a <strong>valueless </strong>value; meaning it can be added to the <strong>elements of a container</strong> and when parsed by the receiver, the <em>no-op</em> values are simply skipped and carry no meaningful value with them.
 
 For example, the two following <em>array</em> elements are considered equal (using JSON format for readability):
 <pre>["foo", "bar", "baz"]</pre>
@@ -274,7 +274,7 @@ <h3><a name="numeric-example"></a>Example</h3>
 UBJSON snippets (using block-notation):
 <pre style="padding-left: 30px;">[i][4][int8][i][16]
 [i][5][uint8][U][255]
-[i][5][int16][I]32767]
+[i][5][int16][I][32767]
 [i][5][int32][l][2147483647]
 [i][5][int64][L][9223372036854775807]
 [i][7][float32][d][3.14]