edits

Author: ShashiSubramanya

modules/ROOT/pages/embed-spotter.adoc

@@ -18,9 +18,8 @@ To embed Spotter, you need the following access and setup:
 
 [NOTE]
 ====
-For Spotter embedding that uses cookieless authentication, use the Visual Embed SDK v1.45.0 or later with ThoughtSpot Cloud 26.2.0.cl or a later version. To enable proactive token refresh, set the `refreshAuthTokenOnNearExpiry` parameter to `true`.
-
-Spotter workflows can run longer, so ensure the authentication token expiry is set to at least 10 minutes to avoid authorization errors.
+For Spotter embedding that uses cookieless authentication, use the Visual Embed SDK v1.45.0 or later with ThoughtSpot Cloud 26.2.0.cl or a later version. To enable proactive token refresh, set the `refreshAuthTokenOnNearExpiry` parameter to `true`. +
+Spotter workflows can run longer, so set the authentication token expiry to at least 10 minutes to avoid authorization errors.
 ====
 
 

modules/ROOT/pages/filters_overview.adoc

@@ -13,14 +13,14 @@ The behavior of each filter type and the mechanism for setting filters can diffe
 There are different types of filters, which can be applied in the following order:
 
 1. xref:rls-rules.adoc[**Row-level security (RLS) Rules**] +
-Rules are defined at the table level and applied at the query generation layer to all objects derived from that table. Rules can be defined based on the logged-in user, their group memberships, or custom variables. +
+Rules are defined at the table level and applied during query generation to all objects derived from that table. Rules can be defined based on the logged-in user, their group memberships, or custom variables. +
 RLS rules secure data and cannot be altered by the logged-in user. +
 RLS rules can also be used, along with custom variables and the JSON Web Token (JWT) generated for the user, to implement xref:abac_rls-variables.adoc[Attribute-Based Access Control (ABAC)].
 
 2. **Data Model filters** +
 Models can have parameters, formulas, and filters. +
 Embedding application users cannot affect the formulas or filters, which are always applied, but Parameters used in a formula can be set by other methods. +
-If the user can edit the Parameter, use the runtime parameters layer to programmatically set the parameter value.
+If the user can edit the parameter, use the runtime parameters layer to programmatically set its value.
 
 3. xref:runtime-filters.adoc[Runtime filters] and xref:runtime-parameters.adoc[Runtime Parameters] +
 You can define xref:runtime-filters.adoc[runtime filters] and xref:runtime-parameters.adoc[runtime parameters] within the browser for a given object at load time. Filters and parameters can be set using the Visual Embed SDK, REST API, or URL query parameters and updated via host events in the Visual Embed SDK.
@@ -32,22 +32,22 @@ Runtime filters do not display as UI filter components.
 
 4. link:https://docs.thoughtspot.com/cloud/latest/liveboard-filters[Liveboard filters, window=_blank] +
 Liveboard filters apply to all visualizations on the Liveboard and are visible as UI components at the top of a Liveboard page. When a filter is clicked, a modal with filter options appropriate for the data type is displayed. +
-Liveboard users can add or modify filters as required. If you are embedding a Liveboard that includes preset filters, you can programmatically update, reset, or remove filters using the `HostEvent.UpdateFilters`.
+Liveboard users can add or modify filters as needed. If you are embedding a Liveboard that includes preset filters, you can programmatically update, reset, or remove filters using the `HostEvent.UpdateFilters`.
 
 5. link:https://docs.thoughtspot.com/cloud/latest/liveboard-filters-cross[Liveboard cross filters, window=_blank] +
-Cross-filters are ad-hoc filters based on user selection. These filters are used for brushing and linking Liveboard visualizations. +
-Cross-filters are supported only on attribute columns.
+Cross filters are ad-hoc filters based on user selection. These filters are used for brushing and linking Liveboard visualizations. +
+Cross filters are supported only on attribute columns.
 
 6. link:https://docs.thoughtspot.com/cloud/latest/filters[Search query filters, window=_blank] +
 Set via the search query string in Answers and visualizations, not visible as UI filter components on a Liveboard, but can be viewed in **Explore** or *Edit* modes. +
-The lowest layer of filters is defined as part of the search query for a given Answer or visualization on a Liveboard. +
+The lowest layer of filters is defined in the search query for a given Answer or visualization on a Liveboard. +
 The link:https://docs.thoughtspot.com/cloud/latest/filters[filter terms, window=_blank] are saved as part of the `search_query` of the object, visible in TML.
 
 == Filter attributes
 When specifying a column for filtering, you must use the exact column name as defined in the model. Filters can be applied to string, number, boolean, Date, Datetime, and time data types.
 For the `DATE` and `DATE_TIME` data types, some filter types may require the date and time values to be specified in the Epoch time format.
 
-All operations include a form of `WHERE` clause being applied to the resulting queries generated by ThoughtSpot, or no query being issued if the resulting logic is always false.
+All operations result in a `WHERE` clause being applied to the queries generated by ThoughtSpot, or no query being issued if the logic is always false.
 
 A data filter object in ThoughtSpot typically includes the following attributes:
 
@@ -200,7 +200,7 @@ LiveboardEmbed.trigger(HostEvent.OpenFilter,
 ----
 
 === UpdateFilters event
-The link:https://developers.thoughtspot.com/docs/Enumeration_HostEvent#_updatefilters[HostEvent.UpdateFilters] directly updates the values of the target Liveboard filter:
+The link:https://developers.thoughtspot.com/docs/Enumeration_HostEvent#_updatefilters[HostEvent.UpdateFilters] directly updates the values of the target of an existing filter that's currently applied on a Liveboard:
 
 [source,JavaScript]
 ----
@@ -214,22 +214,17 @@ liveboardEmbed.trigger(HostEvent.UpdateFilters, {
    });
 ----
 
-The Liveboard filter must already exist on the Liveboard for `HostEvent.UpdateFilters` to work.
-
-For more information and examples, see xref:embed-pinboard.adoc#_filters[Liveboard filters].
-
 === GetFilters and GetParameters events
 If you want to build your own filter UI within the embedding app, you can find out details of the Liveboard and runtime filters that are defined using the link:https://developers.thoughtspot.com/docs/Enumeration_HostEvent#_getfilters[HostEvent.GetFilters]. There is an equivalent link:https://developers.thoughtspot.com/docs/Enumeration_HostEvent#_getparameters[HostEvent.GetParameters] to get the currently set Parameter values:
 
 [source,JavaScript]
 ----
 const data = await liveboardEmbed.trigger(HostEvent.GetFilters);
-    console.log('data', data);
+console.log('data', data);
 
 liveboardEmbed.trigger(HostEvent.GetParameters).then((parameter) => {
- console.log('parameters', parameter);
+    console.log('parameters', parameter);
 });
-
 ----
 
 Note that `HostEvent.GetFilters` and `HostEvent.GetParameters` return a promise directly rather than taking a callback function as their second argument.
@@ -465,8 +460,7 @@ liveboardEmbed.trigger(HostEvent.UpdateFilters, {
    });
 ----
 
-Setting empty values via `HostEvent.UpdateFilters` removes only the values applied to the filter and it doesn't remove or hide the filter chip from the Liveboard.
-
+Setting empty values via `HostEvent.UpdateFilters` removes only the filter values; it does not remove or hide the filter chips from the Liveboard.
 
 
 ////