Merge branch 'clarify-sub-org' into 'master'

Clarify language for sub orgs

See merge request !27

docs/shared-org-vs-sub-org.md

@@ -2,7 +2,7 @@
 
 Informatica Intelligent Cloud Services (IICS) uses the concept of an organization (an "org") as the highest level container for objects, which include assets, projects, connections.
 Orgs also contain a unique set of users and user groups.
-When on-boarding to IICS, a decision will have to be made on whether to use the existing org for UW-Madison, or use a separate org (a "sub-org").
+When on-boarding to IICS, a decision will have to be made on whether to use the existing org for UW-Madison, or use a new parent org with sub-orgs.
 
 The purpose of this document is to help prepare for this decision.
 
@@ -63,4 +63,4 @@ Unlike using the shared org, using this multi-org approach has extra financial c
 Here are cases when using this multi-org approach would be recommended:
 
 - More than one non-prod environment is needed, since the shared org approach only provides one test and one prod environment.
-- Many integrations are being built, requiring many objects. As a general rule, if you have over 30 projects or connections, this would be better managed by having your own org rather than using the shared org.
\ No newline at end of file
+- Many integrations are being built, requiring many objects. As a general rule, if you have over 30 projects or connections, this would be better managed by having your own org rather than using the shared org.