From 64f56a15d7b2c5643e3b14a2f3bd16109745c7a8 Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Tue, 11 Nov 2014 18:15:06 +0000 Subject: [PATCH] fix english and whitespace --- specification/11_event_signing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specification/11_event_signing.rst b/specification/11_event_signing.rst index 966efdc2..ee5e5938 100644 --- a/specification/11_event_signing.rst +++ b/specification/11_event_signing.rst @@ -19,7 +19,7 @@ JSON received from the network is likely to be already encoded using UTF-8. We sort the keys to give a consistent ordering. We force integers to be in the range where they can be accurately represented using IEEE double precision floating point numbers since a number of JSON libraries represent all numbers -use these to store all numbers. +using this representation. .. code:: python @@ -93,7 +93,7 @@ sign the JSON. The currently support value for *signing algorithm* is is used to distinguish between different signing keys used by the same entity. The ``unsigned`` object and the ``signatures`` object are not covered by the -signature. Therefore intermediate servers can add unsigneddata such as time stamps +signature. Therefore intermediate servers can add unsigned data such as timestamps and additional signatures.