From a3385763015ecde5bcf0e1426fbcbb06dfdad7d3 Mon Sep 17 00:00:00 2001 From: Jonathan Ma Date: Fri, 14 Jul 2017 00:01:44 +0800 Subject: [PATCH] Fix a likely grammar issue. --- TechnicalWhitePaper.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TechnicalWhitePaper.md b/TechnicalWhitePaper.md index d4d4b6ef..fd225310 100644 --- a/TechnicalWhitePaper.md +++ b/TechnicalWhitePaper.md @@ -152,7 +152,7 @@ Each account can send structured messages to other accounts and may define scrip Permission management involves determining whether or not a message is properly authorized. The simplest form of permission management is checking that a transaction has the required signatures, but this implies that required signatures are already known. Generally authority is bound to individuals or groups of individuals and is often compartmentalized. The EOS.IO software provides a declarative permission management system that gives accounts fine grained and high level control over who can do what and when. -It is critical that authentication and permission management be standardized and separate from the business logic of the application. This enables tools to be developed to manage permissions in a general purpose manner and also provide significant opportunities for performance optimization. +It is critical that authentication and permission management be standardized and separated from the business logic of the application. This enables tools to be developed to manage permissions in a general purpose manner and also provide significant opportunities for performance optimization. Every account may be controlled by any weighted combination of other accounts and private keys. This creates a hierarchical authority structure that reflects how permissions are organized in reality, and makes multi-user control over funds easier than ever. Multi-user control is the single biggest contributor to security, and, when used properly, it can greatly eliminate the risk of theft due to hacking.