per Org URL update

Author: ShashiSubramanya

modules/ROOT/pages/orgs.adoc

@@ -6,7 +6,7 @@
 :page-pageid: orgs
 :page-description: You can now configure your ThoughtSpot instance as a mult-tenant cluster with separate Org containers for your tenants.
 
-If your deployment requires logical separation of departments within your organization, or if it involves supporting many distinct organizations from a single application instance, use the *Orgs* feature. 
+If your deployment requires logical separation of departments within your organization, or if it involves supporting many distinct organizations from a single application instance, use the *Orgs* feature.
 
 Using Orgs, you can set boundaries within the ThoughtSpot system and isolate each tenant's data in such a way that it is independent of and invisible to other tenant workspaces configured on the same application instance.
 
@@ -46,12 +46,12 @@ Each Org other than the Primary Org serves as an independent container with its
 
 If a user only belongs to a single Org, their experience of ThoughtSpot is as if it were single-tenant.
 
-If a user belongs to multiple Orgs, they will see a menu allowing them to switch between the Orgs they belong to. 
+If a user belongs to multiple Orgs, they will see a menu allowing them to switch between the Orgs they belong to.
 
 All activity within ThoughtSpot is always within the context of *one Org*, even if the user has access to multiple Orgs. They can *switch between Orgs* but not do any actions across Orgs.
 
-=== Administering Orgs
-The cluster administrator can create an Org for each tenant account, configure groups and assign users, and define access to data objects within that org.  
+=== Orgs deployment and administration
+The cluster administrator can create an Org for each tenant account, configure groups and assign users, and define access to data objects within that org.
 
 The following figure depicts the Orgs presentation on a multi-tenant ThoughtSpot instance.
 
@@ -128,7 +128,7 @@ For more information, see link:https://docs.thoughtspot.com/cloud/latest/orgs-ov
 [earlyAccess eaBackground]#Early Access#
 
 A user belonging to multiple Orgs can share ThoughtSpot objects such as Liveboards and Answers, with users of another Org. This will require the object to have share permissions, and both users to be part of the parent Org of the shared object.
- 
+
 //With the current implementation, users belonging to multiple Orgs had to select the parent Org of a shared object from a list while trying to access it from a different Org.
 
 Starting with ThoughtSpot Cloud 10.5.0.cl release, developers embedding ThoughtSpot in their application will be able to edit their custom link settings for their application users to allow seamless access to content from another different Org. For example, a user has
@@ -152,7 +152,7 @@ The Org ID will be passed in the URL depending on the placement of `{ts-query-pa
 
 * The developers are advised to update their implementation to accommodate the Org ID in the `{ts-query-params}` while setting up the link:https://developers.thoughtspot.com/docs/customize-links[custom links] for their application users. This will enable the users to seamlessly access ThoughtSpot objects across Orgs in a multi-Org setup, without causing any disruption to the current workflow.
 * The `overrideOrgId` parameter in the SDK  can accept the Org ID from the resulting URL as its input value.
-* The `overrideOrgId` parameter may not work properly with auth types - trusted authentication (`AuthType.TrustedAuthToken`) or cookieless authentication (`AuthType.TrustedAuthTokenCookieless`) simultaneously in the same browser, if `tokenAuthPerOrg` is already enabled on the ThoughtSpot instance.
+* The `overrideOrgId` parameter may not work properly with trusted authentication (`AuthType.TrustedAuthToken`) or cookieless authentication (`AuthType.TrustedAuthTokenCookieless`), if `tokenAuthPerOrg` is already enabled on your ThoughtSpot instance.
 ====
 
 == Feature availability on a multi-tenant instance
@@ -321,4 +321,3 @@ The following conditions apply to OIDC authentication on a multi-tenant setup:
 * If the Org mapping is enabled on the ThoughtSpot cluster, the Group mapping will not work.
 
 For more information on OIDC authentication, see xref:configure-oidc.adoc[OpenID Connect authentication].
-