Update documentation

This refer to BS-156

restcomm/restcomm.docs/sources-asciidoc/src/main/asciidoc/api/Restcomm - Multi-tenancy and Managing Sub-Accounts.adoc

@@ -57,3 +57,13 @@ image:./images/Screen-Shot-2015-10-05-at-16.35.37.png[Screen Shot 2015-10-05 at
 image:./images/Screen-Shot-2015-10-05-at-16.34.53.png[Screen Shot 2015-10-05 at 16.34.53,width=512,height=396]
 
 This is the way that multi tenancy support provides access control between accounts, ensuring that only authorized accounts will be able to see and manage another accounts info.  
+
+[[security-constraints]]
+*Security constraints*
+~~~~~~~~~~~~~~~~~~~~~~
+
+If the hostname of the request doesn't match the organization domain name of the provided account credential Restcomm-Connect will not allow access.
+
+For example, if trying to login to 'https://wonderland.restcomm.com' using account credentials that belong to organization 'https://alice.restcomm.com', Restcomm-Connect will drop the request.
+
+Same is true for accessing organization/account resources using REST API. If the hostname of the REST API request doesn't match the domain name of the organization that the account credentials belong, Restcomm-Connect will drop the request.

restcomm/restcomm.docs/sources-asciidoc/src/main/asciidoc/features/organizations/index.adoc

@@ -23,7 +23,7 @@ include::organizations/uml/component.adoc[]
 
 *   Relative URLs  will be resolved based on the Organization domain name
 
-*   Security constrains will not allow access to organization resources when using wrong domain name, even if valid credential provided.
+*   Security constraints will not allow access to organization resources when hostname of the request doesn't match the domain name of the organization, even if valid credential provided.
 
 
 == High Level Routing

restcomm/restcomm.docs/sources-asciidoc/src/main/asciidoc/release-notes.adoc

@@ -13,7 +13,7 @@ The folowing tags are used to categorize and state the scope of a change
 === New Features
 // New features (whether major or minor) go here
 * Enabled multi-provider routing for the organization SIP domain
-* Support for Organizations in the REST API. New ecurity constrains applied in order to allow access to organization resources only when origin host match the organization domain.
+* Support for Organizations in the REST API. New ecurity constraints applied in order to allow access to organization resources only when hostname of the request match the organization domain that the account credentials belong to.
 
 === Breaking Changes
 // draws attention to functionality that is getting removed