diff options
| author |   Jonathan Gathman <jonathan.gathman@att.com> | 2018-09-06 13:52:22 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2018-09-06 13:52:22 +0000 |
| commit | 0f78ee6a1036271b46655d190f03edf6f7d0444b (patch) | |
| tree | a4f895bac18e0fa0ab95055a180eab71e0a96277 /docs/sections | |
| parent | 5882678eebcbaa5d640dbc04a56cbd6f8678719e (diff) | |
| parent | 3819c03ec62382df78c7c62d93582398462c1974 (diff) | |
Merge "Update Spelling issue Issue-ID: AAF-453"
Diffstat (limited to 'docs/sections')
| -rw-r--r-- | docs/sections/architecture/security.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/sections/architecture/security.rst b/docs/sections/architecture/security.rst index 93247899..afc99295 100644 --- a/docs/sections/architecture/security.rst +++ b/docs/sections/architecture/security.rst @@ -12,7 +12,7 @@ The service side is always compute process, but the client can be of two types: * People (via browser, or perhaps command line tool) * Compute process talking to another computer process. -In larger systems, it is atypical to have just one connection, but will the call initiated by the initial actor will cause additional calls after it. Thus, we demonstrate both a client call, and a subsequent call in the following: +In larger systems, it is a typical to have just one connection, but will the call initiated by the initial actor will cause additional calls after it. Thus, we demonstrate both a client call, and a subsequent call in the following: Thus, the essential building blocks of any networked system is made up of a caller and any subsquent calls. |