From 448fbbadd4f81033c076a9d66d25a4a7cfe064e9 Mon Sep 17 00:00:00 2001 From: popmechanic Date: Fri, 13 Nov 2015 18:24:53 +0200 Subject: [PATCH] Minor spelling and grammatical edits --- docs/source/ledger-rules/dynamic-permissions.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/source/ledger-rules/dynamic-permissions.rst b/docs/source/ledger-rules/dynamic-permissions.rst index 32f9eab..12fc4c5 100644 --- a/docs/source/ledger-rules/dynamic-permissions.rst +++ b/docs/source/ledger-rules/dynamic-permissions.rst @@ -3,7 +3,7 @@ Dynamic permissions =================== -Openchain supports an implicit permission layout through :ref:`P2PKH accounts ` (``/p2pkh/
/``) and :ref:`thrid party issuance accounts ` (``/asset/p2pkh/
/``). It is also possible to dynamically define permissions by submitting transactions modifying a special record: the ``acl`` record. +Openchain supports an implicit permission layout through :ref:`P2PKH accounts ` (``/p2pkh/
/``) and :ref:`third party issuance accounts ` (``/asset/p2pkh/
/``). It is also possible to dynamically define permissions by submitting transactions modifying a special record: the ``acl`` record. Access Control Lists -------------------- @@ -39,7 +39,7 @@ The schema of the JSON file that the record contains is the following: } ] -The contents is an array containing all the applicable permissions. When the ``acl`` record does not exist, this is equivalent to having an empty array. +The content is an array containing all the applicable permissions. When the ``acl`` record does not exist, this is equivalent to having an empty array. The meaning of the fields within a permission object are the following: @@ -48,7 +48,7 @@ The meaning of the fields within a permission object are the following: - ``addresses``: An array of strings representing the addresses for which signatures are expected. - ``required``: The number of required signatures from the ``addresses`` array. If the ``addresses`` array contains 3 addresses, and ``required`` is set to 2, that means that for the permission to apply, at least 2 signatures from the 3 addresses specified must be present. This is known as a n-of-m multi-signature scheme. -- ``recursive``: (Default: true) A boolean indicating whether the permission applies recursively to the sub accounts. +- ``recursive``: (Default: true) A boolean indicating whether the permission applies recursively to the sub-accounts. .. note:: With recursion, lower level permissions overrule higher level permissions. @@ -87,4 +87,4 @@ A closed loop ledger can be created by denying ``account_modify`` by default, an ``data_modify`` ~~~~~~~~~~~~~~~ -This permission is required to modify a ``DATA`` record. \ No newline at end of file +This permission is required to modify a ``DATA`` record.