@wix/bookings 1.0.301 → 1.0.303

package/build/cjs/src/bookings-availability-v2-time-slot.universal.d.ts

@@ -19,7 +19,7 @@ export declare const __debug: {
  * 5. What is the total capacity and remaining capacity of the service at the time of the calculation of the `TimeSlot`?
  *
  * > __Note:__
- * When the `TimeSlot` has a non empty `NestedTimeSlots`, it represents the availability information
+ * > When the `TimeSlot` has a non empty `NestedTimeSlots`, it represents the availability information
  * > for a given list of `Appointment` services within a specific time slot.
  */
 export interface TimeSlot {
@@ -33,17 +33,11 @@ export interface TimeSlot {
     /**
      * Local start date of the time slot in ISO-8601 format.
      * For example, "2024-01-30T13:30:00".
-     *
-     * > When returned from `MultiServiceAvailabilityTimeSlots` API calls,
-     * > represents the earliest `localStartDate` of the `TimeSlot`'s nested time slots.
      */
     localStartDate?: string | null;
     /**
      * Local end date of the time slot in ISO-8601 format.
      * For example, "2024-01-30T14:30:00".
-     *
-     * > When returned from `MultiServiceAvailabilityTimeSlots` API calls,
-     * > represents the latest `localEndDate` of the `TimeSlot`'s nested time slots.
      */
     localEndDate?: string | null;
     /**
@@ -51,39 +45,22 @@ export interface TimeSlot {
      *
      * If booking this time slot does not violates any of the service's booking policies,
      * the returned value is `true`. Otherwise, returns `false`.
-     *
-     * > When returned from `MultiServiceAvailabilityTimeSlots` API calls,
-     * > + `bookable` is `false` if at least one of the provided services is not bookable within the time slot.
-     * > + `bookable` is `true` if all provided services are bookable within the time slot.
      */
     bookable?: boolean | null;
-    /**
-     * The geographic location of the slot.
-     *
-     * > When returned from `MultiServiceAvailabilityTimeSlots` API calls,
-     * > the geographic location of all nested time slots of the `TimeSlot`.
-     */
+    /** The geographic location of the slot. */
     location?: Location;
-    /**
-     * Total number of spots for the slot.
-     *
-     * > When returned from `MultiServiceAvailabilityTimeSlots` API calls,
-     * > `totalCapacity` is always 1, regardless the number of requested services.
-     */
+    /** Total number of spots for the slot. */
     totalCapacity?: number | null;
     /**
      * Remaining number of spots for the slot.
      * For example, for an appointment service with total capacity of 1 spot and one booked spot, the remaining capacity will be 0.
-     *
-     * > When returned from `MultiServiceAvailabilityTimeSlots` API calls,
-     * > `remainingCapacity` is 1 if all requested services has `remainingCapacity` >= 1.
-     * > `remainingCapacity` is 0, if there is at least one requested service with `remainingCapacity` < 1.
      */
     remainingCapacity?: number | null;
     /**
-     * > When returned from `ListMultiServiceAvailabilityTimeSlots`,
-     * > indicates that at least one of the nested time slots does not meet with at least one of the service's booking policies.
-     * > There is no indication which of the requested services violates a booking policy.
+     * Indicators for booking policy violations for the slot.
+     *
+     * Each nested field is checked on its own. i.e. if `tooEarlyToBook` is defined and `bookOnlineDisabled` is not defined
+     * we will return also slots for which `tooEarlyToBook` is same as on the request, regardless of `bookOnlineDisabled`.
      */
     bookingPolicyViolations?: BookingPolicyViolations;
     /**
@@ -324,43 +301,57 @@ export interface ListMultiServiceAvailabilityTimeSlotsRequest {
      * Services for which the multiService time slots are being returned for.
      * Each service contains its own resources filters within.
      *
-     * MinSize: 2.
-     * MaxSize: 8.
+     * MinSize: `2`.
+     * MaxSize: `8`.
+     *
+     * Required, unless `cursorPaging`.`cursor` is provided.
      */
     services?: Service[];
     /**
      * Lower boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T13:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
      */
     fromLocalDate?: string | null;
     /**
      * Upper boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T14:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
      */
     toLocalDate?: string | null;
     /**
      * Time zone, in IANA time zone format.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
      */
     timeZone?: string | null;
     /**
-     * Location for which the multiService time slots are being returned for.
+     * Location for which the multiService TimeSlots are being returned for.
      *
-     * You can specify location or location type for which the time slots will be returned for.
-     * > __Note:__ Supports filtering by location type, or by locationId. Other fields like `name` are ignored.
-     * > If locationType is `BUSINESS`, you __must__ provide a locationId.
+     * You can specify location or location type for which the TimeSlots will be returned for.
+     * If locationType is `BUSINESS`, you __must__ provide a locationId.
+     *
+     * <blockquote class="warning">
+     * <p><strong>warning:</strong><br/>
+     * Supports filtering by location type, or by location ID. </br>
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
+     * </blockquote>
+     *
+     * Required, unless `cursorPaging`.`cursor` is provided.
      */
     location?: Location;
     /**
-     * Whether the `TimeSlot` is bookable according all of the services booking policies.
+     * Whether the `TimeSlot` is bookable according to all of the services booking policies.
      *
-     * If booking any of the `TimeSlot`.`NestedTimeSlot`'s violates any of its services bookings policies,
+     * If booking any of the `TimeSlot`.`NestedTimeSlot`s violates any of its services bookings policies,
      * returns as `false`. Otherwise, returns as `true`.
      *
      * > __Note:__
@@ -374,7 +365,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsRequest {
      * A bookable time slot must not violate any policy,
      * therefor, this filter is only relevant when `bookable` filter is false.
      *
-     * Each nested field is checked on all `NestedTimeSlot`'s. For example, if only one of the `NestedTimeSlot`'s
+     * Each nested field is checked on all `NestedTimeSlot`s. For example, if only one of the `NestedTimeSlot`'s
      * has a service with `tooEarlyToBook` same as in the request, we return the `TimeSlot` regardless of whether
      * the other `NestedTimeSlots` has the same `tooEarlyToBook` as in request.
      *
@@ -384,7 +375,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsRequest {
     bookingPolicyViolations?: BookingPolicyViolations;
     /**
      * Maximum number of slots to load for each day. For example, if `timeSlotsPerDay` is set to `3`,
-     * we return at most 3 available `TimeSlot`'s for each day within the date range specified in request.
+     * we return at most 3 available TimeSlots for each day within the date range specified in request.
      *
      * By default,
      * if `bookable` filter was not specified,
@@ -397,8 +388,8 @@ export interface ListMultiServiceAvailabilityTimeSlotsRequest {
     /**
      * CursorPaging.
      *
-     * Enables you to fetch `TimeSlot`'s in smaller, more manageable chunks
-     * by setting a limit on the number of `TimeSlots` returned in response.
+     * Enables you to fetch TimeSlots in smaller, more manageable chunks
+     * by setting a limit on the number of results returned in response.
      * This is useful in order to enhance efficiency of data retrieval and reduce load on both the client and server.
      *
      * If there are more results than the specified limit, the response will contain a `cursorPagingMetaData`
@@ -410,17 +401,12 @@ export interface ListMultiServiceAvailabilityTimeSlotsRequest {
      * the `cursorPaging`.`limit`. You may pass a different `limit`.
      * No need to specify any additional parameters.
      *
-     * __TODO: This is only describes the current behavior, should be fixed__
      * <blockquote class="important">
      * <p><strong>Important:</strong><br/>
-     * If you only provide a `cursorPaging`.`cursor`,
-     * the response will contain the default size of results = 1000.
+     * If you only provide a <code class="grey-background">cursorPaging</code>. <code class="grey-background">cursor</code>,
+     * the response will contain the default size of results which is `1000`.
      * </p>
      * </blockquote>
-     *
-     * cursorPaging.limit:
-     * Default: 1000
-     * Max: 1000
      */
     cursorPaging?: CommonCursorPaging;
 }
@@ -442,10 +428,10 @@ export interface Service {
 }
 export interface CommonCursorPaging {
     /**
-     * Number of items to load.
+     * Number of results to load.
      *
-     * Default: `1000`
-     * Max: `1000`
+     * Default: `1000`.
+     * Max: `1000`.
      */
     limit?: number | null;
     /**
@@ -462,7 +448,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsResponse {
     timeSlots?: TimeSlot[];
     /**
      * Time zone, in IANA time zone format.
-     * Shared for all `TimeSlot`'s in response.
+     * Shared for all TimeSlots in response.
      */
     timeZone?: string | null;
     /**
@@ -475,8 +461,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsResponse {
      *
      * <blockquote class="important">
      * <p><strong>Important:</strong><br/>
-     * `count` is not supported.
-     * </p>
+     * <code class="grey-background">count</code> is not supported.</p>
      * </blockquote>
      */
     cursorPagingMetadata?: CommonCursorPagingMetadata;
@@ -499,7 +484,7 @@ export interface CommonCursors {
 }
 export interface GetMultiServiceAvailabilityTimeSlotRequest {
     /**
-     * Services for which the multiService time slots are being returned for.
+     * Services for which the multiService TimeSlots are being returned for.
      * Each service contains its own resources filters within.
      *
      * MinSize: 2.
@@ -522,12 +507,11 @@ export interface GetMultiServiceAvailabilityTimeSlotRequest {
      * The location of the time slot.
      *
      * You must provide a specific `locationType`.
-     * If locationType is `BUSINESS`, you __must__ also provide a locationId.
+     * If locationType is `BUSINESS`, you __must__ also provide a `locationId`.
      *
-     * <blockquote class="important">
-     * <p><strong>Important:</strong><br/>
-     * `name` and `formattedAddress` are ignored.
-     * </p>
+     * <blockquote class="warning">
+     * <p>Supports filtering by location type, or by location ID.
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
      * </blockquote>
      */
     location: Location;
@@ -541,29 +525,34 @@ export interface GetMultiServiceAvailabilityTimeSlotResponse {
 export interface ListAvailabilityTimeSlotsRequest {
     /**
      * Service ID for which the time slots are being returned for.
-     * Currently supports only services of type `Appointment`.
+     * Currently supported only for services of type `APPOINTMENT`.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
      */
     serviceId?: string | null;
     /**
      * Lower boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T13:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
      */
     fromLocalDate?: string | null;
     /**
      * Upper boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T14:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
-     * > The `localEndDate` of the returned `TimeSlot` is the `TimeSlot`'s `localStartDate` + the service duration
      */
     toLocalDate?: string | null;
     /**
      * Time zone, in IANA time zone format.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
      */
     timeZone?: string | null;
@@ -572,34 +561,37 @@ export interface ListAvailabilityTimeSlotsRequest {
      *
      * By default,
      * if no locations are provided,
-     * the response contains `TimeSlot`'s for all locations where the service is available.
+     * the response contains TimeSlots for all locations where the service is available.
      *
      * You can specify locations or location types for which the time slots will be returned for.
-     * > __Note:__ Supports filtering by location type, or by locationId. Other fields like `name` are ignored.
-     * > If locationType is `BUSINESS`, you __must__ provide a locationId.
+     * If locationType is `BUSINESS`, you __must__ provide a locationId.
+     *
+     * <blockquote class="warning">
+     * <p><strong>warning:</strong><br/>
+     * Supports filtering by location type, or by location ID. </br>
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
+     * </blockquote>
      */
     locations?: Location[];
     /**
      * Resources to include in response.
      *
      * If specified,
-     * the returned time slots will contain __up__ to 10 available resources out of the provided list.
-     * Otherwise, the returned time slots returns with an empty `AvailableResources`.
-     * > __Note:__ Not specifying `resourceIds` can be handy in case you want to avoid large response in flows that only
-     * > interested whether the time slots are available or not. [An example for such flow](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/service-availability-time-slots/sample-flows#all-apis_wix-service-availability_service-availability-time-slots_sample-flows_let-your-customers-to-dynamically-select-an-available-time-slot-for-any-of-your-business-services).
+     * the returned TimeSlots will contain __up__ to 10 available resources out of the provided list.
+     * Otherwise, the returned TimeSlots returns with an empty `AvailableResources`.
      */
     resourceIds?: string[];
     /**
-     * Resource type ID's to include in response, this is in addition to the requested resourceIds.
+     * Resource type ID's to include in response, this is in addition to the requested `resourceIds`.
      *
-     * If specified in request, the returned time slots will contain __up__ to 10 `AvailableResources` with `ResourceTypeId`
+     * If specified in request, the returned TimeSlots will contain __up__ to 10 `AvailableResources` with `ResourceTypeId`
      * out of those specified, each contains __up__ to 10 available resources of this type.
      */
     includeResourceTypeIds?: string[];
     /**
      * Whether the `TimeSlot` is bookable according to the service's booking policies.
      *
-     * If booking this time slot does not violates any of the service's booking policies,
+     * If booking this `TimeSlot` does not violates any of the service's booking policies,
      * returns as `true`. Otherwise, returns as `false`.
      *
      * > __Note:__
@@ -619,7 +611,7 @@ export interface ListAvailabilityTimeSlotsRequest {
     bookingPolicyViolations?: BookingPolicyViolations;
     /**
      * Maximum number of slots to load for each day. For example, if `timeSlotsPerDay` is set to `3`,
-     * we return at most 3 available `TimeSlot`'s for each day within the date range specified in request.
+     * we return at most 3 available TimeSlots for each day within the date range specified in request.
      *
      * By default,
      * if `bookable` filter was not specified,
@@ -632,8 +624,8 @@ export interface ListAvailabilityTimeSlotsRequest {
     /**
      * CursorPaging.
      *
-     * Enables you to fetch `TimeSlot`'s in smaller, more manageable chunks
-     * by setting a limit on the number of `TimeSlots` returned in response.
+     * Enables you to fetch results in smaller, more manageable chunks
+     * by setting a limit on the number of results returned in response.
      * This is useful in order to enhance efficiency of data retrieval and reduce load on both the client and server.
      *
      * If there are more results than the specified limit, the response will contain a `cursorPagingMetaData`
@@ -641,21 +633,16 @@ export interface ListAvailabilityTimeSlotsRequest {
      * returned cursor to the next call as `cursorPaging`.`cursor`.
      *
      * For the first call, you should only specify the `limit` for the results page.
-     * For each following call, you should only pass the previous returned cursor as `cursorPaging`.`cursor`
-     * the `cursorPaging`.`limit`. You may pass a different `limit`.
+     * For each following call, you should only pass `cursorPaging`.`cursor` with the returned cursor from previous call, and
+     * a `cursorPaging`.`limit`.
      * No need to specify any additional parameters.
      *
-     * __TODO: This is only describes the current behavior, should be fixed__
      * <blockquote class="important">
      * <p><strong>Important:</strong><br/>
-     * If you only provide a `cursorPaging`.`cursor`,
-     * the response will contain the default size of results = 1000.
+     * If you only provide a <code class="grey-background">cursorPaging</code>. <code class="grey-background">cursor</code>,
+     * the response will contain the default size of results which is `1000`.
      * </p>
      * </blockquote>
-     *
-     * cursorPaging.limit:
-     * Default: 1000
-     * Max: 1000
      */
     cursorPaging?: CommonCursorPaging;
 }
@@ -664,7 +651,7 @@ export interface ListAvailabilityTimeSlotsResponse {
     timeSlots?: TimeSlot[];
     /**
      * Time zone, in IANA time zone format.
-     * Shared for all `TimeSlot`'s in response.
+     * Shared for all TimeSlots in response.
      */
     timeZone?: string | null;
     /**
@@ -677,8 +664,7 @@ export interface ListAvailabilityTimeSlotsResponse {
      *
      * <blockquote class="important">
      * <p><strong>Important:</strong><br/>
-     * `count` is not supported.
-     * </p>
+     * <code class="grey-background">count</code> is not supported.</p>
      * </blockquote>
      */
     cursorPagingMetadata?: CommonCursorPagingMetadata;
@@ -686,7 +672,7 @@ export interface ListAvailabilityTimeSlotsResponse {
 export interface GetAvailabilityTimeSlotRequest {
     /**
      * Service ID of the time slot.
-     * Currently supports only services of type `Appointment`.
+     * Currently supported only for services of type `APPOINTMENT`.
      */
     serviceId: string;
     /**
@@ -705,12 +691,11 @@ export interface GetAvailabilityTimeSlotRequest {
      * The location of the time slot.
      *
      * You must provide a specific `locationType`.
-     * If locationType is `BUSINESS`, you __must__ also provide a locationId.
+     * If locationType is `BUSINESS`, you __must__ also provide a `locationId`.
      *
-     * <blockquote class="important">
-     * <p><strong>Important:</strong><br/>
-     * `name` and `formattedAddress` are ignored.
-     * </p>
+     * <blockquote class="warning">
+     * <p>Supports filtering by location type, or by location ID.
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
      * </blockquote>
      */
     location: Location;
@@ -718,16 +703,14 @@ export interface GetAvailabilityTimeSlotRequest {
      * Resources to include in response.
      *
      * If specified,
-     * the returned time slot contain only the available resources out of provided list.
-     * Otherwise, the returned time slot returned with all possible `AvailableResources`.
-     * > __Note:__ This can be handy in case you want to avoid large response in flows that only
-     * > interested to check the availability of the time slot for specific resources.
+     * the returned `TimeSlot` contains only the available resources out of provided list.
+     * Otherwise, the returned `TimeSlot` returned with all possible `AvailableResources`.
      */
     resourceIds?: string[];
     /**
-     * Resource type ID's to include in response, this is in addition to the requested resourceIds.
+     * Resource type IDs to include in response, this is in addition to the requested `resourceIds`.
      *
-     * If specified in request, the returned time slot contain only the `AvailableResources` with `ResourceTypeId`
+     * If specified in request, the returned `TimeSlot` contains only the `AvailableResources` with `ResourceTypeId`
      * out of those specified, each contains all the available resources of this type.
      */
     includeResourceTypeIds?: string[];
@@ -827,102 +810,83 @@ export interface GetAvailabilityTimeSlotResponseNonNullableFields {
     };
 }
 /**
- * Retrieves a list of multiService `TimeSlot`'s that match the provided filters.
+ * Retrieves a list of multiService `TimeSlot`s that match the provided filters.
+ *
  * <blockquote class="important">
  * <p><strong>Important:</strong><br/>
- * Currently supported only for services of type `APPOINTMENT`.
- * </p>
+ * Currently supported only for services of type <code class="grey-background">APPOINTMENT</code>.</p>
  * </blockquote>
  *
- * The request body __must__ include one of:
- *
- * + All of the following filters:  `serviceId`, `fromLocalDate`, `toLocalDate`, `location`, and `timeZone`. You may add additional filters as you wish.
+ * The request body __must__ include either:
+ * + All of the following filters:  `service`.`serviceId`, `fromLocalDate`, `toLocalDate`, `location`, and `timeZone`. You may add additional filters as you wish.
  * + A `cursorPaging` with a valid `cursor` from previous response.
  *
  *
  * Each [TimeSlot](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/availability-time-slots/time-slot-object) in response
- * represents the availability of the given list of services in a specific location, within a given range of time.
+ * represents the availability of the given sequence of services in a specific order, location, and within a given range of time.
  *
  * Each `TimeSlot`.`NestedTimeSlot` represents a single service from the given list. The order of the `NestedTimeSlots` is the same as the order
  * of the given services in request.
- *
- * The first `NestedTimeSlot` has `localStartDate` within the given `fromLocalDate` and `toLocalDate` - exclusive,
+ * The first `NestedTimeSlot` has `localStartDate` within the given `fromLocalDate` and `toLocalDate` exclusive,
  * and each following `NestedTimeSlot` has a `localStartDate` that equals to the previous `NestedTimeSlot`'s `localEndDate`.
  *
+ * By default,
+ * the response contains at most 1000 results.
+ * If there are more than 1000 results, we return a `cursorPagingMetadata` with
+ * a cursor for the next page of results, regardless of whether a `cursorPaging`
+ * was provided in request.
+ *
  * > __Notes:__
  * >  + All nested time slots share the same location.
  * >  + You can pass up to 8 services in request.
  *
  * ### AvailableResources in response:
+ * The `TimeSlot`.`NestedTimeSlot`'s `AvailableResources` contains information about the resources that are available to provide the service
+ * within the `NestedTimeSlot` range of time. Each `AvailableResources` contains information about available resources of the same type.
+ *
  * <blockquote class="important">
  * <p><strong>Important:</strong><br/>
  * By default,
- * if you don't specify `service`.`includeResourceTypeIds` or `service`.`resourceIds` filters in request,
- * we return `TimeSlot`.`NestedTimeSlot`'s with an empty `AvailableResources`.
+ * if you don't specify <code class="grey-background">service</code>.<code class="grey-background">includeResourceTypeIds</code>
+ * or  <code class="grey-background">service</code>.<code class="grey-background">resourceIds</code> filters in request,
+ * we return TimeSlots with <code class="grey-background">NestedTimeSlot</code>s with an empty <code class="grey-background">AvailableResources</code>.
+ * <br/><strong>Note:</strong><br/> Not specifying resources filters can be handy in case you want to avoid large response in flows that only
+ * interested of whether the time slots are available. [Finding the next available slot within the next 3 months](https://bo.wix.com/wix-docs/rest/all-apis/service-availability/multi-service-availability-time-slots/sample-flows?localViewerId=inbari#all-apis_service-availability_multi-service-availability-time-slots_sample-flows_find-the-first-date-within-the-next-3-months-that-all-selected-services-are-available-for)
+ * is an example for such flow.
  * </p>
  * </blockquote>
  *
+ *
  * If you wish to get a list of available resources for a `TimeSlot`.`NestedTimeSlot` you should either:
  * + provide `service`.`resourceIds` in request.
  * + provide `service`.`includeResourceTypeIds` in request.
  *
- * > __Notes:__
- * >
- * > + In both cases the returned `TimeSlot`.`NestedTimeSlot`'s contains  __up__ to 10 `AvailableResources` that match the provided filters.
- * > Each `AvailableResources` contains __up__ to 10 available `resources` of the same type that match the provided filters.
- * >
- * > + If an `AvailableResources` has more available resources which are not listed within it,
- * > we return `AvailableResources`.`hasMoreAvailableResources` as true.
- * > + If you wish to get the full available resources list for all `NestedTimeSlot` of a specific `TimeSlot`,
- * > you can call [GetMultiServiceAvailabilityTimeSlot](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/multi-service-availability-time-slots/get-multi-service-availability-time-slot).
- *
+ * __Notes:__
+ * + In both cases the returned `TimeSlot`.`NestedTimeSlot` contains  __up__ to 10 `AvailableResources` that match the provided filters. Each `AvailableResources` contains __up__ to 10 available `resources` of the same type that match the provided filters.
+ * + If an `AvailableResources` has more available resources which are not listed within it, we return `AvailableResources`.`hasMoreAvailableResources` as true.
+ * + If you wish to get the full available resources list for all `NestedTimeSlot` of a specific `TimeSlot`, you should call [GetMultiServiceAvailabilityTimeSlot](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/multi-service-availability-time-slots/get-multi-service-availability-time-slot).
  *
- * ### Availability VS Bookability:
- * An available time slot is not necessarily bookable.
  *
+ * ### Availability VS Bookability
+ * An `available` time slot is not necessarily `bookable`.
  * The `bookable` field of a `TimeSlot` indicates whether the customer can book all of the of the services within the given time slot,
  * at a specific period of time.
  * Read more about [Availability VS Bookability](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/multi-service-availability-time-slots/introduction#all-apis_wix-service-availability_multi-service-availability-time-slots_introduction_availability-vs-bookability).
  *
  * By default,
- * + The response does not contains unavailable `TimeSlot`'s.
- * For example,
- * if there are no available resources to provide the service from `2024-01-30T14:30:00` to `2024-01-30T15:30:00`,
- * we don't return `TimeSlot`'s with `localStartDate` within this range.
- * + The response contains both `bookable` and `un-bookable` `TimeSlot`'s.
- * For example,
- * if one of the services has a booking policy which enforces booking the service up to 10 minutes before the session starts,
- * we return `TimeSlot`'s with the violating `localStartDate` with `bookable` as false.
- * If you want to list only __bookable__ `TimeSlots` you should pass `bookable` as true.
- * + If booking one of the `NestedTimeSlot`'s violates one of the corresponding service's booking policies,
- * the `TimeSlot` returns with `bookable` as false. There is no indication which service's policy was violated.
+ * + The response does not contains `unavailable` TimeSlots.For example, if there are no available resources to provide one of the services from `2024-01-30T14:30:00` to `2024-01-30T15:30:00`, we don't return TimeSlots with `NestedTimeSlot`.`localStartDate` within this range for this service.
+ * + The response contains both `bookable` and `un-bookable` TimeSlots.For example, if one of the services has a booking policy which enforces booking the service up to 10 minutes before the session starts, we return TimeSlots with the violating `NestedTimeSlot`.`localStartDate`, with `bookable` as `false`. If you want to list only __bookable__ TimeSlots you should pass `bookable` as `true`.
+ * + If booking one of the `NestedTimeSlot`s violates one of the corresponding service's booking policies, the `TimeSlot` returns with `bookable` as false. There is no indication which service's policy was violated.
  *
  * <blockquote class="important">
- * <p><strong>Important:</strong><br/>
+ * <p><strong>Important:</strong>
  * Because of DST, there are edge cases where certain times either do not exist or exist twice for a local time zone.
- * Read about [DST Handling](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/multi-service-availability-time-slots/introduction#all-apis_wix-service-availability_multi-service-availability-time-slots_introduction_daylight-saving-time-dst-handling)
- * </p>
+ * Read more about <a href="https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/multi-service-availability-time-slots/introduction#all-apis_wix-service-availability_multi-service-availability-time-slots_introduction_daylight-saving-time-dst-handling">DST Handling</a></p>
  * </blockquote>
  *
- *
- * ### Pagination:
- * You can specify how many `TimeSlot`'s will return in response by providing a `limit`
- * for the `cursorPaging` in request.
- *
- * If there are more `TimeSlot`s that match the provided filters, we return a `cursorPagingMetaData`
- * with `hasNext` = true and a `cursors`.`next` that points to the next page of results.
- * In order to retrieve the next page of results, you should only provide `cursorPaging` with a limit and the cursor
- * you got in previous call to `cursorPaging`.`cursor` in the request of the following call.
- *
- * By default,
- * the response contains at most 1000 results.
- * If there are more than 1000 results, we return a `cursorPagingMetadata` with
- * a cursor for the next page of results, regardless of whether a `cursorPaging`
- * was provided in request.
- *
- * #### ListAvailabilityTimeSlots runs with the following defaults:
- * + `cursorPaging`.`limit` is 1000.
+ * ### ListAvailabilityTimeSlots runs with the following defaults:
  * + `localStartDate` is sorted in `ASC` order.
+ * + `cursorPaging`.`limit` is `1000`.
  * @public
  * @documentationMaturity preview
  * @permissionScope Read Bookings - Public Data
@@ -941,43 +905,57 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
      * Services for which the multiService time slots are being returned for.
      * Each service contains its own resources filters within.
      *
-     * MinSize: 2.
-     * MaxSize: 8.
+     * MinSize: `2`.
+     * MaxSize: `8`.
+     *
+     * Required, unless `cursorPaging`.`cursor` is provided.
      */
     services?: Service[];
     /**
      * Lower boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T13:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
      */
     fromLocalDate?: string | null;
     /**
      * Upper boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T14:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
      */
     toLocalDate?: string | null;
     /**
      * Time zone, in IANA time zone format.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
      */
     timeZone?: string | null;
     /**
-     * Location for which the multiService time slots are being returned for.
+     * Location for which the multiService TimeSlots are being returned for.
+     *
+     * You can specify location or location type for which the TimeSlots will be returned for.
+     * If locationType is `BUSINESS`, you __must__ provide a locationId.
      *
-     * You can specify location or location type for which the time slots will be returned for.
-     * > __Note:__ Supports filtering by location type, or by locationId. Other fields like `name` are ignored.
-     * > If locationType is `BUSINESS`, you __must__ provide a locationId.
+     * <blockquote class="warning">
+     * <p><strong>warning:</strong><br/>
+     * Supports filtering by location type, or by location ID. </br>
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
+     * </blockquote>
+     *
+     * Required, unless `cursorPaging`.`cursor` is provided.
      */
     location?: Location;
     /**
-     * Whether the `TimeSlot` is bookable according all of the services booking policies.
+     * Whether the `TimeSlot` is bookable according to all of the services booking policies.
      *
-     * If booking any of the `TimeSlot`.`NestedTimeSlot`'s violates any of its services bookings policies,
+     * If booking any of the `TimeSlot`.`NestedTimeSlot`s violates any of its services bookings policies,
      * returns as `false`. Otherwise, returns as `true`.
      *
      * > __Note:__
@@ -991,7 +969,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
      * A bookable time slot must not violate any policy,
      * therefor, this filter is only relevant when `bookable` filter is false.
      *
-     * Each nested field is checked on all `NestedTimeSlot`'s. For example, if only one of the `NestedTimeSlot`'s
+     * Each nested field is checked on all `NestedTimeSlot`s. For example, if only one of the `NestedTimeSlot`'s
      * has a service with `tooEarlyToBook` same as in the request, we return the `TimeSlot` regardless of whether
      * the other `NestedTimeSlots` has the same `tooEarlyToBook` as in request.
      *
@@ -1001,7 +979,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
     bookingPolicyViolations?: BookingPolicyViolations;
     /**
      * Maximum number of slots to load for each day. For example, if `timeSlotsPerDay` is set to `3`,
-     * we return at most 3 available `TimeSlot`'s for each day within the date range specified in request.
+     * we return at most 3 available TimeSlots for each day within the date range specified in request.
      *
      * By default,
      * if `bookable` filter was not specified,
@@ -1014,8 +992,8 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
     /**
      * CursorPaging.
      *
-     * Enables you to fetch `TimeSlot`'s in smaller, more manageable chunks
-     * by setting a limit on the number of `TimeSlots` returned in response.
+     * Enables you to fetch TimeSlots in smaller, more manageable chunks
+     * by setting a limit on the number of results returned in response.
      * This is useful in order to enhance efficiency of data retrieval and reduce load on both the client and server.
      *
      * If there are more results than the specified limit, the response will contain a `cursorPagingMetaData`
@@ -1027,17 +1005,12 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
      * the `cursorPaging`.`limit`. You may pass a different `limit`.
      * No need to specify any additional parameters.
      *
-     * __TODO: This is only describes the current behavior, should be fixed__
      * <blockquote class="important">
      * <p><strong>Important:</strong><br/>
-     * If you only provide a `cursorPaging`.`cursor`,
-     * the response will contain the default size of results = 1000.
+     * If you only provide a <code class="grey-background">cursorPaging</code>. <code class="grey-background">cursor</code>,
+     * the response will contain the default size of results which is `1000`.
      * </p>
      * </blockquote>
-     *
-     * cursorPaging.limit:
-     * Default: 1000
-     * Max: 1000
      */
     cursorPaging?: CommonCursorPaging;
 }
@@ -1048,8 +1021,7 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
  *
  * <blockquote class="important">
  * <p><strong>Important:</strong><br/>
- * Currently supported only for services of type `APPOINTMENT`.
- * </p>
+ * Currently supported only for services of type <code class="grey-background">APPOINTMENT</code>.</p>
  * </blockquote>
  *
  * By default,
@@ -1065,7 +1037,12 @@ export interface ListMultiServiceAvailabilityTimeSlotsOptions {
  * + Notes:
  * + All nested time slots share the same location.
  * + You can pass up to 8 services.
- * @param services - Services for which the multiService time slots are being returned for.
+ *
+ * <blockquote class="tip">
+ * <p><strong>Tip:</strong><br/>
+ * Use this API in order to get the availability of a specific <code class="grey-background">TimeSlot</code> out of those returned from  <code class="grey-background">ListMultiServiceAvailabilityTimeSlots</code> API.</p>
+ * </blockquote>
+ * @param services - Services for which the multiService TimeSlots are being returned for.
  * Each service contains its own resources filters within.
  *
  * MinSize: 2.
@@ -1108,41 +1085,53 @@ export interface GetMultiServiceAvailabilityTimeSlotOptions {
      * The location of the time slot.
      *
      * You must provide a specific `locationType`.
-     * If locationType is `BUSINESS`, you __must__ also provide a locationId.
+     * If locationType is `BUSINESS`, you __must__ also provide a `locationId`.
      *
-     * <blockquote class="important">
-     * <p><strong>Important:</strong><br/>
-     * `name` and `formattedAddress` are ignored.
-     * </p>
+     * <blockquote class="warning">
+     * <p>Supports filtering by location type, or by location ID.
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
      * </blockquote>
      */
     location: Location;
 }
 /**
- * Retrieves a list of `TimeSlot`'s that match the provided filters.
+ * Retrieves a list of `TimeSlot`s that match the provided filters.
  *
  * <blockquote class="important">
- * <p><strong>Important:</strong><br/>
- * Currently supported only for services of type `APPOINTMENT`.
- * </p>
+ * <p><strong>Important:</strong>
+ * Currently supported only for services of type <code class="grey-background">APPOINTMENT</code>.</p>
  * </blockquote>
  *
- * The request body __must__ include one of:
- *
- * + All of the following filters:  `serviceId`, `fromLocalDate`, `toLocalDate`, and `timeZone`. You may add additional filters as you wish.
+ * The request body __must__ include either:
+ * + All of the following filters:  `serviceId`, `fromLocalDate`, `toLocalDate`, and `timeZone`.
+ * You may add additional filters as you wish.
  * + A `cursorPaging` with a valid `cursor` from previous response.
  *
+ *
  * Each [TimeSlot](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/availability-time-slots/time-slot-object) in response
  * represents the availability of the service in a specific location,
  * and has a `localStartDate` within the range of the provided `fromLocalDate` and `toLocalDate` exclusive.
+ * The `localEndDate` of a `TimeSlot` is calculated as the sum of the `TimeSlot`'s `localStartDate` and the duration of the service.
  *
+ * By default,
+ * the response contains at most 1000 results.
+ * If there are more than 1000 results, we return a `cursorPagingMetadata` with
+ * a cursor for the next page of results, regardless of whether a `cursorPaging`
+ * was provided in request.
+ *
+ * ### AvailableResources in response
+ * The `TimeSlot`'s `AvailableResources` contains information about the resources that are available to provide the service
+ * within the time slot. Each `AvailableResources` contains information about available resources of the same type.
  *
- * ### AvailableResources in response:
  * <blockquote class="important">
  * <p><strong>Important:</strong><br/>
  * By default,
- * if you don't specify `includeResourceTypeIds` or `resourceIds` filters in request,
- * we return `TimeSlot`'s with an empty `AvailableResources`.
+ * if you don't specify <code class="grey-background">includeResourceTypeIds</code>
+ * or <code class="grey-background">resourceIds</code> filters in request,
+ * we return TimeSlots with an empty <code class="grey-background">AvailableResources</code>.
+ * <br/><strong>Note:</strong><br/> Not specifying resources filters can be handy in case you want to avoid large response in flows that only
+ * interested of whether the time slots are available. [Finding the next available slot within the next 3 months](https://bo.wix.com/wix-docs/rest/all-apis/service-availability/availability-time-slots/sample-flows?localViewerId=inbari#all-apis_service-availability_availability-time-slots_sample-flows_find-the-first-date-within-the-next-3-months-that-the-selected-service-is-available-for)
+ * is an example for such flow.
  * </p>
  * </blockquote>
  *
@@ -1150,61 +1139,43 @@ export interface GetMultiServiceAvailabilityTimeSlotOptions {
  * + provide `resourceIds` in request.
  * + provide `includeResourceTypeIds` in request.
  *
- * > __Notes:__
- * >
- * > + In both cases the returned `TimeSlot`'s contains  __up__ to 10 `AvailableResources` that match the provided filters.
- * > Each `AvailableResources` contains __up__ to 10 available `resources` of the same type that match the provided filters.
- * >
- * > + If an `AvailableResources` has more available resources which are not listed within it,
- * > we return `AvailableResources`.`hasMoreAvailableResources` as true.
- * > + If you wish to get the full available resources list for a specific `TimeSlot`,
- * > you can call [GetAvailabilityTimeSlot](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/service-availability-time-slots/get-availability-time-slot).
- *
+ * __Notes:__
+ * + In both cases the returned TimeSlots contains  __up__ to 10 `AvailableResources` that match the provided filters.
+ * Each `AvailableResources` contains __up__ to 10 available `resources` of the same type that match the provided filters.
+ * + If an `AvailableResources` has more available resources which are not listed within it,
+ * we return `AvailableResources`.`hasMoreAvailableResources` as true.
+ * > __Note:__
+ * > If you wish to get the full available resources list for a specific `TimeSlot`,
+ * > you should call [GetAvailabilityTimeSlot](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/service-availability-time-slots/get-availability-time-slot).
  *
- * ### Availability VS Bookability:
- * An available time slot is not necessarily bookable.
  *
+ * ### Availability VS Bookability
+ * An `available` time slot is not necessarily `bookable`.
  * The `bookable` field of a `TimeSlot` indicates whether a customer can book the service within the given time slot,
  * at a specific period of time.
  * Read more about [Availability VS Bookability](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/service-availability-time-slots/introduction#all-apis_wix-service-availability_service-availability-time-slots_introduction_availability-vs-bookability).
  *
  * By default,
- * + The response does not contains unavailable `TimeSlot`'s.
+ * + The response does not contains `unavailable` TimeSlots.
  * For example,
  * if there are no available resources to provide the service from `2024-01-30T14:30:00` to `2024-01-30T15:30:00`,
- * we don't return `TimeSlot`'s with `localStartDate` within this range.
- * + The response contains both `bookable` and `un-bookable` `TimeSlot`'s.
+ * we don't return TimeSlots with `localStartDate` within this range.
+ * + The response contains both `bookable` and `un-bookable` TimeSlots.
  * For example,
  * if the service has a booking policy which enforces booking the service up to 10 minutes before the session starts,
- * we return `TimeSlot`'s with the violating `localStartDate` with `bookable` as false.
- * If you want to list only __bookable__ `TimeSlots` you should pass `bookable` as true.
+ * we return TimeSlots with the violating `localStartDate` with `bookable` as false.
+ * If you wish to list only available __bookable__ TimeSlots you should pass `bookable` filter as true.
  *
  * <blockquote class="important">
- * <p><strong>Important:</strong><br/>
+ * <p><strong>Important:</strong>
  * Because of DST, there are edge cases where certain times either do not exist or exist twice for a local time zone.
- * Read about [DST Handling](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/service-availability-time-slots/introduction#all-apis_wix-service-availability_service-availability-time-slots_introduction_daylight-saving-time-dst-handling)
- * </p>
+ * Read more about <a href="https://bo.wix.com/wix-docs/rest/all-apis/service-availability/availability-time-slots/introduction?localViewerId=inbari#all-apis_service-availability_availability-time-slots_introduction_daylight-saving-time-dst-handling">DST Handling</a></p>
  * </blockquote>
  *
  *
- * ### Pagination:
- * You can specify how many `TimeSlot`'s will return in response by providing a `limit`
- * for the `cursorPaging` in request.
- *
- * If there are more `TimeSlot`s that match the provided filters, we return a `cursorPagingMetaData`
- * with `hasNext` = true and a `cursors`.`next` that points to the next page of results.
- * In order to retrieve the next page of results, you should only provide `cursorPaging` with a limit and the cursor
- * you got in previous call to `cursorPaging`.`cursor` in the request of the following call.
- *
- * By default,
- * the response contains at most 1000 results.
- * If there are more than 1000 results, we return a `cursorPagingMetadata` with
- * a cursor for the next page of results, regardless of whether a `cursorPaging`
- * was provided in request.
- *
- * #### ListAvailabilityTimeSlots runs with the following defaults:
- * + `cursorPaging`.`limit` is 1000.
- * + `localStartDate` is sorted in `ASC` order.
+ * ### ListAvailabilityTimeSlots runs with the following defaults
+ * + `localStartDate` is sorted in `ASC` order
+ * + `cursorPaging`.`limit` is `1000`
  * @public
  * @documentationMaturity preview
  * @permissionScope Read Bookings - Public Data
@@ -1221,29 +1192,34 @@ export declare function listAvailabilityTimeSlots(options?: ListAvailabilityTime
 export interface ListAvailabilityTimeSlotsOptions {
     /**
      * Service ID for which the time slots are being returned for.
-     * Currently supports only services of type `Appointment`.
+     * Currently supported only for services of type `APPOINTMENT`.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
      */
     serviceId?: string | null;
     /**
      * Lower boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T13:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
      */
     fromLocalDate?: string | null;
     /**
      * Upper boundary for `localStartDate` to include in response, in ISO-8601 format.
      * For example, "2024-01-30T14:30:00".
+     *
+     * Each returned `TimeSlot` in response has a `localStartDate`
+     * within the provided `fromLocalDate` and `toLocalDate` exclusive.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
-     * > __Note:__: Each returned `TimeSlot` in response has a `localStartDate`
-     * > within the provided `fromLocalDate` and `toLocalDate` exclusive.
-     * > The `localEndDate` of the returned `TimeSlot` is the `TimeSlot`'s `localStartDate` + the service duration
      */
     toLocalDate?: string | null;
     /**
      * Time zone, in IANA time zone format.
+     *
      * Required, unless `cursorPaging`.`cursor` is provided.
      */
     timeZone?: string | null;
@@ -1252,34 +1228,37 @@ export interface ListAvailabilityTimeSlotsOptions {
      *
      * By default,
      * if no locations are provided,
-     * the response contains `TimeSlot`'s for all locations where the service is available.
+     * the response contains TimeSlots for all locations where the service is available.
      *
      * You can specify locations or location types for which the time slots will be returned for.
-     * > __Note:__ Supports filtering by location type, or by locationId. Other fields like `name` are ignored.
-     * > If locationType is `BUSINESS`, you __must__ provide a locationId.
+     * If locationType is `BUSINESS`, you __must__ provide a locationId.
+     *
+     * <blockquote class="warning">
+     * <p><strong>warning:</strong><br/>
+     * Supports filtering by location type, or by location ID. </br>
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
+     * </blockquote>
      */
     locations?: Location[];
     /**
      * Resources to include in response.
      *
      * If specified,
-     * the returned time slots will contain __up__ to 10 available resources out of the provided list.
-     * Otherwise, the returned time slots returns with an empty `AvailableResources`.
-     * > __Note:__ Not specifying `resourceIds` can be handy in case you want to avoid large response in flows that only
-     * > interested whether the time slots are available or not. [An example for such flow](https://bo.wix.com/wix-docs/rest/all-apis/wix-service-availability/service-availability-time-slots/sample-flows#all-apis_wix-service-availability_service-availability-time-slots_sample-flows_let-your-customers-to-dynamically-select-an-available-time-slot-for-any-of-your-business-services).
+     * the returned TimeSlots will contain __up__ to 10 available resources out of the provided list.
+     * Otherwise, the returned TimeSlots returns with an empty `AvailableResources`.
      */
     resourceIds?: string[];
     /**
-     * Resource type ID's to include in response, this is in addition to the requested resourceIds.
+     * Resource type ID's to include in response, this is in addition to the requested `resourceIds`.
      *
-     * If specified in request, the returned time slots will contain __up__ to 10 `AvailableResources` with `ResourceTypeId`
+     * If specified in request, the returned TimeSlots will contain __up__ to 10 `AvailableResources` with `ResourceTypeId`
      * out of those specified, each contains __up__ to 10 available resources of this type.
      */
     includeResourceTypeIds?: string[];
     /**
      * Whether the `TimeSlot` is bookable according to the service's booking policies.
      *
-     * If booking this time slot does not violates any of the service's booking policies,
+     * If booking this `TimeSlot` does not violates any of the service's booking policies,
      * returns as `true`. Otherwise, returns as `false`.
      *
      * > __Note:__
@@ -1299,7 +1278,7 @@ export interface ListAvailabilityTimeSlotsOptions {
     bookingPolicyViolations?: BookingPolicyViolations;
     /**
      * Maximum number of slots to load for each day. For example, if `timeSlotsPerDay` is set to `3`,
-     * we return at most 3 available `TimeSlot`'s for each day within the date range specified in request.
+     * we return at most 3 available TimeSlots for each day within the date range specified in request.
      *
      * By default,
      * if `bookable` filter was not specified,
@@ -1312,8 +1291,8 @@ export interface ListAvailabilityTimeSlotsOptions {
     /**
      * CursorPaging.
      *
-     * Enables you to fetch `TimeSlot`'s in smaller, more manageable chunks
-     * by setting a limit on the number of `TimeSlots` returned in response.
+     * Enables you to fetch results in smaller, more manageable chunks
+     * by setting a limit on the number of results returned in response.
      * This is useful in order to enhance efficiency of data retrieval and reduce load on both the client and server.
      *
      * If there are more results than the specified limit, the response will contain a `cursorPagingMetaData`
@@ -1321,21 +1300,16 @@ export interface ListAvailabilityTimeSlotsOptions {
      * returned cursor to the next call as `cursorPaging`.`cursor`.
      *
      * For the first call, you should only specify the `limit` for the results page.
-     * For each following call, you should only pass the previous returned cursor as `cursorPaging`.`cursor`
-     * the `cursorPaging`.`limit`. You may pass a different `limit`.
+     * For each following call, you should only pass `cursorPaging`.`cursor` with the returned cursor from previous call, and
+     * a `cursorPaging`.`limit`.
      * No need to specify any additional parameters.
      *
-     * __TODO: This is only describes the current behavior, should be fixed__
      * <blockquote class="important">
      * <p><strong>Important:</strong><br/>
-     * If you only provide a `cursorPaging`.`cursor`,
-     * the response will contain the default size of results = 1000.
+     * If you only provide a <code class="grey-background">cursorPaging</code>. <code class="grey-background">cursor</code>,
+     * the response will contain the default size of results which is `1000`.
      * </p>
      * </blockquote>
-     *
-     * cursorPaging.limit:
-     * Default: 1000
-     * Max: 1000
      */
     cursorPaging?: CommonCursorPaging;
 }
@@ -1346,8 +1320,7 @@ export interface ListAvailabilityTimeSlotsOptions {
  *
  * <blockquote class="important">
  * <p><strong>Important:</strong><br/>
- * Currently supported only for services of type `APPOINTMENT`.
- * </p>
+ * Currently supported only for services of type <code class="grey-background">APPOINTMENT</code>.</p>
  * </blockquote>
  *
  * By default,
@@ -1359,8 +1332,14 @@ export interface ListAvailabilityTimeSlotsOptions {
  * the returned `TimeSlot` will contain only `AvailableResources` with at least one available resource
  * which match the given resources filters,
  * each contains all available resources out of those requested.
+ *
+ *
+ * <blockquote class="tip">
+ * <p><strong>Tip:</strong><br/>
+ * Use this API in order to get the availability of a specific <code class="grey-background">TimeSlot</code> out of those returned from  <code class="grey-background">ListAvailabilityTimeSlots</code> API.</p>
+ * </blockquote>
  * @param serviceId - Service ID of the time slot.
- * Currently supports only services of type `Appointment`.
+ * Currently supported only for services of type `APPOINTMENT`.
  * @public
  * @documentationMaturity preview
  * @requiredField options.localEndDate
@@ -1396,12 +1375,11 @@ export interface GetAvailabilityTimeSlotOptions {
      * The location of the time slot.
      *
      * You must provide a specific `locationType`.
-     * If locationType is `BUSINESS`, you __must__ also provide a locationId.
+     * If locationType is `BUSINESS`, you __must__ also provide a `locationId`.
      *
-     * <blockquote class="important">
-     * <p><strong>Important:</strong><br/>
-     * `name` and `formattedAddress` are ignored.
-     * </p>
+     * <blockquote class="warning">
+     * <p>Supports filtering by location type, or by location ID.
+     * Other fields like <code class="grey-background">name</code> are ignored.</p>
      * </blockquote>
      */
     location: Location;
@@ -1409,16 +1387,14 @@ export interface GetAvailabilityTimeSlotOptions {
      * Resources to include in response.
      *
      * If specified,
-     * the returned time slot contain only the available resources out of provided list.
-     * Otherwise, the returned time slot returned with all possible `AvailableResources`.
-     * > __Note:__ This can be handy in case you want to avoid large response in flows that only
-     * > interested to check the availability of the time slot for specific resources.
+     * the returned `TimeSlot` contains only the available resources out of provided list.
+     * Otherwise, the returned `TimeSlot` returned with all possible `AvailableResources`.
      */
     resourceIds?: string[];
     /**
-     * Resource type ID's to include in response, this is in addition to the requested resourceIds.
+     * Resource type IDs to include in response, this is in addition to the requested `resourceIds`.
      *
-     * If specified in request, the returned time slot contain only the `AvailableResources` with `ResourceTypeId`
+     * If specified in request, the returned `TimeSlot` contains only the `AvailableResources` with `ResourceTypeId`
      * out of those specified, each contains all the available resources of this type.
      */
     includeResourceTypeIds?: string[];