diff --git a/docs/api/config/booking-cardshape.md b/docs/api/config/booking-cardshape.md
index 828b821..fc93a34 100644
--- a/docs/api/config/booking-cardshape.md
+++ b/docs/api/config/booking-cardshape.md
@@ -26,9 +26,9 @@ cardShape?: {
 
 ### Parameters
 
-In the **cardShape** object you can specify the following parameters (fields):
+In the `cardShape` object you can specify the following parameters (fields):
 
-- `category` - (optional) shows/hides a card's name
+- `category` - (optional) shows/hides a category name
 - `details` - (optional) shows/hides details
 - `preview` - (optional) shows/hides a preview image
 - `price` - (optional) shows/hides price
@@ -45,7 +45,7 @@ const defaultCardShape = {
     preview: true,
     price: true,
     review: true,
-    subtitle: false,
+    subtitle: true,
     title: true
 };
 ~~~
@@ -70,10 +70,10 @@ The snippet below demonstrates how to configure what fields to display on the le
 <iframe src="https://snippet.dhtmlx.com/6mxd7918?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
 :::info
-You can also configure the appearance of a card using the [`cardTemplate`](/api/config/booking-cardtemplate) property. If both `cardTemplate` and `cardShape` are applied, `cardTemplate` will override the `cardShape` settings. 
+You can also configure the appearance of a card using the [`cardTemplate`](api/config/booking-cardtemplate.md) property. If both `cardTemplate` and `cardShape` are applied, `cardTemplate` will override the `cardShape` settings. 
 :::
 
-**Related articles:** 
+**Related articles**: 
 
-- [Defining the structure of cards](/guides/configuration/#defining-the-structure-of-cards)
-- [`cardTemplate`](/api/config/booking-cardtemplate)
\ No newline at end of file
+- [Defining the structure of cards](guides/configuration.md#define-the-structure-of-cards)
+- [`cardTemplate`](api/config/booking-cardtemplate.md)
\ No newline at end of file
diff --git a/docs/api/config/booking-cardtemplate.md b/docs/api/config/booking-cardtemplate.md
index 69c33e9..ec56943 100644
--- a/docs/api/config/booking-cardtemplate.md
+++ b/docs/api/config/booking-cardtemplate.md
@@ -13,7 +13,7 @@ description: You can learn about the cardTemplate config in the documentation of
 The property specifies the HTML structure and layout of each card's block (the left side of each card). It means you can manage which fields are displayed, how they are arranged, and how they look.
 
 :::info
-You can also specify which fields to display using the [`cardShape`](/api/config/booking-cardshape) property
+You can also specify which fields to display using the [`cardShape`](api/config/booking-cardshape.md) property
 :::
 
 ### Usage
@@ -24,11 +24,11 @@ cardTemplate?: ({item: obj}) => string;
 
 ### Parameters
 
-`cardTemplate` expects a function that takes a `card` object as input and returns a string of HTML that defines how the card should look.
+`cardTemplate` expects a function that takes an `item` (card) object as input and returns a string of HTML that defines how the card should look.
 
 ### Example
 
-In the example below we create a function that takes the `card` object and returns HTML for a card that includes a preview image (card.preview), category (card.category), title (card.title), and price (card.price). You need to create your own HTML template to be applied to a card and import the **template** helper. Then pass the function into the Booking configuration by assigning the function to the `cardTemplate` property.  
+In the example below we create a function that takes the `item` (card) object and returns HTML for a card that includes a preview image (item.preview), category (item.category), title (item.title), and price (item.price). You need to create your own HTML template to be applied to a card and import the `template` helper. Then pass the function into the Booking configuration by assigning the function to the `cardTemplate` property.  
 
 ~~~html {}
 <style>
@@ -51,21 +51,21 @@ In the example below we create a function that takes the `card` object and retur
 <script>
     const { Booking, template } = booking; //import template helper
 
-    function cardPreviewTemplate({ card }) {
+    function cardPreviewTemplate({ item }) {
         return `
             <div class="custom-preview" data-action="preview-click">
                 <div class="preview-left">
                     <div
-                        style="background-image: url(${card.preview})"
+                        style="background-image: url(${item.preview})"
                         class="card-photo"
                     ></div>
                     <!-- <div class="card-photo-empty" /> -->
                     </div>
 
                     <div class="preview-right">
-                    <div class="category">${card.category}</div>
-                    <div class="title">${card.title}</div>
-                    <div class="price">${card.price}</div>
+                    <div class="category">${item.category}</div>
+                    <div class="title">${item.title}</div>
+                    <div class="price">${item.price}</div>
                 </div>
             </div>
             `;
@@ -73,7 +73,7 @@ In the example below we create a function that takes the `card` object and retur
 
     const widget = new Booking("#root", {
 	    data,
-	    cardTemplate: template(card => cardPreviewTemplate(card)), // pass the function to Booking configuration
+	    cardTemplate: template(item => cardPreviewTemplate(item)), // pass the function to Booking configuration
     });
     // other parameters
 </script>
@@ -84,8 +84,7 @@ The snippet below demonstrates how to apply a template to the left block of a ca
 
 <iframe src="https://snippet.dhtmlx.com/k2v01vng" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
-**Related articles:** 
-
-- [Defining the structure of cards](/guides/configuration/#defining-the-structure-of-cards)
-- [`cardShape`](/api/config/booking-cardshape)
+**Related articles**:
 
+- [Defining the structure of cards](guides/configuration.md#define-the-structure-of-cards)
+- [`cardShape`](api/config/booking-cardshape.md)
diff --git a/docs/api/config/booking-data.md b/docs/api/config/booking-data.md
index bcb65da..7ef2526 100644
--- a/docs/api/config/booking-data.md
+++ b/docs/api/config/booking-data.md
@@ -26,7 +26,7 @@ data: [
             stars: number,
             count: number
         },
-        slots: [
+        slots?: [
             {
                 from: number | string, // hours from 0 to 24
                 to: number | string, // hours from 0 to 24
@@ -36,12 +36,7 @@ data: [
                 dates?: array, // exact dates for which rule can be applied, timestamps
             }
         ],
-        availableSlots?: [
-            {
-                id: string|number,
-                time:[number, number] //timestamp, length in minutes
-            },
-        ],
+        availableSlots?: [number, number][], // each slot: [timestamp, slot duration in minutes]
         usedSlots?: number[], //timestamps
         slotSize?: number, //minutes
         slotGap?: number //minutes
@@ -63,13 +58,13 @@ For each card object you can specify the following parameters:
 - `review` - (optional) rating information that includes the following parameters:  
   - `stars` - (optional) the number of rating stars (out of five)  
   - `count` - (optional) the number of reviews
-- `slots` - (required) an array of objects with the following parameters for each slot object:
+- `slots` - (optional) an array of objects that defines slot rules (either `slots` or `availableSlots` should be provided to display bookable time); each slot object has the following parameters:
   - `from` - (required) a slot start time in hours from 0 to 24
   - `to` - (required) a slot end time in hours from 0 to 24
   - `size` - (optional) the duration of one slot in minutes
   - `gap` - (optional) the gap between slots in minutes; 0 is set by default
-  - `days` - (optional) days of the week when a slot is available for booking; possible values: from 0 to 6 where 0 is Sunday and 6 is Saturday; if no days are specified, all days are applied by default; if days are specified, the slot parameters (**to**, **from**, **size**, **gap**) defined for these days will be applied
-  - `dates` - (optional) an array of timestamps in milliseconds which are exact dates when a slot is available; the slot parameters (**to**, **from**, **size**, **gap**) for these specified dates will be applied (timestamps are in a local timezone)
+  - `days` - (optional) days of the week when a slot is available for booking; possible values: from 0 to 6 where 0 is Sunday and 6 is Saturday; if no days are specified, all days are applied by default; if days are specified, the slot parameters (`to`, `from`, `size`, `gap`) defined for these days will be applied
+  - `dates` - (optional) an array of timestamps in milliseconds which are exact dates when a slot is available; the slot parameters (`to`, `from`, `size`, `gap`) for these specified dates will be applied (timestamps are in a local timezone)
 
 :::note
 Slot parameters specified for days will override common parameters defined for all days.
@@ -77,9 +72,7 @@ Slot parameters specified for dates will override parameters defined for specifi
 If several slots objects are created for the same day, make sure that slots time ranges (from and to) with **different** size and gap do not overlap, otherwise all slots data for these days will not be applied.
 :::
 
-- `availableSlots` - (optional) an array of timestamps of available slots in milliseconds; if available slots are specified here, all slots from the `slots` array are ignored (i.e., become unavailable); each object in the array has the next parameters:
-  - `id` - (required) the id of a slot
-  - `time` - (required) an array that includes timestamp and slot duration in minutes (timestamps are in a local timezone)
+- `availableSlots` - (optional) an array of available slots; each slot is an array `[timestamp, duration]` where the timestamp is in milliseconds (in a local timezone) and the duration is the slot length in minutes; if available slots are specified here, all slots from the `slots` array are ignored (i.e., become unavailable)
 - `usedSlots` - (optional) an array of timestamps of booked slots in milliseconds (timestamps are in a local timezone)
 - `slotSize` - (optional) the duration of a slot in minutes; the value will be applied to all slots of this card if other value is not set inside the `slots` object; *60* minutes is set by default
 - `slotGap` - (optional) the gap between slots in minutes that is set for all slots in the current card; this value is applied if any other value is not specified inside the `slots` object; 0 is set by default
@@ -98,7 +91,7 @@ const data = [
         preview: "https://snippet.dhtmlx.com/codebase/data/booking/01/img/01.jpg",
         price: "37 $",
         review: {
-            star: 1,
+            stars: 1,
             count: 40
         },
         slots: [
@@ -137,4 +130,4 @@ new booking.Booking("#root", {
 });
 ~~~
 
-**Related articles:** [Defining slot rules](/guides/configuration#defining-slot-rules)
+**Related articles**: [Defining slot rules](guides/configuration.md#define-slot-rules)
diff --git a/docs/api/config/booking-end.md b/docs/api/config/booking-end.md
index a87e521..35002ab 100644
--- a/docs/api/config/booking-end.md
+++ b/docs/api/config/booking-end.md
@@ -30,6 +30,6 @@ new booking.Booking("#root", {
 });
 ~~~
 
-The snippet below shows how to set the [start](/api/config/booking-start) and end dates:
+The snippet below shows how to set the [start](api/config/booking-start.md) and end dates:
 
 <iframe src="https://snippet.dhtmlx.com/cc28whe7?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
\ No newline at end of file
diff --git a/docs/api/config/booking-filtershape.md b/docs/api/config/booking-filtershape.md
index c88fdf1..b207dd6 100644
--- a/docs/api/config/booking-filtershape.md
+++ b/docs/api/config/booking-filtershape.md
@@ -31,17 +31,17 @@ filterShape: {
 
 ### Parameters
 
-- `text` - (optional) if **true**, the text input field is displayed (default); if **false**, the text field is hidden
+- `text` - (optional) if `true`, the text input field is displayed (default); if `false`, the text field is hidden
   - `id` - (required) the id of a card
-  - `suggest` - (required) if **true**, the auto-complete is enabled and the values (from the [`data`](/api/config/booking-data) object) that match a user's input text will be displayed
+  - `suggest` - (optional) if `true`, the auto-complete is enabled and the values (from the [`data`](api/config/booking-data.md) object) that match a user's input text will be displayed
   - `label` - (optional) the label for the property from the `data` object. See [Default config](#default-config) below.
-- `date` - (optional) shows/hides the date field; **true** is set by default (the field is shown)
-- `time` - (optional) shows/hides the time field. If set to **true**, it takes an array of objects with default time options for a slot. For each object you can specify the following parameters:
+- `date` - (optional) shows/hides the date field; `true` is set by default (the field is shown)
+- `time` - (optional) shows/hides the time field. If set to `true`, it takes an array of objects with default time options for a slot. For each object you can specify the following parameters:
   - `from` - (required) the start time for a slot; it can be a number from 0 to 24 that specifies the time in hours (e.g., 9 means 9:00, 8.5 means 8:30) or a string in the format "h:m" (for example, "8:30")
   - `to` - (required) the end time for a slot; it can be a number from 0 to 24 that specifies the time in hours (e.g., 9 means 9:00, 8.5 means 8:30) or a string in the format "h:m" (for example, "8:30")
   - `label` - (optional) placeholder for the time field
 If the `time` parameters are not set, the default values are applied: see [Default config](#default-config) below.
-- `autoApply` - (optional) if **true**, the search criteria will be automatically applied (no need to initiate the search by clicking the button); **false** is set by default
+- `autoApply` - (optional) if `true`, the search criteria will be automatically applied (no need to initiate the search by clicking the button); `false` is set by default
 
 ### Default config
 
diff --git a/docs/api/config/booking-formshape.md b/docs/api/config/booking-formshape.md
index 15e45ac..bfe9df7 100644
--- a/docs/api/config/booking-formshape.md
+++ b/docs/api/config/booking-formshape.md
@@ -13,22 +13,26 @@ description: You can learn about the formShape config in the documentation of th
 ### Usage
 
 ~~~jsx {}
-formShape: {
+formShape: [{
     comp: "text" | "textarea",
     key: string,
     label?: string,
-    required?: boolean
-};
+    required?: boolean,
+    validation?: (value: any) => boolean,
+    errorMessage?: string
+}];
 ~~~
 
 ### Parameters
 
 For each field you can specify the following parameters:
 
-- `comp` - (required) the field type (**text** or **textarea**)
+- `comp` - (required) the field type (`text` or `textarea`)
 - `key` - (required) the id of a field
 - `label` - (optional) the field label
-- `required` - (optional) if the value is set to **true**, the field should not be empty and it's required to submit the booking form; if **false**, the field can be empty
+- `required` - (optional) if the value is set to `true`, the field should not be empty and it's required to submit the booking form; if `false`, the field can be empty
+- `validation` - (optional) a function that takes the field value and returns a boolean; the field is considered valid when the function returns `true`
+- `errorMessage` - (optional) the message shown when the value does not pass validation
 
 ### Default config
 
@@ -68,17 +72,17 @@ const defaultFormShape = [
 ~~~jsx {1-17,21}
 const formShape = [
     {
-        type: "text",
+        comp: "text",
         key: "name",
         label: "Name"
     },
     {
-        type: "text",
+        comp: "text",
         key: "contact",
         label: "Mobile"
     },
     {
-        type: "textarea",
+        comp: "textarea",
         key: "description",
         label: "Details"
     },
diff --git a/docs/api/config/booking-infoshape.md b/docs/api/config/booking-infoshape.md
index 96a2def..98b268c 100644
--- a/docs/api/config/booking-infoshape.md
+++ b/docs/api/config/booking-infoshape.md
@@ -64,10 +64,10 @@ The snippet below shows how to configure what to display on the left side of the
 <iframe src="https://snippet.dhtmlx.com/pd6wp1xc?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
 :::info
-You can also control which fields to display in the information block of the Booking dialog using the [`infoTemplate`](/api/config/booking-infotemplate) property. But if both properties are applied, `infoTemplate` will override the `infoShape` settings.
+You can also control which fields to display in the information block of the Booking dialog using the [`infoTemplate`](api/config/booking-infotemplate.md) property. But if both properties are applied, `infoTemplate` will override the `infoShape` settings.
 :::
 
-**Related articles:** 
+**Related articles**: 
 
-- [Configuring the Booking dialog](/guides/configuration/#configuring-the-booking-dialog)
-- [`infoTemplate`](/api/config/booking-infotemplate)
\ No newline at end of file
+- [Configuring the Booking dialog](guides/configuration.md#configure-the-booking-dialog)
+- [`infoTemplate`](api/config/booking-infotemplate.md)
\ No newline at end of file
diff --git a/docs/api/config/booking-infotemplate.md b/docs/api/config/booking-infotemplate.md
index 19da9fc..43d27a8 100644
--- a/docs/api/config/booking-infotemplate.md
+++ b/docs/api/config/booking-infotemplate.md
@@ -23,7 +23,7 @@ infoTemplate?: ({item: obj, slot: number}) => string;
 
 ### Example
 
-In the example below, we define the `cardInfoTemplate` function that will generate the custom HTML for the information block. This function will receive the `item` (card object) and `slot` (slot timestamp) as input parameters. The function returns div containers representing the information block for a selected booking item, including an image, category, title, and formatted date. You should also import the **template** helper and assign your custom function to `infoTemplate`.
+In the example below, we define the `cardInfoTemplate` function that will generate the custom HTML for the information block. This function will receive the `item` (card object) and `slot` (slot timestamp) as input parameters. The function returns div containers representing the information block for a selected booking item, including an image, category, title, and formatted date. You should also import the `template` helper and assign your custom function to `infoTemplate`.
 
 ~~~html
 <style>
@@ -83,10 +83,10 @@ The snippet below shows how to apply a template to the information block of the
 <iframe src="https://snippet.dhtmlx.com/byb94ipu?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
 :::info
-You can also control which fields to display in the information block of the Booking dialog using the [`infoShape`](/api/config/booking-infoshape) property. But if both properties are applied, `infoTemplate` will override the `infoShape` settings.
+You can also control which fields to display in the information block of the Booking dialog using the [`infoShape`](api/config/booking-infoshape.md) property. But if both properties are applied, `infoTemplate` will override the `infoShape` settings.
 :::
 
-**Related articles:** 
+**Related articles**: 
 
-- [Configuring the Booking dialog](/guides/configuration/#configuring-the-booking-dialog)
-- [`infoShape`](/api/config/booking-infoshape)
\ No newline at end of file
+- [Configuring the Booking dialog](guides/configuration.md#configure-the-booking-dialog)
+- [`infoShape`](api/config/booking-infoshape.md)
\ No newline at end of file
diff --git a/docs/api/config/booking-locale.md b/docs/api/config/booking-locale.md
index 467e8b6..e201272 100644
--- a/docs/api/config/booking-locale.md
+++ b/docs/api/config/booking-locale.md
@@ -18,22 +18,22 @@ locale?: object;
 
 ### Default config
 
-By default, Booking uses the [English](/guides/localization/#default-locale) locale. You can set it to the custom locale as well.
+By default, Booking uses the [English](guides/localization.md#default-locale) locale. You can set it to the custom locale as well.
 
 :::tip
-To change the current locale dynamically, you can use the [`setLocale()`](/api/methods/booking-setlocale-method) method
+To change the current locale dynamically, you can use the [`setLocale()`](api/methods/booking-setlocale-method.md) method
 :::
 
 ### Example
 
 ~~~jsx
 const { data } = getData();
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
-    locale: de
+    locale: booking.locales.de
 });
 ~~~
 
 **Related articles**:
-- [setLocale()](/api/methods/booking-setlocale-method)
-- [Localization](/guides/localization)
+- [setLocale()](api/methods/booking-setlocale-method.md)
+- [Localization](guides/localization.md)
diff --git a/docs/api/config/booking-slotgap.md b/docs/api/config/booking-slotgap.md
index 7fd1ae4..a739192 100644
--- a/docs/api/config/booking-slotgap.md
+++ b/docs/api/config/booking-slotgap.md
@@ -11,7 +11,7 @@ description: You can learn about the slotGap in the documentation of the DHTMLX
 @short: Optional. Defines a gap between booking slots for all cards
 
 :::note
-The value will be applied in case the gap value is not set for the `gap` or `slotGap` parameter inside the [`data`](/api/config/booking-data) property.
+The value will be applied in case the gap value is not set for the `gap` or `slotGap` parameter inside the [`data`](api/config/booking-data.md) property.
 :::
 
 ### Usage
@@ -35,6 +35,6 @@ new booking.Booking("#root", {
 });
 ~~~
 
-The snippet below shows how to set [duration](/api/config/booking-slotsize) and gap for all slots:
+The snippet below shows how to set [duration](api/config/booking-slotsize.md) and gap for all slots:
 
 <iframe src="https://snippet.dhtmlx.com/pw8xsl1p?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
diff --git a/docs/api/config/booking-slotsize.md b/docs/api/config/booking-slotsize.md
index 87c3e92..bbf30c5 100644
--- a/docs/api/config/booking-slotsize.md
+++ b/docs/api/config/booking-slotsize.md
@@ -11,7 +11,7 @@ description: You can learn about the slotSize in the documentation of the DHTMLX
 @short: Optional. Defines the duration of a booking slot for all cards
 
 :::note
-This value will be applied in case the size value is not set for the `size` or `slotSize` parameter inside the [`data`](/api/config/booking-data) property.
+This value will be applied in case the size value is not set for the `size` or `slotSize` parameter inside the [`data`](api/config/booking-data.md) property.
 :::
 
 ### Usage
@@ -35,6 +35,6 @@ new booking.Booking("#root", {
 });
 ~~~
 
-The snippet below shows how to set duration and [gap](/api/config/booking-slotgap) for all slots:
+The snippet below shows how to set duration and [gap](api/config/booking-slotgap.md) for all slots:
 
 <iframe src="https://snippet.dhtmlx.com/pw8xsl1p?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
diff --git a/docs/api/config/booking-start.md b/docs/api/config/booking-start.md
index 5a6c5f6..9aa0254 100644
--- a/docs/api/config/booking-start.md
+++ b/docs/api/config/booking-start.md
@@ -30,6 +30,6 @@ new booking.Booking("#root", {
 });
 ~~~
 
-The snippet below shows how to set the start and [end](/api/config/booking-end) dates:
+The snippet below shows how to set the start and [end](api/config/booking-end.md) dates:
 
 <iframe src="https://snippet.dhtmlx.com/cc28whe7?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
diff --git a/docs/api/events/booking-confirmslot-event.md b/docs/api/events/booking-confirmslot-event.md
index 4d3acc2..9e1c109 100644
--- a/docs/api/events/booking-confirmslot-event.md
+++ b/docs/api/events/booking-confirmslot-event.md
@@ -19,7 +19,7 @@ description: You can learn about the confirm-slot event in the documentation of
         time: [ number, number ]
     },
     data:{
-        [key]: any
+        [key]: string
     },
     confirm:{
         promise:Promise,
@@ -31,13 +31,13 @@ description: You can learn about the confirm-slot event in the documentation of
 
 ### Parameters
 
-The callback of the **confirm-slot** event can take an object with the following parameters:
+The callback of the `confirm-slot` event can take an object with the following parameters:
 
 - `slot` - (required) an object with the next slot parameters:
     - `id` - (required) the ID of a card for which the booking of a slot is confirmed
     - `time` - (required) an array with the slot start time in milliseconds and the slot duration in minutes (timestamps are in a local timezone)
-- `data` - (required) an abject with the booking screen fields with the following parameters for each field:
-    - `key` - (required) the form field ID (from the [`formShape`](/api/config/booking-formshape)). By default, three fields are added: *name*, *email*, *description*
+- `data` - (required) an object with the booking screen fields with the following parameters for each field:
+    - `key` - (required) the form field ID (from the [`formShape`](api/config/booking-formshape.md)). By default, three fields are added: *name*, *email*, *description*
 - `confirm` - (required) an object with the next parameters:
     - `promise` -  (required) a promise that represents the confirmation status. This is a JavaScript Promise object that represents the asynchronous operation of confirming the slot booking. The promise will be resolved or rejected based on the outcome of the booking process. You can attach `.then` and `.catch` handlers to this promise to handle the success or failure of the booking.
     - `done` - (required) a callback function that should be called when booking is successfully confirmed. Calling this function will resolve the promise, indicating that the booking was successful. You can call this function after receiving a positive response from the server.
@@ -47,14 +47,14 @@ The callback of the **confirm-slot** event can take an object with the following
 
 ~~~jsx {7-10}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // other configuration parameters
 });
 
-booking.api.on("confirm-slot", (obj) => {
-    console.log("The slot id for which booking was confirmed:", obj.id);
+widget.api.on("confirm-slot", (obj) => {
+    console.log("The slot id for which booking was confirmed:", obj.slot.id);
 });
 ~~~
 
-**Related articles:** [`setConfirmHandler`](/api/methods/booking-setconfirmhandler-method) method
+**Related articles**: [`setConfirmHandler`](api/methods/booking-setconfirmhandler-method.md) method
diff --git a/docs/api/events/booking-filterdata-event.md b/docs/api/events/booking-filterdata-event.md
index 60ab7d2..aefeaf0 100644
--- a/docs/api/events/booking-filterdata-event.md
+++ b/docs/api/events/booking-filterdata-event.md
@@ -28,7 +28,7 @@ description: You can learn about the filter-data event in the documentation of t
 
 ### Parameters
 
-The callback of the **filter-data** event can take an object with the following parameters:
+The callback of the `filter-data` event can take an object with the following parameters:
 
 - `text` - (required) the text in the search field
 - `date` - (required) Date object with the start and end date for a slot: 
@@ -40,15 +40,15 @@ The callback of the **filter-data** event can take an object with the following
 
 ### Example
 
-The example below demonstrates how to apply filter at the initialization using the [`api.exec()`](/api/internal/booking-exec) method:
+The example below demonstrates how to apply filter at the initialization using the [`api.exec()`](api/internal/booking-exec.md) method:
 
 ~~~jsx {6-18}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // other configuration parameters
 });
-booking.api.exec("filter-data", {
+widget.api.exec("filter-data", {
     text: "Allergist",
     date: {
         start: new Date,
diff --git a/docs/api/events/booking-selectitem-event.md b/docs/api/events/booking-selectitem-event.md
index cfa9239..6ab0c40 100644
--- a/docs/api/events/booking-selectitem-event.md
+++ b/docs/api/events/booking-selectitem-event.md
@@ -20,7 +20,7 @@ description: You can learn about the select-item event in the documentation of t
 
 ### Parameters
 
-The callback of the **select-item** event can take an object with the following parameters:
+The callback of the `select-item` event can take an object with the following parameters:
 
 - `id` - (required) the id of an item
 
@@ -28,13 +28,13 @@ The callback of the **select-item** event can take an object with the following
 
 ~~~jsx {7-10}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data, 
     // other configuration parameters
 });
 
 // output the id of the selected item
-booking.api.on("select-item", (ev) => {
+widget.api.on("select-item", (ev) => {
     console.log(ev.id);
 });
 ~~~
diff --git a/docs/api/events/booking-selectitemdate-event.md b/docs/api/events/booking-selectitemdate-event.md
index ea40d91..4b9e694 100644
--- a/docs/api/events/booking-selectitemdate-event.md
+++ b/docs/api/events/booking-selectitemdate-event.md
@@ -8,7 +8,7 @@ description: You can learn about the select-item-date event in the documentation
 
 ### Description
 
-@short: Fires when an item is selected
+@short: Fires when a date is selected for an item
 
 ### Usage
 
@@ -21,7 +21,7 @@ description: You can learn about the select-item-date event in the documentation
 
 ### Parameters
 
-The callback of the **select-item-date** event can take an object with the following parameters:
+The callback of the `select-item-date` event can take an object with the following parameters:
 
 - `id` - (required) the id of an item
 - `date` - (required) the date (in milliseconds) that was set for the selected item
@@ -30,13 +30,13 @@ The callback of the **select-item-date** event can take an object with the follo
 
 ~~~jsx {7-10}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // other configuration parameters
 });
 
 // output the date  
-booking.api.on("select-item-date", (ev) => {
+widget.api.on("select-item-date", (ev) => {
     console.log(ev.date);
 });
 ~~~
diff --git a/docs/api/events/booking-selectslot-event.md b/docs/api/events/booking-selectslot-event.md
index beec2bc..5acf0c2 100644
--- a/docs/api/events/booking-selectslot-event.md
+++ b/docs/api/events/booking-selectslot-event.md
@@ -21,7 +21,7 @@ description: You can learn about the select-slot event in the documentation of t
 
 ### Parameters
 
-The callback of the **select-slot** event can take an object with the following parameters:
+The callback of the `select-slot` event can take an object with the following parameters:
 
 - `id` - (required) the ID of a card the selected slot belongs to
 - `time` - (required) an array with the slot start time in milliseconds and the slot duration in minutes (timestamps are in a local timezone)
@@ -30,13 +30,13 @@ The callback of the **select-slot** event can take an object with the following
 
 ~~~jsx {7-10}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // other configuration parameters
 });
 
 // output the id of the selected slot
-booking.api.on("select-slot", (obj) => {
+widget.api.on("select-slot", (obj) => {
     console.log(obj.id);
 });
 ~~~
diff --git a/docs/api/internal/booking-detach.md b/docs/api/internal/booking-detach.md
index 3ab0d37..612fc14 100644
--- a/docs/api/internal/booking-detach.md
+++ b/docs/api/internal/booking-detach.md
@@ -22,17 +22,17 @@ api.detach(tag: number | string ): void;
 
 ## Example
 
-In the example below we add an object with the **tag** property to the [`api.on()`](/api/internal/booking-on) handler, and then we use the `api.detach()` method to stop logging the [`open-filter`](/api/events/booking-selectslot-event) event.
+In the example below we add an object with the `tag` property to the [`api.on()`](api/internal/booking-on.md) handler, and then we use the `api.detach()` method to stop logging the [`select-slot`](api/events/booking-selectslot-event.md) event.
 
 ~~~jsx {6-20}
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     //other configuration parameters
 });
 
 // add handler
-if (booking.api) {
-    booking.api.on(
+if (widget.api) {
+    widget.api.on(
         "select-slot",
         ({ id }) => {
             console.log("Selected: " + id);
@@ -43,7 +43,7 @@ if (booking.api) {
 
 // detach handler
 function stop() {
-    booking.api.detach("track");
+    widget.api.detach("track");
 }
 
 const button = document.createElement("button");
diff --git a/docs/api/internal/booking-exec.md b/docs/api/internal/booking-exec.md
index 5d3d916..c150ffd 100644
--- a/docs/api/internal/booking-exec.md
+++ b/docs/api/internal/booking-exec.md
@@ -10,13 +10,15 @@ description: You can learn about the exec method in the documentation of the DHT
 
 @short: Allows triggering the inner events
 
+The method is asynchronous and returns a Promise that resolves with the processed event config.
+
 ### Usage
 
 ~~~jsx {}
 api.exec(
     event: string,
     config: object
-): void;
+): Promise<any>;
 ~~~
 
 ### Parameters
@@ -27,7 +29,7 @@ api.exec(
 ### Events
 
 :::info
-The full list of the Booking internal events can be found [**here**](/api/overview/booking-events-overview)
+The full list of the Booking internal events can be found [**here**](api/overview/booking-events-overview.md)
 :::
 
 ### Example
@@ -35,23 +37,21 @@ The full list of the Booking internal events can be found [**here**](/api/overvi
 The example below demonstrates how to apply filter at the initialization:
 
 ~~~jsx {5-19}
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     //other configuration parameters
 });
-booking.api.exec("filter-data", {
-    filterData: {
-        text: "Allergist",
-        date: {
-            start: new Date,
-            end: new Date(2025, 2, 12)
-        },
-        time: [
-            {
-                from: 12,
-                to: 20
-            }
-        ]
-    }
+widget.api.exec("filter-data", {
+    text: "Allergist",
+    date: {
+        start: new Date,
+        end: new Date(2025, 2, 12)
+    },
+    time: [
+        {
+            from: 12,
+            to: 20
+        }
+    ]
 });
 ~~~
diff --git a/docs/api/internal/booking-getreactivestate.md b/docs/api/internal/booking-getreactivestate.md
index 2ab7cbb..3955b16 100644
--- a/docs/api/internal/booking-getreactivestate.md
+++ b/docs/api/internal/booking-getreactivestate.md
@@ -22,7 +22,7 @@ The method returns an object with the following parameters:
 
 ~~~jsx {}
 {    
-    data: [], // an array of cards objects ?
+    data: [], // an array of cards objects
     cardShape: {}, // an object with settings for cards
     filteredData: [], // filtered data array
     filterShape: {}, // an object with filter settings
@@ -30,9 +30,12 @@ The method returns an object with the following parameters:
     formShape: [], // an array of objects with settings for the Booking editor dialog
     infoShape: {}, // an object with settings for the left side of the Booking editor
     selectedItem: {}, // single data item
-    selectedSlot: {}, // an object with slot id and timestamp in minutes
+    selectedSlot: {}, // an object with slot id and time ([timestamp, duration in minutes])
     slotGap: number, // slots gap in minutes
-    slotSize: number // slot size in minutes
+    slotSize: number, // slot size in minutes
+    start: Date, // start date of the displayed range
+    end: Date, // end date of the displayed range
+    renderType: "default" | "lazy" // cards rendering mode
 }
 ~~~
 
@@ -40,17 +43,17 @@ The method returns an object with the following parameters:
 
 ~~~jsx {7-9,11-14}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     //other properties
 });
 
 // get the Reactive State of Booking and output it to console
-const state = booking.api.getReactiveState();
+const state = widget.api.getReactiveState();
 console.log(state);
 
 // subscribe on the cards changes and output the array of cards
-state.cards.subscribe((data) => {
+state.data.subscribe((data) => {
     console.log(data);
 });
 ~~~
diff --git a/docs/api/internal/booking-getstate.md b/docs/api/internal/booking-getstate.md
index 7249049..7c37814 100644
--- a/docs/api/internal/booking-getstate.md
+++ b/docs/api/internal/booking-getstate.md
@@ -30,9 +30,12 @@ The method returns an object with the following parameters of state:
     formShape: [], // an array of objects with settings for the Booking editor dialog
     infoShape: {}, // an object with settings for the left side of the Booking editor
     selectedItem: {}, // single data item
-    selectedSlot: {}, // an object with slot id and timestamp in minutes
+    selectedSlot: {}, // an object with slot id and time ([timestamp, duration in minutes])
     slotGap: number, // slots gap in minutes
-    slotSize: number // slot size in minutes
+    slotSize: number, // slot size in minutes
+    start: Date, // start date of the displayed range
+    end: Date, // end date of the displayed range
+    renderType: "default" | "lazy" // cards rendering mode
 }
 ~~~
 
@@ -40,12 +43,12 @@ The method returns an object with the following parameters of state:
 
 ~~~jsx {7-11}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     cardShape
 });
 
 // get and output the State of Booking to console
-const state = booking.api.getState();
+const state = widget.api.getState();
 console.log(state); 
 ~~~
diff --git a/docs/api/internal/booking-intercept.md b/docs/api/internal/booking-intercept.md
index 51a78e3..62ab079 100644
--- a/docs/api/internal/booking-intercept.md
+++ b/docs/api/internal/booking-intercept.md
@@ -15,7 +15,8 @@ description: You can learn about the intercept method in the documentation of th
 ~~~jsx {}
 api.intercept(
     event: string,
-    callback: function
+    callback: function,
+    config?: { tag?: number | string }
 ): void;
 ~~~
 
@@ -23,23 +24,25 @@ api.intercept(
 
 - `event` - (required) an event to be fired
 - `callback` - (required) a callback to be performed (the callback arguments will depend on the event to be fired)
+- `config` - (optional) an object with extra settings for the callback:
+  - `tag` - (optional) a tag that identifies the callback so it can be removed later via the [`api.detach()`](api/internal/booking-detach.md) method
 
 :::info
-The full list of the Booking internal events you can find [**here**](/api/overview/booking-events-overview).
-Use the [`api.on()`](/api/internal/booking-on) method if you want to listen to the actions without modifying them. To make changes to the actions, apply the `api.intercept()` method.
+The full list of the Booking internal events you can find [**here**](api/overview/booking-events-overview.md).
+Use the [`api.on()`](api/internal/booking-on.md) method if you want to listen to the actions without modifying them. To make changes to the actions, apply the `api.intercept()` method.
 :::
 
 ### Example
 
 ~~~jsx {7-11}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // other configuration parameters
 });
 
 // every time the filter-data event is triggered, slots will be shown only for the morning time
-booking.api.intercept("filter-data", data => {
+widget.api.intercept("filter-data", data => {
     data.time = [{ from: 9, to: 12 }];
 });
 ~~~
diff --git a/docs/api/internal/booking-on.md b/docs/api/internal/booking-on.md
index a491347..d046dbd 100644
--- a/docs/api/internal/booking-on.md
+++ b/docs/api/internal/booking-on.md
@@ -15,7 +15,8 @@ description: You can learn about the on method in the documentation of the DHTML
 ~~~jsx {}
 api.on(
     event: string,
-    handler: function
+    handler: function,
+    config?: { tag?: number | string }
 ): void;
 ~~~
 
@@ -23,23 +24,25 @@ api.on(
 
 - `event` - (required) an event to be fired
 - `handler` - (required) a handler to be attached (the handler arguments will depend on the event to be fired)
+- `config` - (optional) an object with extra settings for the handler:
+  - `tag` - (optional) a tag that identifies the handler so it can be removed later via the [`api.detach()`](api/internal/booking-detach.md) method
 
 :::info
-The full list of the Booking internal events you can find [**here**](/api/overview/booking-events-overview).
-Use the `api.on()` method if you want to listen to the actions without modifying them. To make changes to the actions, apply the [`api.intercept()`](/api/internal/booking-intercept) method.
+The full list of the Booking internal events you can find [**here**](api/overview/booking-events-overview.md).
+Use the `api.on()` method if you want to listen to the actions without modifying them. To make changes to the actions, apply the [`api.intercept()`](api/internal/booking-intercept.md) method.
 :::
 
 ### Example
 
 ~~~jsx {7-10}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // other configuration parameters
 });
 
 // output the selected slot id and time
-booking.api.on("select-slot", (obj) => {
+widget.api.on("select-slot", (obj) => {
     console.log("The selected slot", obj.id, "and time", obj.time);
 });
 ~~~
diff --git a/docs/api/internal/booking-setnext.md b/docs/api/internal/booking-setnext.md
index 47394fd..67d2029 100644
--- a/docs/api/internal/booking-setnext.md
+++ b/docs/api/internal/booking-setnext.md
@@ -25,17 +25,17 @@ api.setNext(next: any): void;
 The example below shows how to use the `api.setNext()` method to integrate some custom class into the Event Bus order:
 
 ~~~jsx {}
-const booking = new booking.Booking("#root", { data: [] });
+const widget = new booking.Booking("#root", { data: [] });
 const server = "https://some-backend-url";
 
 // Assume you have a custom server service class named someServerService
 const someServerService = new ServerDataService(server);
 
 fetch(server + "/data").then((res) => res.json()).then((data) => { 
-    booking.setConfig({data});
+    widget.setConfig({data});
 });   
 // Integrate the serverDataService into the Event Bus order of widget
-booking.api.setNext(someServerService);
+widget.api.setNext(someServerService);
 ~~~
 
-**Related articles:** [Loading data](/guides/loading-data)
+**Related articles**: [Loading data](guides/loading-data.md)
diff --git a/docs/api/methods/booking-serialize-method.md b/docs/api/methods/booking-serialize-method.md
index 89c9eea..06bef82 100644
--- a/docs/api/methods/booking-serialize-method.md
+++ b/docs/api/methods/booking-serialize-method.md
@@ -13,21 +13,21 @@ description: You can learn about the serialize() method in the documentation of
 ### Usage
 
 ~~~jsx
-serialize(): [];
+serialize(): object[];
 ~~~
 
 ### Returns
 
-Returns [data](/api/config/booking-data) array.
+Returns [data](api/config/booking-data.md) array.
 
 ### Example
 
 ~~~jsx {}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // configuration parameters
 });
 
-console.log(booking.serialize());
+console.log(widget.serialize());
 ~~~
diff --git a/docs/api/methods/booking-setconfig-method.md b/docs/api/methods/booking-setconfig-method.md
index e943691..a748d42 100644
--- a/docs/api/methods/booking-setconfig-method.md
+++ b/docs/api/methods/booking-setconfig-method.md
@@ -20,7 +20,7 @@ setConfig(config: object): void;
 
 ### Parameters
 
-- `config` - (required) an object of the Booking configuration. See the full list of properties [here](/api/overview/booking-properties-overview)
+- `config` - (required) an object of the Booking configuration. See the full list of properties [here](api/overview/booking-properties-overview.md)
 
 :::info
 The method changes only the parameters you passed. It destroys the current component and initializes a new one.
@@ -30,7 +30,7 @@ The method changes only the parameters you passed. It destroys the current compo
 
 ~~~jsx {}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     cardShape: {
         review: false,
@@ -49,20 +49,18 @@ const booking = new booking.Booking("#root", {
 });
 
 //update configuration parameters
-booking.setConfig({
-    config: {
-        cardShape: {
-            review: true
-        },
-        filterShape: {
-            date: true,
-            autoApply: false,
-            time: [
-                { from: 9, to: 11, label: "Morning" },
-                { from: 13, to: 17, label: "Afternoon" },
-                { from: 18, to: 20, label: "Evening" }
-            ]
-        }
+widget.setConfig({
+    cardShape: {
+        review: true
+    },
+    filterShape: {
+        date: true,
+        autoApply: false,
+        time: [
+            { from: 9, to: 11, label: "Morning" },
+            { from: 13, to: 17, label: "Afternoon" },
+            { from: 18, to: 20, label: "Evening" }
+        ]
     }
 });
 ~~~
diff --git a/docs/api/methods/booking-setconfirmhandler-method.md b/docs/api/methods/booking-setconfirmhandler-method.md
index 5d51063..6a01cd5 100644
--- a/docs/api/methods/booking-setconfirmhandler-method.md
+++ b/docs/api/methods/booking-setconfirmhandler-method.md
@@ -18,21 +18,21 @@ setConfirmHandler(confirmHandler: (ev) => any): void;
 
 ### Parameters
 
-The method takes the `confirmHandler` function that will be called when confirming a slot for booking. The function takes the object as in the [`confirm-slot`](/api/events/booking-confirmslot-event) event.
+The method takes the `confirmHandler` function that will be called when confirming a slot for booking. The function takes the object as in the [`confirm-slot`](api/events/booking-confirmslot-event.md) event.
 
 ### Example
 
 ~~~jsx {}
 const { data } = getData();
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data
 });
 
-booking.setConfirmHandler((ev) => {
+widget.setConfirmHandler((ev) => {
     console.log("Booking info:", ev);
 });
 ~~~
 
 <iframe src="https://snippet.dhtmlx.com/dpbmyr8j?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
-**Related articles**: [Saving slots reservations to the server](/guides/saving-reservations)
+**Related articles**: [Saving slots reservations to the server](guides/saving-reservations.md)
diff --git a/docs/api/methods/booking-setlocale-method.md b/docs/api/methods/booking-setlocale-method.md
index 2b60535..fe5a8e7 100644
--- a/docs/api/methods/booking-setlocale-method.md
+++ b/docs/api/methods/booking-setlocale-method.md
@@ -13,7 +13,7 @@ description: You can learn about the setLocale() method in the documentation of
 ### Usage
 
 ~~~jsx
-setLocale(null | locale?: object): void;
+setLocale(locale?: object | null): void;
 ~~~
 
 ### Parameters
@@ -25,18 +25,18 @@ setLocale(null | locale?: object): void;
 
 ~~~jsx {}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     // initial configuration parameters
 });
 
 // apply the "de" locale to Booking
-booking.setLocale(de);
+widget.setLocale(booking.locales.de);
 
 // apply the default locale to Booking
-booking.setLocale(); // or setLocale(null);
+widget.setLocale(); // or setLocale(null);
 ~~~
 
 **Related articles**:
-- [locale](/api/config/booking-locale)
-- [Localization](/guides/localization)
+- [locale](api/config/booking-locale.md)
+- [Localization](guides/localization.md)
diff --git a/docs/api/overview/booking-api-overview.md b/docs/api/overview/booking-api-overview.md
index 0facd06..c9ab40e 100644
--- a/docs/api/overview/booking-api-overview.md
+++ b/docs/api/overview/booking-api-overview.md
@@ -23,10 +23,10 @@ new booking.Booking("#root", {
 
 | Name                                               | Description                                               |
 | -------------------------------------------------- | --------------------------------------------------------- |
-| [](../methods/booking-serialize-method.md)         | @getshort(../methods/booking-serialize-method.md)         |
-| [](../methods/booking-setconfig-method.md)         | @getshort(../methods/booking-setconfig-method.md)         |
-| [](../methods/booking-setconfirmhandler-method.md) | @getshort(../methods/booking-setconfirmhandler-method.md) |
-| [](../methods/booking-setlocale-method.md)         | @getshort(../methods/booking-setlocale-method.md)         |
+| [](api/methods/booking-serialize-method.md)         | @getshort(../methods/booking-serialize-method.md)         |
+| [](api/methods/booking-setconfig-method.md)         | @getshort(../methods/booking-setconfig-method.md)         |
+| [](api/methods/booking-setconfirmhandler-method.md) | @getshort(../methods/booking-setconfirmhandler-method.md) |
+| [](api/methods/booking-setlocale-method.md)         | @getshort(../methods/booking-setlocale-method.md)         |
 
 ## Booking internal API
 
@@ -34,43 +34,43 @@ new booking.Booking("#root", {
 
 | Name                                     | Description                                     |
 | ---------------------------------------- | ----------------------------------------------- |
-| [](../internal/booking-detach.md)    | @getshort(../internal/booking-detach.md)            |
-| [](../internal/booking-exec.md)      | @getshort(../internal/booking-exec.md)              |
-| [](../internal/booking-intercept.md) | @getshort(../internal/booking-intercept.md)         |
-| [](../internal/booking-on.md)        | @getshort(../internal/booking-on.md)                |
-| [](../internal/booking-setnext.md)   | @getshort(../internal/booking-setnext.md)           |
+| [](api/internal/booking-detach.md)    | @getshort(../internal/booking-detach.md)            |
+| [](api/internal/booking-exec.md)      | @getshort(../internal/booking-exec.md)              |
+| [](api/internal/booking-intercept.md) | @getshort(../internal/booking-intercept.md)         |
+| [](api/internal/booking-on.md)        | @getshort(../internal/booking-on.md)                |
+| [](api/internal/booking-setnext.md)   | @getshort(../internal/booking-setnext.md)           |
 
 ### State methods
 
 | Name                                            | Description                                            |
 | ----------------------------------------------- | ------------------------------------------------------ |
-| [](../internal/booking-getreactivestate.md) | @getshort(../internal/booking-getreactivestate.md) |
-| [](../internal/booking-getstate.md)         | @getshort(../internal/booking-getstate.md)         |
+| [](api/internal/booking-getreactivestate.md) | @getshort(../internal/booking-getreactivestate.md) |
+| [](api/internal/booking-getstate.md)         | @getshort(../internal/booking-getstate.md)         |
 
 ## Booking events
 
 | Name                                      | Description                                      |
 | ----------------------------------------- | ------------------------------------------------ |
-| [](../events/booking-confirmslot-event.md)  | @getshort(../events/booking-confirmslot-event.md)  |
-| [](../events/booking-filterdata-event.md)  | @getshort(../events/booking-filterdata-event.md)    |
-| [](../events/booking-selectitem-event.md)  | @getshort(../events/booking-selectitem-event.md)    |
-| [](../events/booking-selectitemdate-event.md)  | @getshort(../events/booking-selectitemdate-event.md) |
-| [](../events/booking-selectslot-event.md)   | @getshort(../events/booking-selectslot-event.md)   |
+| [](api/events/booking-confirmslot-event.md)  | @getshort(../events/booking-confirmslot-event.md)  |
+| [](api/events/booking-filterdata-event.md)  | @getshort(../events/booking-filterdata-event.md)    |
+| [](api/events/booking-selectitem-event.md)  | @getshort(../events/booking-selectitem-event.md)    |
+| [](api/events/booking-selectitemdate-event.md)  | @getshort(../events/booking-selectitemdate-event.md) |
+| [](api/events/booking-selectslot-event.md)   | @getshort(../events/booking-selectslot-event.md)   |
 
 ## Booking properties
 
 | Name                                  | Description                                        |
 | ------------------------------------- | -------------------------------------------------- |
-| [](../config/booking-data.md)         | @getshort(../config/booking-data.md)               |
-| [](../config/booking-end.md)          | @getshort(../config/booking-end.md)                |
-| [](../config/booking-cardshape.md)    | @getshort(../config/booking-cardshape.md)          |
-| [](../config/booking-cardtemplate.md) | @getshort(../config/booking-cardtemplate.md)       |
-| [](../config/booking-filtershape.md)  | @getshort(../config/booking-filtershape.md)        |
-| [](../config/booking-formshape.md)    | @getshort(../config/booking-formshape.md)          |
-| [](../config/booking-infoshape.md)    | @getshort(../config/booking-infoshape.md)          |
-| [](../config/booking-infotemplate.md) | @getshort(../config/booking-infotemplate.md)       |
-| [](../config/booking-locale.md)       | @getshort(../config/booking-locale.md)             |
-| [](../config/booking-rendertype.md)   | @getshort(../config/booking-rendertype.md)         |
-| [](../config/booking-slotgap.md)      | @getshort(../config/booking-slotgap.md)            |
-| [](../config/booking-slotsize.md)     | @getshort(../config/booking-slotsize.md)           |
-| [](../config/booking-start.md)        | @getshort(../config/booking-start.md)              |
+| [](api/config/booking-data.md)         | @getshort(../config/booking-data.md)               |
+| [](api/config/booking-end.md)          | @getshort(../config/booking-end.md)                |
+| [](api/config/booking-cardshape.md)    | @getshort(../config/booking-cardshape.md)          |
+| [](api/config/booking-cardtemplate.md) | @getshort(../config/booking-cardtemplate.md)       |
+| [](api/config/booking-filtershape.md)  | @getshort(../config/booking-filtershape.md)        |
+| [](api/config/booking-formshape.md)    | @getshort(../config/booking-formshape.md)          |
+| [](api/config/booking-infoshape.md)    | @getshort(../config/booking-infoshape.md)          |
+| [](api/config/booking-infotemplate.md) | @getshort(../config/booking-infotemplate.md)       |
+| [](api/config/booking-locale.md)       | @getshort(../config/booking-locale.md)             |
+| [](api/config/booking-rendertype.md)   | @getshort(../config/booking-rendertype.md)         |
+| [](api/config/booking-slotgap.md)      | @getshort(../config/booking-slotgap.md)            |
+| [](api/config/booking-slotsize.md)     | @getshort(../config/booking-slotsize.md)           |
+| [](api/config/booking-start.md)        | @getshort(../config/booking-start.md)              |
diff --git a/docs/api/overview/booking-events-overview.md b/docs/api/overview/booking-events-overview.md
index 6012a9a..ed9f7e6 100644
--- a/docs/api/overview/booking-events-overview.md
+++ b/docs/api/overview/booking-events-overview.md
@@ -8,8 +8,8 @@ description: You can have events overview of JavaScript Booking in the documenta
 
 | Name                                      | Description                                      |
 | ----------------------------------------- | ------------------------------------------------ |
-| [](../events/booking-confirmslot-event.md)  | @getshort(../events/booking-confirmslot-event.md)  |
-| [](../events/booking-filterdata-event.md)  | @getshort(../events/booking-filterdata-event.md)    |
-| [](../events/booking-selectitem-event.md)  | @getshort(../events/booking-selectitem-event.md)    |
-| [](../events/booking-selectitemdate-event.md)  | @getshort(../events/booking-selectitemdate-event.md) |
-| [](../events/booking-selectslot-event.md)   | @getshort(../events/booking-selectslot-event.md)   |
+| [](api/events/booking-confirmslot-event.md)  | @getshort(../events/booking-confirmslot-event.md)  |
+| [](api/events/booking-filterdata-event.md)  | @getshort(../events/booking-filterdata-event.md)    |
+| [](api/events/booking-selectitem-event.md)  | @getshort(../events/booking-selectitem-event.md)    |
+| [](api/events/booking-selectitemdate-event.md)  | @getshort(../events/booking-selectitemdate-event.md) |
+| [](api/events/booking-selectslot-event.md)   | @getshort(../events/booking-selectslot-event.md)   |
diff --git a/docs/api/overview/booking-internal-eventbus-overview.md b/docs/api/overview/booking-internal-eventbus-overview.md
index f826e22..7b4331b 100644
--- a/docs/api/overview/booking-internal-eventbus-overview.md
+++ b/docs/api/overview/booking-internal-eventbus-overview.md
@@ -8,8 +8,8 @@ description: You can have event bus methods overview of JavaScript Booking in th
 
 | Name                                 | Description                                         |
 | ------------------------------------ | --------------------------------------------------- |
-| [](../internal/booking-detach.md)    | @getshort(../internal/booking-detach.md)            |
-| [](../internal/booking-exec.md)      | @getshort(../internal/booking-exec.md)              |
-| [](../internal/booking-intercept.md) | @getshort(../internal/booking-intercept.md)         |
-| [](../internal/booking-on.md)        | @getshort(../internal/booking-on.md)                |
-| [](../internal/booking-setnext.md)   | @getshort(../internal/booking-setnext.md)           |
+| [](api/internal/booking-detach.md)    | @getshort(../internal/booking-detach.md)            |
+| [](api/internal/booking-exec.md)      | @getshort(../internal/booking-exec.md)              |
+| [](api/internal/booking-intercept.md) | @getshort(../internal/booking-intercept.md)         |
+| [](api/internal/booking-on.md)        | @getshort(../internal/booking-on.md)                |
+| [](api/internal/booking-setnext.md)   | @getshort(../internal/booking-setnext.md)           |
diff --git a/docs/api/overview/booking-internal-state-overview.md b/docs/api/overview/booking-internal-state-overview.md
index b230795..5ccd67d 100644
--- a/docs/api/overview/booking-internal-state-overview.md
+++ b/docs/api/overview/booking-internal-state-overview.md
@@ -8,5 +8,5 @@ description: You can have an API overview of JavaScript Booking in the documenta
 
 | Name                                        | Description                                        |
 | ------------------------------------------- | -------------------------------------------------- |
-| [](../internal/booking-getreactivestate.md) | @getshort(../internal/booking-getreactivestate.md) |
-| [](../internal/booking-getstate.md)         | @getshort(../internal/booking-getstate.md)         |
+| [](api/internal/booking-getreactivestate.md) | @getshort(../internal/booking-getreactivestate.md) |
+| [](api/internal/booking-getstate.md)         | @getshort(../internal/booking-getstate.md)         |
diff --git a/docs/api/overview/booking-methods-overview.md b/docs/api/overview/booking-methods-overview.md
index 29515d0..8ac757b 100644
--- a/docs/api/overview/booking-methods-overview.md
+++ b/docs/api/overview/booking-methods-overview.md
@@ -8,7 +8,7 @@ description: You can have methods overview of JavaScript Booking in the document
 
 | Name                                               | Description                                               |
 | -------------------------------------------------- | --------------------------------------------------------- |
-| [](../methods/booking-serialize-method.md)         | @getshort(../methods/booking-serialize-method.md)         |
-| [](../methods/booking-setconfig-method.md)         | @getshort(../methods/booking-setconfig-method.md)         |
-| [](../methods/booking-setconfirmhandler-method.md) | @getshort(../methods/booking-setconfirmhandler-method.md) |
-| [](../methods/booking-setlocale-method.md)         | @getshort(../methods/booking-setlocale-method.md)         |
+| [](api/methods/booking-serialize-method.md)         | @getshort(../methods/booking-serialize-method.md)         |
+| [](api/methods/booking-setconfig-method.md)         | @getshort(../methods/booking-setconfig-method.md)         |
+| [](api/methods/booking-setconfirmhandler-method.md) | @getshort(../methods/booking-setconfirmhandler-method.md) |
+| [](api/methods/booking-setlocale-method.md)         | @getshort(../methods/booking-setlocale-method.md)         |
diff --git a/docs/api/overview/booking-properties-overview.md b/docs/api/overview/booking-properties-overview.md
index 1c27854..48ec3dd 100644
--- a/docs/api/overview/booking-properties-overview.md
+++ b/docs/api/overview/booking-properties-overview.md
@@ -8,16 +8,16 @@ description: You can have properties overview of JavaScript Booking in the docum
 
 | Name                                  | Description                                        |
 | ------------------------------------- | -------------------------------------------------- |
-| [](../config/booking-data.md)         | @getshort(../config/booking-data.md)               |
-| [](../config/booking-end.md)          | @getshort(../config/booking-end.md)                |
-| [](../config/booking-cardshape.md)    | @getshort(../config/booking-cardshape.md)          |
-| [](../config/booking-cardtemplate.md) | @getshort(../config/booking-cardtemplate.md)       |
-| [](../config/booking-filtershape.md)  | @getshort(../config/booking-filtershape.md)        |
-| [](../config/booking-formshape.md)    | @getshort(../config/booking-formshape.md)          |
-| [](../config/booking-infoshape.md)    | @getshort(../config/booking-infoshape.md)          |
-| [](../config/booking-infotemplate.md) | @getshort(../config/booking-infotemplate.md)       |
-| [](../config/booking-locale.md)       | @getshort(../config/booking-locale.md)             |
-| [](../config/booking-rendertype.md)   | @getshort(../config/booking-rendertype.md)         |
-| [](../config/booking-slotgap.md)      | @getshort(../config/booking-slotgap.md)            |
-| [](../config/booking-slotsize.md)     | @getshort(../config/booking-slotsize.md)           |
-| [](../config/booking-start.md)        | @getshort(../config/booking-start.md)              |
+| [](api/config/booking-data.md)         | @getshort(../config/booking-data.md)               |
+| [](api/config/booking-end.md)          | @getshort(../config/booking-end.md)                |
+| [](api/config/booking-cardshape.md)    | @getshort(../config/booking-cardshape.md)          |
+| [](api/config/booking-cardtemplate.md) | @getshort(../config/booking-cardtemplate.md)       |
+| [](api/config/booking-filtershape.md)  | @getshort(../config/booking-filtershape.md)        |
+| [](api/config/booking-formshape.md)    | @getshort(../config/booking-formshape.md)          |
+| [](api/config/booking-infoshape.md)    | @getshort(../config/booking-infoshape.md)          |
+| [](api/config/booking-infotemplate.md) | @getshort(../config/booking-infotemplate.md)       |
+| [](api/config/booking-locale.md)       | @getshort(../config/booking-locale.md)             |
+| [](api/config/booking-rendertype.md)   | @getshort(../config/booking-rendertype.md)         |
+| [](api/config/booking-slotgap.md)      | @getshort(../config/booking-slotgap.md)            |
+| [](api/config/booking-slotsize.md)     | @getshort(../config/booking-slotsize.md)           |
+| [](api/config/booking-start.md)        | @getshort(../config/booking-start.md)              |
diff --git a/docs/guides/configuration.md b/docs/guides/configuration.md
index fc17a37..717b3f1 100644
--- a/docs/guides/configuration.md
+++ b/docs/guides/configuration.md
@@ -6,32 +6,36 @@ description: You can learn about the configuration in the documentation of the D
 
 # Configuration
 
-## Loading data for cards
+## Load data for cards
 
-To load data, add data to the [`data`](/api/config/booking-data) array. See all instructions here: [`Loading data`](/guides/loading-data).
+Pass card objects to the [`data`](api/config/booking-data.md) array of the Booking configuration. For the full data format and loading scenarios, see the [Loading data](guides/loading-data.md) guide.
 
-## Defining the structure of cards 
+## Define the structure of cards
 
-You can configure what information all cards will display on their left side using the [`cardShape`](/api/config/booking-cardshape) property or the [`cardTemplate`](/api/config/booking-cardtemplate) property, which also allows customizing the appearance of each card's block.
+The left side of each card displays a fixed set of data fields. To control which fields appear or to fully replace the default layout, use one of the following properties:
+
+- [`cardShape`](api/config/booking-cardshape.md) — toggle visibility of the default fields
+- [`cardTemplate`](api/config/booking-cardtemplate.md) — replace the default layout with custom HTML
 
 :::info
-`cardTemplate` helps completely customize the appearance of a card by providing your own custom HTML. It gives full control over the card's layout, design and content.
-`cardShape` allows you only to modify the default template by hiding/showing fields. 
-If both are applied, `cardTemplate` will override the `cardShape` settings.
+The `cardTemplate` property fully customizes a card's appearance through custom HTML and gives full control over layout, design, and content. The `cardShape` property only hides or shows fields of the default template. If you apply both, `cardTemplate` overrides the `cardShape` settings.
 :::
 
-On the left side of each card the following data fields are displayed by default:
-- preview: card image
-- review: rating information with the number of rating stars (out of five) and the number of reviews
-- category: the subtitle of a card
-- title: the title of a card which is a specialist's name
-- subtitle: the subtitle of a card, for example, experience details 
-- price: the price of the service
-- details: other details of a card
+### Toggle default card fields
+
+The card's left side displays the following fields by default:
+
+- `preview` — card image
+- `review` — rating information with the number of rating stars (out of five) and the number of reviews
+- `category` — the category name (for example, a specialist's job)
+- `title` — the card title (for example, a specialist's name)
+- `subtitle` — the card subtitle (for example, experience details)
+- `price` — the price of the service
+- `details` — other details of a card
 
-To hide any information block from cards' display, set the appropriate parameter value of the [`cardShape`](/api/config/booking-cardshape) property to **false**.
+To hide a field, set the corresponding parameter of the [`cardShape`](api/config/booking-cardshape.md) property to `false`.
 
-Example:
+The example below hides the `details` field of a card:
 
 ~~~jsx {24}
 const data = [
@@ -68,12 +72,16 @@ new booking.Booking("#root", {
 ~~~
 
 :::info
-Please, see an example in the [snippet tool](https://snippet.dhtmlx.com/6mxd7918)
+See an example in the [snippet tool](https://snippet.dhtmlx.com/6mxd7918).
 :::
 
-To apply a template to each card (the left-hand block), use the [`cardTemplate`](/api/config/booking-cardtemplate) property. 
+### Apply a custom card template
 
-First, create a function that takes a card object and returns a string of HTML. To define a template, arrange card item properties into any HTML blocks with custom styles. In the example, `cardPreviewTemplate` returns HTML for a card that includes a preview image (card.preview), category (card.category), title (card.title), and price (card.price). 
+The [`cardTemplate`](api/config/booking-cardtemplate.md) property replaces the default left-hand block of a card with custom HTML.
+
+Create a function that takes a card object and returns an HTML string. Arrange card item properties into HTML blocks with custom styles.
+
+The following code snippet defines `cardPreviewTemplate`, which returns HTML for a card with a preview image, category, title, and price:
 
 ~~~html {}
 <style>
@@ -96,21 +104,21 @@ First, create a function that takes a card object and returns a string of HTML.
 <script>
     const { Booking, template } = booking;
 
-    function cardPreviewTemplate({ card }) {
+    function cardPreviewTemplate({ item }) {
         return `
             <div class="custom-preview" data-action="preview-click">
                 <div class="preview-left">
                     <div
-                        style="background-image: url(${card.preview})"
+                        style="background-image: url(${item.preview})"
                         class="card-photo"
                     ></div>
                     <!-- <div class="card-photo-empty" /> -->
                     </div>
 
                     <div class="preview-right">
-                    <div class="category">${card.category}</div>
-                    <div class="title">${card.title}</div>
-                    <div class="price">${card.price}</div>
+                    <div class="category">${item.category}</div>
+                    <div class="title">${item.title}</div>
+                    <div class="price">${item.price}</div>
                 </div>
             </div>
             `;
@@ -118,30 +126,33 @@ First, create a function that takes a card object and returns a string of HTML.
 </script>
 ~~~
 
-Then you also need to import the **template** helper and assign the`cardTemplate` property to your custom template function.
+Import the `template` helper and assign your custom function to the `cardTemplate` property.
+
+The following code snippet wires `cardPreviewTemplate` into the Booking configuration:
 
 ~~~jsx
 const { Booking, template } = booking;
 
 const widget = new Booking("#root", {
 	data,
-	cardTemplate: template(card => cardPreviewTemplate(card)),
+	cardTemplate: template(item => cardPreviewTemplate(item)),
     // other parameters
 });
 ~~~
 
 :::info
-Please, see an example in the [snippet tool](https://snippet.dhtmlx.com/k2v01vng)
+See an example in the [snippet tool](https://snippet.dhtmlx.com/k2v01vng).
 :::
 
-## Filling cards with slots
+## Fill cards with slots
 
-A slot is a time unit available for booking. Available slots for cards are displayed for the next five days starting from the current day or from the start date from the filter. 
+A slot is a time unit available for booking. The widget displays available slots for six days (four on narrow screens), starting from the current day or from the start date selected in the filter.
 
-### Adding slots for booking
+### Add slots for booking
 
-To add booking slots to a card, add an object to the `slots` array of the [`data`](/api/config/booking-data) property.
-In the example below, the slots are added for the specified card for Tuesdays and Fridays from 12 a.m. to 6 p.m and each slot duration is 30 minutes with 10-minutes gap between slots.
+To add booking slots to a card, add an object to the `slots` array of the [`data`](api/config/booking-data.md) property.
+
+The example below adds slots for Tuesdays and Fridays from 12:00 to 18:00. Each slot lasts 30 minutes with a 10-minute gap between slots:
 
 ~~~jsx {15-22}
 const data = [
@@ -154,7 +165,7 @@ const data = [
         preview: "https://snippet.dhtmlx.com/codebase/data/booking/01/img/01.jpg",
         price: "37 $",
         review: {
-            star: 1,
+            stars: 1,
             count: 40
         },
         slots: [
@@ -176,39 +187,37 @@ new booking.Booking("#root", {
 });
 ~~~
 
-### Defining slot rules
+### Define slot rules
 
-Parameters of each object in the `slots` array of the [`data`](/api/config/booking-data) property allow specifying the next settings: 
+Each object in the `slots` array of the [`data`](api/config/booking-data.md) property specifies:
 
-- slots start and end time
-- slot sizes (duration in minutes)
-- slot gaps (the length between slot)
-- days to which slots should be applied
+- slot start and end time
+- slot size (duration in minutes)
+- slot gap (the interval between slots)
+- days or dates to which the rule applies
 
-When applying these rules, you can apply one common rule to all days of the required card or apply different rules (specific rules to selected days or even dates), namely, you can:  
+Apply a single common rule to all days of a card, or combine several rules to use different parameters for selected days or specific dates.
 
-- set the same parameters to all days of a specific card, which means you can add slots with the same duration, the same start and end time to all days of the selected card
-- set different slot duration and slot gaps to the same card by applying different parameters to days of the week of the same card or specific dates
+Set slot size and gap at three levels of priority (from highest to lowest):
 
-When applying **slot size and gap**, you can:
-- set specific values to specific slots of the required card(s) using the `size` and `gap` parameters in the `slots` array of the [`data`](/api/config/booking-data) property (these values have the highest priority and will override the next values in this list)
-- set specific values to all slots of the selected card using the `slotSize` and `slotGap` parameters of the [`data`](/api/config/booking-data) property 
-- set global values to all cards in the widget by using the [`slotSize`](/api/config/booking-slotsize) and [`slotGap`](/api/config/booking-slotgap) properties
+- `size` and `gap` inside an object of the [`data`](api/config/booking-data.md) slots array — apply to that specific slot rule
+- `slotSize` and `slotGap` inside a card object of the [`data`](api/config/booking-data.md) property — apply to all slots of that card
+- [`slotSize`](api/config/booking-slotsize.md) and [`slotGap`](api/config/booking-slotgap.md) at the widget level — apply to all cards
 
 :::info
-In case you have common slots parameters and specific parameters for some days, you should be aware of the following: 
-- Slot parameters defined for specific days will override common parameters defined for all days. 
-- Slot parameters specified for dates will override parameters defined for specific days and all days. 
-- If several slots objects are created for the same day, make sure that slots time ranges (from and to) with **different** size and gap do not overlap, otherwise all slots data for these days will not be applied.
+When you mix common and specific rules, the widget resolves them as follows:
+- Slot parameters defined for specific days override common parameters defined for all days.
+- Slot parameters specified for dates override parameters defined for specific days and all days.
+- If several slot objects target the same day, the time ranges (`from` and `to`) with different `size` or `gap` must not overlap. Otherwise, the widget skips all slot data for those days.
 :::
 
-For all slots of the widget, you can also set the [`end`](/api/config/booking-end) value that defines the date until which slots are displayed and/or the [`start`](/api/config/booking-start) date from which to start showing slots.
+To bound the range of displayed slots, set the [`start`](api/config/booking-start.md) date and the [`end`](api/config/booking-end.md) date at the widget level.
 
-#### Examples of defining slot rules
+#### Apply one rule to all days
 
-For example, if you want to add booking slots with the same parameters to all days of the selected card, i.e., add slots with the same duration, the same start and end time to all days of the selected card, you should add one object to the `slots` array with the required parameters. 
+To add slots with the same duration and time range to every day of a card, add a single object to the `slots` array.
 
-Example:
+The following code snippet defines a common rule for all days from 14:00 to 17:00, with 30-minute slots and a 10-minute gap:
 
 ~~~jsx {}
 const data = [
@@ -221,7 +230,7 @@ const data = [
         preview: "https://snippet.dhtmlx.com/codebase/data/booking/01/img/01.jpg",
         price: "37 $",
         review: {
-            star: 1,
+            stars: 1,
             count: 40
         },
         slots: [
@@ -242,9 +251,11 @@ new booking.Booking("#root", {
 });
 ~~~
     
-But if you need to add slots with one set of parameters to some days of the week and other parameters to the other days, you need to add several objects to the `slots` array and specify days/dates to which these parameters should be applied.  
+#### Apply different rules per day or date
+
+To use different parameters for selected weekdays or exact dates, add several objects to the `slots` array and set the `days` or `dates` parameter on each rule.
 
-Example:
+The following code snippet combines three rules — a common rule, a weekday rule for Tuesdays and Fridays, and a rule for Wednesdays, Thursdays, and one exact date:
 
 ~~~jsx {}
 const data = [
@@ -257,20 +268,20 @@ const data = [
         preview: "https://snippet.dhtmlx.com/codebase/data/booking/01/img/01.jpg",
         price: "37 $",
         review: {
-            star: 1,
+            stars: 1,
             count: 40
         },
         slots: [
             {
-                //a common slot rule for all days except those specified for the days and dates below
+                // common rule for all days except those listed below
                 from: 14,
                 to: 17,
                 size: 30,
                 gap: 10
             },
             {
-                //this rule is applied to days 2 and 5 (Tuesdays and Fridays) except
-                //the Friday from the slot object below
+                // applies to Tuesdays and Fridays, except the Friday
+                // listed in the next rule
                 from: 12,
                 to: 17,
                 size: 50,
@@ -278,13 +289,13 @@ const data = [
                 days: [2, 5]
             },
             {
-                //this rule is applied to days 3 and 4 (Wednesdays and Thursdays) and exact date
+                // applies to Wednesdays, Thursdays, and one exact date
                 from: 18,
                 to: 20,
                 size: 45,
                 gap: 20,
                 days: [3, 4],
-                dates: [ 1683234000000 ] // exact upcoming date (May 5, 2023, Friday)
+                dates: [ 1683234000000 ] // May 5, 2023, Friday
             }
         ]
     }
@@ -296,13 +307,20 @@ new booking.Booking("#root", {
 });
 ~~~
 
-To see how to set [duration](/api/config/booking-slotsize) and [gap](/api/config/booking-slotgap) for all slots in the widget, [open the snippet tool](https://snippet.dhtmlx.com/pw8xsl1p).
+To see how to set [duration](api/config/booking-slotsize.md) and [gap](api/config/booking-slotgap.md) for all slots in the widget, [open the snippet tool](https://snippet.dhtmlx.com/pw8xsl1p).
+
+### Mark slots as used or available
+
+Two parameters of the [`data`](api/config/booking-data.md) card object control which slots a user can see or book:
+
+- `usedSlots` — hide booked slots from the user
+- `availableSlots` — display an explicit list of bookable slots and ignore the `slots` array rules
 
-### Marking slots as used or available
+#### Mark slots as used
 
-To mark slots as used (booked) and make them not visible for a user, use the `usedSlots` parameter of the required card item of the [`data`](/api/config/booking-data) property.
+To hide booked slots, set the `usedSlots` parameter to an array of slot start timestamps.
 
-Example:
+The following code snippet hides one slot as already booked:
 
 ~~~jsx {}
 const data = [
@@ -315,20 +333,21 @@ const data = [
         preview: "https://snippet.dhtmlx.com/codebase/data/booking/01/img/01.jpg",
         price: "37 $",
         review: {
-            star: 1,
+            stars: 1,
             count: 40
         },
         slots: [
             {
-                //a common rule for all days\
-                from: 14, //slots start time
-                to: 17, // slots end time
-                size: 30, // each slot duration in minutes
-                gap: 10 // a gap between slots
+                // common rule for all days
+                from: 14, // slot start time
+                to: 17,   // slot end time
+                size: 30, // slot duration in minutes
+                gap: 10   // gap between slots
             }
         ],
-        usedSlots: [ 1683234000000 ] // an array of timestamps of booked slots in milliseconds
-    },]
+        usedSlots: [ 1683234000000 ] // timestamps of booked slots in milliseconds
+    }
+];
 
 new booking.Booking("#root", {
     data,
@@ -336,11 +355,11 @@ new booking.Booking("#root", {
 });
 ~~~
 
-To mark available slots, use the `availableSlots` parameter of the [`data`](/api/config/booking-data) property.
+#### Mark slots as available
 
-If available slots are specified here, all slots from the `slots` array are ignored (i.e., become unavailable).
+To display an explicit list of bookable slots, use the `availableSlots` parameter of the [`data`](api/config/booking-data.md) property. When you set `availableSlots`, the widget ignores every entry in the `slots` array.
 
-Example:
+The following code snippet exposes two timestamps as the only bookable slots for the card:
 
 ~~~jsx {}
 const data = [
@@ -353,19 +372,19 @@ const data = [
         preview: "https://snippet.dhtmlx.com/codebase/data/booking/01/img/01.jpg",
         price: "37 $",
         review: {
-            star: 1,
+            stars: 1,
             count: 40
         },
         slots: [
             {
-                //a common rule for all days\
-                from: 14, //slots start time
-                to: 17, // slots end time
-                size: 30, // each slot duration in minutes
-                gap: 10 // a gap between slots
+                // common rule for all days
+                from: 14, // slot start time
+                to: 17,   // slot end time
+                size: 30, // slot duration in minutes
+                gap: 10   // gap between slots
             }
         ],
-        availableSlots: [ 1693325145000, 1693584345000 ] // an array of timestamps of available slots in milliseconds
+        availableSlots: [ 1693325145000, 1693584345000 ] // timestamps of available slots in milliseconds
     }
 ];
 
@@ -375,27 +394,35 @@ new booking.Booking("#root", {
 });
 ~~~
 
-## Configuring the Booking dialog
+## Configure the Booking dialog
 
-To configure the fields that should be displayed in the Booking dialog, use the [`formShape`](/api/config/booking-formshape) property.
+The Booking dialog has two configurable parts: the form fields where a user enters booking details, and the information block on the left side. Use the following properties to control each part:
 
-To add a new field, add a new object to the array. To make a field required for filling, set the `required` parameter to *true*. 
+- [`formShape`](api/config/booking-formshape.md) — configure the form fields
+- [`infoShape`](api/config/booking-infoshape.md) — toggle default fields of the information block
+- [`infoTemplate`](api/config/booking-infotemplate.md) — replace the information block with a custom HTML template
+
+### Configure form fields
+
+Pass an array of field descriptors to the [`formShape`](api/config/booking-formshape.md) property. Each descriptor sets the field type, identifier, label, and an optional `required` flag.
+
+The following code snippet defines three form fields, with the `contact` field marked as required:
 
 ~~~jsx {}
 const formShape = [
     {
-        type: "text",
+        comp: "text",
         key: "name",
         label: "Your name"
     },
     {
-        type: "text",
+        comp: "text",
         key: "contact",
         label: "Mobile",
         required: true
     },
     {
-        type: "textarea",
+        comp: "textarea",
         key: "description",
         label: "Details"
     }
@@ -408,10 +435,14 @@ new booking.Booking("#root", {
 ~~~
 
 :::info
-Please, see an example in the [snippet tool](https://snippet.dhtmlx.com/yeqkuzx7)
+See an example in the [snippet tool](https://snippet.dhtmlx.com/yeqkuzx7).
 :::
 
-To manage information that is displayed on the left side of the Booking dialog, apply the [`infoShape`](/api/config/booking-infoshape) property. You can hide necessary fields from display by setting values to *false*.
+### Toggle default information fields
+
+The [`infoShape`](api/config/booking-infoshape.md) property hides or shows the default fields of the information block. Set a field to `false` to hide it.
+
+The following code snippet hides the `details` field of the information block:
 
 ~~~jsx {1-7,11}
 const infoShape = {
@@ -425,17 +456,21 @@ const infoShape = {
 new booking.Booking("#root", {
     data,
     infoShape,
-    //other parameters
+    // other parameters
 });
 ~~~
 
 :::info
-Please, see an example in the [snippet tool](https://snippet.dhtmlx.com/pd6wp1xc)
+See an example in the [snippet tool](https://snippet.dhtmlx.com/pd6wp1xc).
 :::
 
-To fully customize the appearance and content of the information block, apply your own template using the [`infoTemplate`](/api/config/booking-infotemplate) property (`infoShape` can be used only to hide/show fields provided by the default template). If both properties are applied, `infoTemplate` will override the `infoShape` settings.
+### Apply a custom information template
 
-To apply a template, you need to define the function that will generate the custom HTML for the information block. This function will receive the card and slot objects as input parameters, which are `item` (card object) and `slot` (slot timestamp) as in the example below. You should also define your custom template by arranging card item properties into any HTML blocks with custom styles.
+Use the [`infoTemplate`](api/config/booking-infotemplate.md) property to fully replace the default information block with custom HTML. If you apply both `infoTemplate` and `infoShape`, `infoTemplate` overrides the `infoShape` settings.
+
+Define a function that takes `item` (the card object) and `slot` (the slot timestamp) and returns an HTML string. Arrange card item properties into HTML blocks with custom styles.
+
+The following code snippet defines `cardInfoTemplate`, which renders a photo, title, category, and formatted date for the selected slot:
 
 ~~~html
 <style>
@@ -485,7 +520,9 @@ To apply a template, you need to define the function that will generate the cust
 </script>
 ~~~
 
-Then you also need to import the **template** helper and pass the `infoTemplate` function into the Booking configuration as follows:
+Import the `template` helper and assign your custom function to the `infoTemplate` property.
+
+The following code snippet wires `cardInfoTemplate` into the Booking configuration:
 
 ~~~jsx
 const { Booking, template } = booking;
@@ -498,13 +535,12 @@ const widget = new Booking("#root", {
 ~~~
 
 :::info
-Please, see an example in the [snippet tool](https://snippet.dhtmlx.com/byb94ipu) 
+See an example in the [snippet tool](https://snippet.dhtmlx.com/byb94ipu).
 :::
 
+## Configure the filter
 
-## Configuring the filter
-
-You can configure filter settings via the [`filterShape`](/api/config/booking-filtershape) property. Default configuration is the following:
+Use the [`filterShape`](api/config/booking-filtershape.md) property to control which filter inputs appear and how each behaves. The default configuration enables three text fields, a date picker, and three time ranges:
 
 ~~~jsx {}
 const defaultTimeRanges = [
@@ -525,11 +561,11 @@ const defaultFilterShape = {
 };
 ~~~
 
-### Hiding filter input fields
+### Hide filter input fields
 
-All input fields are displayed by default: text, time, and date. To hide the fields, apply the [`filterShape`](/api/config/booking-filtershape) property and set the corresponding parameters to **false**.
+The widget displays all input fields by default — text, time, and date. To hide a field, set the corresponding parameter of the [`filterShape`](api/config/booking-filtershape.md) property to `false`.
 
-Example:
+The following code snippet hides the date filter:
 
 ~~~jsx {}
 const filterShape = {
@@ -543,11 +579,11 @@ new booking.Booking("#root", {
 });
 ~~~
 
-### Configuring filter fields
+### Configure text filter fields
 
-To enable the auto-complete and show the values that match a user's input text in the **text** field, set the `suggest` parameter of the [`filterShape`](/api/config/booking-filtershape) property to **true**. The values from the [`data`](/api/config/booking-data) object will be displayed. To add labels to these fields, apply the `label` parameter of the [`filterShape`](/api/config/booking-filtershape) property. 
+To enable auto-complete in a text field, set the `suggest` parameter to `true`. The widget then displays values from the [`data`](api/config/booking-data.md) array that match the user's input. Use the `label` parameter to add a placeholder.
 
-Example:
+The following code snippet enables auto-complete and custom labels for three text fields:
 
 ~~~jsx {}
 const filterShape = {
@@ -561,18 +597,19 @@ const filterShape = {
 new booking.Booking("#root", {
     data,
     filterShape,
-    //other parameters
+    // other parameters
 });
 ~~~
 
-To define the time filtering options, for the `time` parameter of the [`filterShape`](/api/config/booking-filtershape) property specify the start and end slot time values:
+### Configure time ranges
 
-- `from` - the start time for a slot; it can be a number from 0 to 24 that specifies the time in hours (e.g., 9 means 9:00, 8.5 means 8:30) or a string in the format "h:m" (for example, "8:30")
-- `to` - the end time for a slot; it can be a number from 0 to 24 that specifies the time in hours (e.g., 9 means 9:00, 8.5 means 8:30) or a string in the format "h:m" (for example, "8:30")
+To define time filtering options, pass an array of objects to the `time` parameter of the [`filterShape`](api/config/booking-filtershape.md) property. Each object accepts the following keys:
 
-And you can also add a placeholder to each time range.
+- `from` — slot start time, as a number from 0 to 24 (for example, `9` means 9:00, `8.5` means 8:30) or a string in the `"h:m"` format (for example, `"8:30"`)
+- `to` — slot end time, in the same format as `from`
+- `label` — placeholder for the time range
 
-Example:
+The following code snippet defines four time ranges with custom labels:
 
 ~~~jsx {}
 const filterShape = {
@@ -591,11 +628,11 @@ new booking.Booking("#root", {
 });
 ~~~
 
-### Enabling the autoApply mode for the filter
+### Enable autoApply mode
 
-To hide the **Search** button and make the filter immediately apply a user's input, set the `autoApply` parameter of the [`filterShape`](/api/config/booking-filtershape) property to **true**.
+To hide the **Search** button and apply filter input immediately, set the `autoApply` parameter of the [`filterShape`](api/config/booking-filtershape.md) property to `true`.
 
-Example:
+The following code snippet enables auto-apply for the filter:
 
 ~~~jsx {}
 const filterShape = {
@@ -609,8 +646,22 @@ new booking.Booking("#root", {
 });
 ~~~
 
-### Example
+### Filter example
 
-The snippet below demonstrates how to configure the filter:
+The snippet below demonstrates a complete filter configuration:
 
 <iframe src="https://snippet.dhtmlx.com/b5uj78bs?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
+
+## Optimize rendering of large datasets
+
+The Booking widget renders every loaded card by default. For large datasets, enable lazy rendering so the widget renders only visible cards. Use the [`renderType`](api/config/booking-rendertype.md) property to switch between modes.
+
+The following code snippet enables lazy rendering of cards:
+
+~~~jsx {}
+new booking.Booking("#root", {
+    data,
+    renderType: "lazy",
+    // other parameters
+});
+~~~
diff --git a/docs/guides/initialization.md b/docs/guides/initialization.md
index 8aef4a1..999a03a 100644
--- a/docs/guides/initialization.md
+++ b/docs/guides/initialization.md
@@ -6,42 +6,48 @@ description: You can learn about the initialization in the documentation of the
 
 # Initialization
 
-This guide will give you detailed instructions on how to create Booking on a page to enrich your application with rich features of this tool. Take the following steps to get a ready-to-use component:
+This guide walks you through creating a Booking instance on a page. Take the following steps to get a working component:
 
-1. [Include the Booking source files on a page](#including-source-files).
-2. [Create a container for Booking](#creating-container).
-3. [Initialize Booking with a constructor](#initializing-booking).
+1. [Include the Booking source files](#include-source-files).
+2. [Create a container](#create-a-container).
+3. [Initialize Booking with the constructor](#initialize-booking).
 
-## Including source files
+## Include source files
 
-[Download the package](https://dhtmlx.com/docs/products/dhtmlxBooking/) and unpack it into a folder of your project.
+The Booking widget ships as two files that you load on the page.
 
-To create Booking, you need to include 2 source files on your page:
+[Download the package](https://dhtmlx.com/docs/products/dhtmlxBooking/) and unpack it into a folder of your project. Add the following files to your page:
 
-- *booking.js*
-- *booking.css*
+- *booking.js* — Booking source code
+- *booking.css* — Booking stylesheet
 
-Make sure that you set correct relative paths to the source files:
+Set correct relative paths to the source files.
+
+The following code snippet includes the Booking files from a *dist/* folder:
 
 ~~~html title="index.html"
 <script type="text/javascript" src="./dist/booking.js"></script>  
 <link rel="stylesheet" href="./dist/booking.css">
 ~~~
 
-## Creating container
+## Create a container
+
+Add an HTML element that hosts the Booking widget and assign it an ID, for example *root*.
 
-Add a container for Booking and give it an ID, for example *"root"*:
+The following code snippet creates a container with the ID *root*:
 
 ~~~jsx title="index.html"
 <div id="root"></div>
 ~~~
 
-## Initializing Booking
+## Initialize Booking
+
+Call the `booking.Booking` constructor with two parameters:
 
-Initialize Booking using the **booking.Booking** constructor. It takes two parameters:
+- container — the selector or ID of the HTML container that hosts the widget
+- config — an object with configuration properties (see [Configuration properties](#configuration-properties))
 
-- an HTML container (the ID of the HTML container)
-- an object with configuration properties. [See the full list here](#configuration-properties)
+The following code snippet initializes Booking inside the `#root` container:
 
 ~~~jsx title="index.html"
 // create Booking
@@ -53,11 +59,11 @@ new booking.Booking("#root", {
 ### Configuration properties
 
 :::info
-The full list of properties to configure **Booking** can be found [**here**](api/overview/booking-properties-overview.md).
+For the full list of properties used to configure Booking, see the [Properties overview](api/overview/booking-properties-overview.md).
 :::
 
 ## Example
 
-In this snippet you can see how to initialize **JavaScript Booking** with initial settings:
+The snippet below initializes Booking with a set of initial properties:
 
 <iframe src="https://snippet.dhtmlx.com/6it4ohez?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
diff --git a/docs/guides/integration-with-angular.md b/docs/guides/integration-with-angular.md
index b607b6e..5bbc627 100644
--- a/docs/guides/integration-with-angular.md
+++ b/docs/guides/integration-with-angular.md
@@ -6,82 +6,93 @@ description: You can learn about the integration with Angular in the documentati
 
 # Integration with Angular
 
+DHTMLX Booking integrates with Angular through a custom component that wraps the widget constructor. This guide walks you through scaffolding a new Angular project, installing Booking, and rendering the widget with data and events. For the complete reference implementation, see the [Angular example on GitHub](https://github.com/DHTMLX/angular-booking-demo).
+
 :::tip
-You should be familiar with basic concepts and patterns of **Angular** before reading this documentation. To refresh your knowledge, please refer to the [**Angular documentation**](https://v17.angular.io/docs).
+This guide assumes familiarity with Angular core concepts. For an introduction, see the [Angular documentation](https://v17.angular.io/docs).
 :::
 
-DHTMLX Booking is compatible with **Angular**. We have prepared code examples on how to use DHTMLX Booking with **Angular**. For more information, refer to the corresponding [**Example on GitHub**](https://github.com/DHTMLX/angular-booking-demo).
+## Create a project
 
-## Creating a project
+Scaffold a new Angular app with Angular CLI before adding the Booking integration.
 
 :::info
-Before you start to create a new project, install [**Angular CLI**](https://v17.angular.io/cli) and [**Node.js**](https://nodejs.org/en/).
+Install [Angular CLI](https://v17.angular.io/cli) and [Node.js](https://nodejs.org/en/) before you start.
 :::
 
-Create a new **my-angular-booking-app** project using Angular CLI. Run the following command for this purpose:
+The following command creates a new *my-angular-booking-app* project:
 
 ~~~json
 ng new my-angular-booking-app
 ~~~
 
 :::note
-If you want to follow this guide, disable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering) when creating new Angular app!
+Disable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering) when prompted by the CLI. The Booking widget mounts to the DOM on the client side.
 :::
 
-The command above installs all the necessary tools, so you don't need to run any additional commands.
+The command installs all necessary tools. No additional commands are required.
+
+### Install dependencies
 
-### Installation of dependencies
+Switch to the project directory.
 
-Go to the new created app directory:
+The following command opens the newly created app folder:
 
 ~~~json
 cd my-angular-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use the [**yarn**](https://yarnpkg.com/) package manager:
+Install the dependencies and start the dev server with the [yarn](https://yarnpkg.com/) package manager.
+
+The following commands install dependencies and launch the dev server:
 
 ~~~json
 yarn
 yarn start
 ~~~
 
-The app should run on a localhost (for instance `http://localhost:3000`).
+The app runs on a localhost, for example *http://localhost:3000*.
+
+## Add Booking to the app
 
-## Creating Booking
+Stop the dev server before installing the Booking package, then create an Angular component that wraps the widget.
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+### Step 1. Install the package
 
-### Step 1. Package installation
+Download the [trial Booking package](how-to-start.md#installing-trial-booking-via-npm-or-yarn) and follow the steps in the package README. The trial version stays active for 30 days.
 
-Download the [**trial Booking package**](/how-to-start/#installing-trial-booking-via-npm-or-yarn) and follow steps mentioned in the README file. Note that trial Booking is available 30 days only.
-  
-### Step 2. Component creation
+### Step 2. Create the Booking component
 
-Now you need to create an Angular component, to add Booking into the application. Create  the ***booking*** folder in the ***src/app/*** directory, add a new file into it and name it ***booking.component.ts***. Then complete the steps described below.
+Create a *booking* folder in the *src/app/* directory and add a *booking.component.ts* file inside it. Complete the steps below to wire the widget.
 
-#### Import source files
+#### Import the source files
 
-Open the file and import Booking source files. Note that:
+Import the Booking class with the path that matches your distribution:
 
-- if you use PRO version and install the Booking package from a local folder, the imported path looks like this:
+- *dhx-booking-package* — PRO version installed from a local folder
+- *@dhx/trial-booking* — trial version
+
+The following code snippet imports Booking from the PRO package:
 
 ~~~jsx
 import { Booking } from 'dhx-booking-package';
 ~~~
 
-- if you use the trial version of Booking, specify the following path:
+The following code snippet imports Booking from the trial package:
 
 ~~~jsx
 import { Booking } from '@dhx/trial-booking';
 ~~~
 
 :::info
-In this tutorial you can see how to configure the **trial** version of Booking.
+This tutorial uses the trial version of Booking.
 :::
 
 #### Set the container and initialize Booking
 
-To display Booking on the page, you need to set the container to render the component inside and initialize Booking using the corresponding constructor:
+Define the host container in the component template and instantiate Booking in `ngOnInit()`. Call `destructor()` in `ngOnDestroy()` to unmount the widget when Angular removes the component.
+
+The following code snippet declares a Booking component with a container element and lifecycle hooks:
 
 ~~~jsx {1,8,12-13,18-19} title="booking.component.ts"
 import { Booking } from '@dhx/trial-booking';
@@ -89,37 +100,41 @@ import { Component, ElementRef, OnInit, ViewChild, OnDestroy, ViewEncapsulation
 
 @Component({
     encapsulation: ViewEncapsulation.None,
-    selector: "booking", // a template name used in the "app.component.ts" file as <booking />
-    styleUrls: ["./booking.component.css"], // include a css file
+    selector: "booking", // used in app.component.ts as <booking />
+    styleUrls: ["./booking.component.css"],
     template: `<div #container class="widget"></div>`,
 })
 
 export class BookingComponent implements OnInit, OnDestroy {
-    // initialize container for Booking
+    // host container for Booking
     @ViewChild('container', { static: true }) booking_container!: ElementRef;
 
     private _booking!: Booking;
 
     ngOnInit() {
-        // initialize the Booking component
+        // create the Booking instance
         this._booking = new Booking(this.booking_container.nativeElement, {});
     }
 
     ngOnDestroy(): void {
-        this._booking.destructor(); // destruct Booking
+        this._booking.destructor(); // unmount Booking
     }
 }
 ~~~
 
-#### Adding styles
+#### Add the styles
+
+Booking requires both the widget stylesheet and a sized container.
 
-To display Booking correctly, you need to provide the corresponding styles. For this purpose, you can create the ***booking.component.css*** file in the **src/app/booking/** directory and specify important styles for Booking and its container:
+Create a *booking.component.css* file in the *src/app/booking/* directory.
+
+The following code snippet imports the Booking stylesheet and sets full height for the page and the widget container:
 
 ~~~css title="booking.component.css"
 /* import Booking styles */
 @import "@dhx/trial-booking/dist/booking.css";
 
-/* specify styles for initial page */
+/* page styles */
 html,
 body {
     margin: 0;
@@ -127,15 +142,19 @@ body {
     height: 100%;
 }
 
-/* specify styles for the Booking container */
+/* Booking container */
 .widget {
     height: 100%;
 }
 ~~~
 
-#### Loading data
+#### Load data
+
+To load card data into Booking, prepare a dataset matching the [`data`](api/config/booking-data.md) property. For the full data format and loading scenarios, see the [Loading data](guides/loading-data.md) guide.
 
-To add data into Booking, you need to provide a data set. You can create the ***data.ts*** file in the ***src/app/booking/*** directory and add some data into it:
+Create a *data.ts* file in the *src/app/booking/* directory.
+
+The following code snippet defines a `getData()` helper that returns a sample dataset:
 
 ~~~jsx title="data.ts"
 export function getData() : any {
@@ -218,7 +237,9 @@ export function getData() : any {
 }
 ~~~
 
-Then open the ***booking.component.ts*** file. Import the file with data and specify the corresponding data properties to the configuration object of Booking within the `ngOnInit()` method, as shown below.
+Open *booking.component.ts*, import the dataset, and pass it to the Booking configuration inside `ngOnInit()`.
+
+The following code snippet wires `getData()` into the Booking constructor:
 
 ~~~jsx {2,18,20} title="booking.component.ts"
 import { Booking } from '@dhx/trial-booking';
@@ -238,7 +259,7 @@ export class BookingComponent implements OnInit, OnDestroy {
     private _booking!: Booking;
 
     ngOnInit() {
-        const data = getData(); // initialize data property
+        const data = getData(); // load the dataset
         this._booking = new Booking(this.booking_container.nativeElement, {
             data
         });
@@ -250,22 +271,24 @@ export class BookingComponent implements OnInit, OnDestroy {
 }
 ~~~
 
-Now the Booking component is ready to use. When the element will be added to the page, it will initialize the Booking with data. You can provide necessary configuration settings as well. Visit our [Booking API docs](/api/overview/booking-properties-overview/) to check the full list of available properties.
+The Booking component now renders with the loaded data. To customize the widget further, pass extra configuration properties — see the full list in the [Properties overview](api/overview/booking-properties-overview.md).
 
-#### Handling events
+#### Handle events
 
-When a user makes some action in the Booking, it invokes an event. You can use these events to detect the action and run the desired code for it. See the [full list of events](/api/overview/booking-events-overview/).
+A user action in the widget triggers an event. Subscribe to an event with `booking.api.on(eventName, handler)` to react to the action. For the full list of events, see the [Events overview](api/overview/booking-events-overview.md).
 
-Open the ***booking.component.ts*** file and complete the `ngOnInit()` method as in:
+Open *booking.component.ts* and extend `ngOnInit()` with an event subscription.
+
+The following code snippet logs the slot ID when a user selects a slot:
 
 ~~~jsx {7-10} title="booking.component.ts"
 // ...
 ngOnInit() {
     this._booking = new Booking(this.booking_container.nativeElement, {
-        date: new Date(2024, 5, 10),
+        start: new Date(2024, 5, 10),
     });
 
-    // output the id of the selected slot
+    // log the selected slot id
     this._booking.api.on("select-slot", (obj) => {
         console.log(obj.id);
     });
@@ -276,23 +299,27 @@ ngOnDestroy(): void {
 }
 ~~~
 
-### Step 3. Adding Booking into the app
+### Step 3. Register Booking in the app
+
+Add the `BookingComponent` to the application bootstrap. Open *src/app/app.component.ts* and replace the default code.
 
-To add the ***BookingComponent*** component into the app, open the ***src/app/app.component.ts*** file and replace the default code with the following one:
+The following code snippet renders the Booking component inside `AppComponent`:
 
 ~~~jsx {5} title="app.component.ts"
 import { Component } from "@angular/core";
 
 @Component({
     selector: "app-root",
-    template: `<booking/>` // a template created in the "booking.component.ts" file 
+    template: `<booking/>` // template defined in booking.component.ts
 })
 export class AppComponent {
     name = "";
 }
 ~~~
 
-Then create the ***app.module.ts*** file in the ***src/app/*** directory and specify the *BookingComponent* as shown below:
+Create *app.module.ts* in *src/app/* and declare both components.
+
+The following code snippet registers `AppComponent` and `BookingComponent` in the root module:
 
 ~~~jsx {4-5,8} title="app.module.ts"
 import { NgModule } from "@angular/core";
@@ -309,7 +336,9 @@ import { BookingComponent } from "./booking/booking.component";
 export class AppModule {}
 ~~~
 
-The last step is to open the ***src/main.ts*** file and replace the existing code with the following one:
+Open *src/main.ts* and bootstrap the root module.
+
+The following code snippet starts the application with `AppModule`:
 
 ~~~jsx title="main.ts"
 import { platformBrowserDynamic } from "@angular/platform-browser-dynamic";
@@ -319,8 +348,8 @@ platformBrowserDynamic()
     .catch((err) => console.error(err));
 ~~~
 
-After that, you can start the app to see Booking loaded with data on a page.
+Start the app to see Booking loaded with data on the page.
 
 ![Booking initialization](../assets/trial-booking.png)
 
-Now you know how to integrate DHTMLX Booking with Angular. You can customize the code according to your specific requirements. The final example you can find on [**GitHub**](https://github.com/DHTMLX/angular-booking-demo).
+Customize the code to match your project requirements. The complete reference implementation is available on [GitHub](https://github.com/DHTMLX/angular-booking-demo).
diff --git a/docs/guides/integration-with-eventcalendar.md b/docs/guides/integration-with-eventcalendar.md
index 6c191f7..91c78dc 100644
--- a/docs/guides/integration-with-eventcalendar.md
+++ b/docs/guides/integration-with-eventcalendar.md
@@ -6,56 +6,45 @@ description: You can learn about the integration with DHTMLX Event Calendar in t
 
 # Integration with DHTMLX Event Calendar
 
-This guide will show how to integrate the DHTMLX Booking widget with [DHTMLX Event Calendar](https://docs.dhtmlx.com/eventcalendar/).
+This guide shows how to integrate the DHTMLX Booking widget with [DHTMLX Event Calendar](https://docs.dhtmlx.com/eventcalendar/). The integration converts Event Calendar events into Booking slots on the server side.
 
-## Main concepts
+## Understand the main concepts
 
-The integration primarily focuses on converting the Event Calendar data into Booking slots.
+The integration centers on converting Event Calendar events into Booking slots. Keep the following points in mind before you start.
 
-- **Event Calendar events vs. Booking slots:**
-    - Event Calendar handles events (e.g., single or recurring).
-    - Booking generates available time slots from those events.
+**Event Calendar events vs. Booking slots.** Event Calendar handles events, both single and recurring. Booking generates available time slots from those events. The [snippet below](#example) generates booking slots from a doctor's schedule by converting JSON data on the server side.
 
-So what you actually need is to generate booking slots from events (the [snippet below](#example) shows how to generate booking slots from the doctor's schedule by converting JSON data on server-side).
+**Recurring events limitation.** Booking supports only weekly recurring events, defined as `FREQ=WEEKLY;INTERVAL=1` in Event Calendar. Event Calendar handles any recurrence pattern, so hide the other recurrence options in the Event Calendar form.
 
-- **Recurring events limitation:**
-    - Booking supports only weekly recurring events (defined as INTERVAL=1;FREQ=WEEKLY in Event Calendar).
-    - Event Calendar can handle any recurring pattern so you will need to hide other recurring options from Event calendar form
+**Timezone handling.** Booking interprets timestamps in the local timezone. If you use global timestamps, convert them to the local timezone before sending them to Booking, and back to UTC before saving. For conversion instructions, see [Convert UTC data to the local timezone](guides/saving-reservations.md#convert-utc-data-to-the-local-timezone).
 
-- **Timezone handling:**
-    - Booking interprets timestamps in the local timezone.
-    - If you use global timestamps, you need to convert them to local timezones before sending them to Booking (and vice versa before saving the data back).
-For conversion instructions, refer to [Working with UTC data](/guides/saving-reservations/#working-with-utc-data).
+**Booking slot strategies.** Choose one of two approaches to build the schedule:
 
-- **Booking slot strategies:**
-    - Use `slots` and `usedSlots` to build the schedule, ensuring that used slots are excluded (we'll focus on this strategy)
-    - Use only `availableSlots`, which is suitable for events without recurrences.
+- [`slots`](api/config/booking-data.md) and [`usedSlots`](api/config/booking-data.md) — build the schedule and exclude booked slots (the strategy covered here)
+- [`availableSlots`](api/config/booking-data.md) — list bookable slots explicitly, suitable for events without recurrences
 
-## Example 
+## Example
 
-The snippet below demonstrates how to integrate Booking with the Event Calendar widget by converting doctors' schedules into booking slots. Key data endpoints used for integration:
+The snippet below integrates Booking with Event Calendar by converting doctors' schedules into booking slots. The integration uses four data endpoints:
 
-- `/events` - Event Calendar data (doctor schedules) that includes recurring and single-time events. These events are used to create time slots for the Booking system.
+- `/events` — Event Calendar data (doctor schedules) with recurring and single events; the source for Booking time slots
+- `/units` — final Booking slots generated from the `/events` data on the server side; see the [backend example](https://github.com/DHTMLX/event-calendar-booking-go)
+- `/calendars` — doctors' calendars; supplies doctor information to both the Event Calendar and Booking widgets
+- `/reservations` — auxiliary collection that visualizes `usedSlots` in the timeline view; holds already reserved slots from the Booking form
 
-- `/units` - final Booking slots generated from the Event Calendar `events` data. The slots are generated on the server-side. Please, also refer to [backend](https://github.com/DHTMLX/event-calendar-booking-go).
-
-- `/calendars` - contains doctors' calendars. It is used for displaying doctor information in both the Event Calendar and Booking widgets.
-
-- `/reservations` - an auxiliary collection used to visualize `usedSlots` in the timeline view. This data comes from the Booking form, containing information about already reserved slots for doctors.
-
-Converting events to Booking slots is the major part of integration and the rules for handling the events and converting them to slots are described in the [section below](#rules-for-converting-events-to-booking-slots).
+Event-to-slot conversion is the core of the integration. The [next section](#convert-events-to-booking-slots) describes the conversion rules.
 
 <iframe src="https://snippet.dhtmlx.com/c5eu8pdk?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="800"></iframe>
 
-## Rules for converting events to Booking slots
+## Convert events to Booking slots
 
-We will show how to generate booking slots from the doctor's schedule/calendars using JSON data. Data is converted on the the server-side. In all example below the schedule for the next period is considered: from 2025-03-13 to 2027-03-13. 
+The rules below generate booking slots from a doctor's schedule using JSON data, converted on the server side. Every example assumes the schedule for the next period, from 2025-03-13 to 2027-03-13.
 
-**Rule 1. Single event slot creation.**
+### Rule 1. Create a slot from a single event
 
-For each single event in the schedule, convert the start and end times to Booking slots by creating an entry in the slots array, including the corresponding date (dates).
+For each single event, convert the start and end times to a Booking slot. Add an entry to the `slots` array and include the event date in the `dates` array.
 
-Event Calendar event:
+The following code snippet shows a single Event Calendar event:
 
 ~~~json
 {
@@ -65,7 +54,7 @@ Event Calendar event:
 }
 ~~~
 
-Booking slot:
+The following code snippet shows the resulting Booking slot:
 
 ~~~json
 {
@@ -84,11 +73,11 @@ Booking slot:
 }
 ~~~
 
-**Rule 2. Recurring events.**
+### Rule 2. Convert a recurring event
 
-For recurring events, we use a weekly pattern. The start date and end date of each recurring event in Event Calendar should be equal to Booking [start](/api/config/booking-start) and [end](/api/config/booking-end) dates, otherwise create placeholders for dates before and after the recurring event (see Rule 7).
+Map a recurring event to a weekly pattern. The start and end dates of the recurring event in Event Calendar must equal the Booking [`start`](api/config/booking-start.md) and [`end`](api/config/booking-end.md) dates. Otherwise, create placeholders for the dates before and after the recurring event (see [Rule 7](#rule-7-handle-events-that-start-after-the-booking-start-date)).
 
-Event Calendar event (weekly on weekdays): the recurrence rule (rrule) specifies that the event repeats weekly on Monday, Tuesday, Wednesday, Thursday, and Friday.
+The following code snippet shows a recurring Event Calendar event that repeats weekly on weekdays (Monday through Friday):
 
 ~~~json
 {
@@ -102,7 +91,9 @@ Event Calendar event (weekly on weekdays): the recurrence rule (rrule) specifies
 }
 ~~~
 
-Booking slots: In Booking, the weekly schedule is represented as a single rule, with the same start and end times for all recurring events:
+Booking represents the weekly schedule as a single rule, with the same start and end times for every weekday.
+
+The following code snippet shows the resulting Booking slots:
 
 ~~~json
 {
@@ -119,13 +110,13 @@ Booking slots: In Booking, the weekly schedule is represented as a single rule,
 }
 ~~~
 
-**Rule 3. Scheduling an event that spans multiple days.**
+### Rule 3. Split an event that spans multiple days
 
-If an event spans across multiple days (e.g., starts at 8 PM and ends at 4 AM), it should be split into two slots — one for each day.
+Booking generates slots within a single day. If an event spans two days (for example, starts at 8 PM and ends at 4 AM), split it into two slots, one for each day.
 
-For example, when a doctor's shift starts on Saturday evening and lasts into Sunday morning, Booking can only generate slots within one day. In this case, we need to split the event into two separate rules: one for Saturday and another for Sunday.
+For example, a doctor's shift that starts on Saturday evening and lasts into Sunday morning splits into two rules: one for Saturday and one for Sunday.
 
-Event Calendar event:
+The following code snippet shows the multi-day Event Calendar event:
 
 ~~~json
 {
@@ -139,7 +130,7 @@ Event Calendar event:
 }
 ~~~
 
-Booking slots:
+The following code snippet shows the two resulting Booking slots, one per day:
 
 ~~~json
 {
@@ -161,14 +152,16 @@ Booking slots:
 }
 ~~~
 
-**Rule 4. Additional single events added to recurring events.**
+### Rule 4. Add a single event to a recurring schedule
 
-In this case, a single event is added to a recurring schedule. The Booking slots are generated for both the recurring and the single events. The single event dates are added to the recurring event's dates array. 
+When a single event extends a recurring schedule, generate slots for both. Add the single event dates to the recurring rule's `dates` array.
 
-Event Calendar events:
+This example combines two Event Calendar events:
 
-- Recurring event: a doctor’s availability from 9:00 AM to 5:00 PM on weekdays.
-- Single event: a doctor is also available from 2:00 AM to 6:00 AM on March 18th and 19th.
+- recurring event — a doctor's availability from 9:00 AM to 5:00 PM on weekdays
+- single event — extra availability from 2:00 AM to 6:00 AM on March 18 and 19
+
+The following code snippet shows both Event Calendar events:
 
 ~~~json
 [
@@ -196,10 +189,9 @@ Event Calendar events:
 ]
 ~~~
 
-Booking slots:
+Booking merges the recurring event and the single events into one rule. The single event dates (March 18 and 19) carry higher priority and join the recurring rule's `dates` array. For the priority order, see [Define slot rules](guides/configuration.md#define-slot-rules).
 
-- Merging events: the recurring event and single events are combined into one Booking rule.
-- If a single event has priority, its specific dates (March 18th and 19th) are added to the recurring event's rule. Please, refer to [Defining the slot rules](/guides/configuration/#defining-slot-rules)
+The following code snippet shows the merged Booking slots:
 
 ~~~json
 {
@@ -228,11 +220,11 @@ Booking slots:
 }
 ~~~
 
-**Rule 5. Modifying a single instance of a recurring event.**
+### Rule 5. Modify a single instance of a recurring event
 
-If a single instance of a recurring event is edited (e.g., time change for a specific date), generate a new slot with the updated time and date in the dates array, overriding the days array.
+When a single instance of a recurring event changes (for example, a time shift on one date), generate a new slot with the updated time. Add the date to the `dates` array, which overrides the `days` array for that date.
 
-Event Calendar event:
+The following code snippet shows the recurring event and its modified instance:
 
 ~~~json
 [
@@ -256,7 +248,7 @@ Event Calendar event:
 ]
 ~~~
 
-Booking slots:
+The following code snippet shows the recurring rule plus the override for the modified date:
 
 ~~~json
 {
@@ -280,11 +272,11 @@ Booking slots:
 }
 ~~~
 
-**Rule 6. Deleting a single instance of a recurring event.**
+### Rule 6. Delete a single instance of a recurring event
 
-When a single occurrence is removed from a recurring event in Event Calendar, we need to update Booking rules to reflect this removal. This is done by creating a special rule for the removed date, using an empty time interval and the dates property (which has higher priority than days).
+When you remove a single occurrence from a recurring event, reflect the removal in the Booking rules. Create a rule for the removed date with an empty time interval and the `dates` property, which carries higher priority than `days`.
 
-Event Calendar events:
+The following code snippet shows the recurring event and its cancelled occurrence:
 
 ~~~json
 [
@@ -307,7 +299,7 @@ Event Calendar events:
 ]
 ~~~
 
-Booking slots:
+The following code snippet shows the recurring rule plus the empty interval that removes the cancelled date:
 
 ~~~json
 {
@@ -331,11 +323,11 @@ Booking slots:
 }
 ~~~
 
-**Rule 7. Events starting later than Booking start date.**
+### Rule 7. Handle events that start after the Booking start date
 
-If a recurring event starts after the Booking start date (default is today which is 2025-03-13 in all examples), create rules with empty time intervals for the dates prior to the event's start date. This simulates the dates being "removed" from the recurrence.
+If a recurring event starts after the Booking start date (the default is today, 2025-03-13 in these examples), create rules with empty time intervals for the dates before the event's start. This removes those dates from the recurrence.
 
-Event Calendar event:
+The following code snippet shows a recurring event that starts four days after the Booking start date:
 
 ~~~json
 {
@@ -347,10 +339,9 @@ Event Calendar event:
   "STDATE": "2025-03-17T09:00:00Z",
   "DTEND": "2027-03-13T00:00:00Z"
 }
-
 ~~~
 
-Booking slots:
+The following code snippet shows the recurring rule plus empty intervals for the four dates before the event starts:
 
 ~~~json
 {
@@ -369,12 +360,3 @@ Booking slots:
 }
 ~~~
 
-
-
-
-
-
-
-
-
-
diff --git a/docs/guides/integration-with-react.md b/docs/guides/integration-with-react.md
index 9276a6c..52ba58c 100644
--- a/docs/guides/integration-with-react.md
+++ b/docs/guides/integration-with-react.md
@@ -6,76 +6,83 @@ description: You can learn about the integration with React in the documentation
 
 # Integration with React
 
+DHTMLX Booking integrates with React through a wrapper component that mounts the widget inside a ref'd container. This guide walks you through scaffolding a React project, installing Booking, and rendering the widget with data and events. For the complete reference implementation, see the [React example on GitHub](https://github.com/DHTMLX/react-booking-demo).
+
 :::tip
-You should be familiar with the basic concepts and patterns of [**React**](https://react.dev) before reading this documentation. To refresh your knowledge, please refer to the [**React documentation**](https://react.dev/learn).
+This guide assumes familiarity with React core concepts. For an introduction, see the [React documentation](https://react.dev/learn).
 :::
 
-DHTMLX Booking is compatible with **React**. We have prepared code examples on how to use DHTMLX Booking with **React**. For more information, refer to the corresponding [**Example on GitHub**](https://github.com/DHTMLX/react-booking-demo).
+## Create a project
 
-## Creating a project
+Scaffold a React app before adding the Booking integration. Use either Create React App or React with Vite.
 
 :::info
-Before you start to create a new project, install [**Vite**](https://vite.dev/) (optional) and [**Node.js**](https://nodejs.org/en/).
+Install [Vite](https://vite.dev/) (optional) and [Node.js](https://nodejs.org/en/) before you start.
 :::
 
-You can create a basic **React** project or use **React with Vite**. Let's name the project as **my-react-booking-app**:
+The following command creates a new *my-react-booking-app* project with Create React App:
 
 ~~~json
 npx create-react-app my-react-booking-app
 ~~~
 
-### Installation of dependencies
+### Install dependencies
+
+Switch to the project directory.
 
-Go to the new created app directory:
+The following command opens the newly created app folder:
 
 ~~~json
 cd my-react-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use a package manager:
+Install the dependencies and start the dev server with your package manager.
 
-- if you use [**yarn**](https://yarnpkg.com/), run the following commands:
+The following commands use [yarn](https://yarnpkg.com/):
 
 ~~~json
 yarn
 yarn start
 ~~~
 
-- if you use [**npm**](https://www.npmjs.com/), run the following commands:
+The following commands use [npm](https://www.npmjs.com/):
 
 ~~~json
 npm install
-npm run dev
+npm start
 ~~~
 
-The app should run on a localhost (for instance `http://localhost:3000`).
+The app runs on a localhost, for example *http://localhost:3000*.
+
+## Add Booking to the app
 
-## Creating Booking
+Stop the dev server before installing the Booking package, then create a React component that wraps the widget.
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+### Step 1. Install the package
 
-### Step 1. Package installation
+Download the [trial Booking package](how-to-start.md#installing-trial-booking-via-npm-or-yarn) and follow the steps in the package README. The trial version stays active for 30 days.
 
-Download the [**trial Booking package**](/how-to-start/#installing-trial-booking-via-npm-or-yarn) and follow steps mentioned in the README file. Note that trial Booking is available 30 days only.
+### Step 2. Create the Booking component
 
-### Step 2. Component creation
+Create a *Booking.jsx* file in the *src/* directory and complete the steps below to wire the widget.
 
-Now you need to create a React component, to add an Booking into the application. Create a new file in the ***src/*** directory and name it ***Booking.jsx***.
+#### Import the source files
 
-#### Import source files
+Import the Booking class and stylesheet with the path that matches your distribution:
 
-Open the ***Booking.jsx*** file and import Booking source files. Note that:
+- *dhx-booking-package* — PRO version installed from a local folder
+- *@dhx/trial-booking* — trial version
 
-- if you use PRO version and install the Booking package from a local folder, the import paths look like this:
+The following code snippet imports Booking from the PRO package:
 
 ~~~jsx title="Booking.jsx"
 import { Booking } from 'dhx-booking-package';
 import 'dhx-booking-package/dist/booking.css';
 ~~~
 
-Note that depending on the used package, the source files can be minified. In this case make sure that you are importing the CSS file as ***booking.min.css***.
+If your PRO package ships minified assets, import the CSS file as *booking.min.css*.
 
-- if you use the trial version of Booking, specify the following paths:
+The following code snippet imports Booking from the trial package:
 
 ~~~jsx title="Booking.jsx"
 import { Booking } from '@dhx/trial-booking';
@@ -83,27 +90,29 @@ import "@dhx/trial-booking/dist/booking.css";
 ~~~
 
 :::info
-In this tutorial you can see how to configure the **trial** version of Booking.
+This tutorial uses the trial version of Booking.
 :::
 
-#### Setting the container and adding Booking
+#### Set the container and initialize Booking
 
-To display Booking on the page, you need to create the container for Booking, and initialize this component using the corresponding constructor:
+Declare a `ref` for the host container and instantiate Booking inside `useEffect()`. Return a cleanup function that calls `destructor()` to unmount the widget when React unmounts the component.
+
+The following code snippet declares a Booking component with a ref'd container and lifecycle cleanup:
 
 ~~~jsx {2,6,9-10,17} title="Booking.jsx"
 import { useEffect, useRef } from "react";
 import { Booking } from "@dhx/trial-booking";
-import "@dhx/trial-booking/dist/booking.css"; // include Booking styles
+import "@dhx/trial-booking/dist/booking.css"; // import Booking styles
 
 export default function BookingComponent(props) {
-    let container = useRef(); // initialize container for Booking
+    let container = useRef(); // host container for Booking
 
     useEffect(() => {
-        // initialize the Booking component
+        // create the Booking instance
         const booking = new Booking(container.current, {});
 
         return () => {
-            booking.destructor(); // destruct Booking
+            booking.destructor(); // unmount Booking
         };
     }, []);
 
@@ -111,12 +120,14 @@ export default function BookingComponent(props) {
 }
 ~~~
 
-#### Adding styles
+#### Add the styles
+
+Booking requires both the widget stylesheet (imported above) and a sized container. Set full height for the page and the widget container in the main CSS file of the project.
 
-To display Booking correctly, you need to specify important styles for Booking and its container in the main css file of the project:
+The following code snippet sets full height for the page and the Booking container:
 
 ~~~css title="index.css"
-/* specify styles for initial page */
+/* page styles */
 html,
 body,
 #root {
@@ -125,15 +136,19 @@ body,
     margin: 0;
 }
 
-/* specify styles for the Booking container */
+/* Booking container */
 .widget {
     height: 100%;
 }
 ~~~
 
-#### Loading data
+#### Load data
 
-To add data into the Booking, you need to provide a data set. You can create the ***data.js*** file in the ***src/*** directory and add some data into it:
+To load card data into Booking, prepare a dataset matching the [`data`](api/config/booking-data.md) property. For the full data format and loading scenarios, see the [Loading data](guides/loading-data.md) guide.
+
+Create a *data.js* file in the *src/* directory.
+
+The following code snippet defines a `getData()` helper that returns a sample dataset:
 
 ~~~jsx title="data.js"
 export function getData() {
@@ -216,7 +231,9 @@ export function getData() {
 }
 ~~~
 
-Then open the ***App.js*** file and import data. After this you can pass data into the new created `<Booking/>` components as **props**:
+Open *App.js*, import the dataset, and pass the dataset to the `<Booking/>` component as a prop.
+
+The following code snippet renders the Booking component with a `data` prop:
 
 ~~~jsx {2,5-6} title="App.js"
 import Booking from "./Booking";
@@ -230,7 +247,9 @@ function App() {
 export default App;
 ~~~
 
-Go to the ***Booking.jsx*** file and apply the passed **props** to the Booking configuration object:
+Open *Booking.jsx* and forward the `data` prop to the Booking configuration.
+
+The following code snippet wires the prop into the Booking constructor:
 
 ~~~jsx {5,10} title="Booking.jsx"
 import { useEffect, useRef } from "react";
@@ -255,20 +274,22 @@ export default function BookingComponent(props) {
 }
 ~~~
 
-Now the Booking component is ready to use. When the element will be added to the page, it will initialize the Booking with data. You can provide necessary configuration settings as well. Visit our [Booking API docs](/api/overview/booking-properties-overview/) to check the full list of available properties.
+The Booking component now renders with the loaded data. To customize the widget further, pass extra configuration properties — see the full list in the [Properties overview](api/overview/booking-properties-overview.md).
+
+#### Handle events
 
-#### Handling events
+A user action in the widget triggers an event. Subscribe to an event with `booking.api.on(eventName, handler)` to react to the action. For the full list of events, see the [Events overview](api/overview/booking-events-overview.md).
 
-When a user makes some action in the Booking, it invokes an event. You can use these events to detect the action and run the desired code for it. See the [full list of events](/api/overview/booking-events-overview/).
+Open *Booking.jsx* and extend `useEffect()` with an event subscription.
 
-Open ***Booking.jsx*** and complete the `useEffect()` method in the following way:
+The following code snippet logs the slot ID when a user selects a slot:
 
 ~~~jsx {5-8} title="Booking.jsx"
 // ...
 useEffect(() => {
     const booking = new Booking(container.current, {});
 
-    // output the id of the selected slot
+    // log the selected slot id
     booking.api.on("select-slot", (obj) => {
         console.log(obj.id);
     });
@@ -280,8 +301,8 @@ useEffect(() => {
 // ...
 ~~~
 
-After that, you can start the app to see Booking loaded with data on a page.
+Start the app to see Booking loaded with data on the page.
 
 ![Booking initialization](../assets/trial-booking.png)
 
-Now you know how to integrate DHTMLX Booking with React. You can customize the code according to your specific requirements. The final example you can find on [**GitHub**](https://github.com/DHTMLX/react-booking-demo).
+Customize the code to match your project requirements. The complete reference implementation is available on [GitHub](https://github.com/DHTMLX/react-booking-demo).
diff --git a/docs/guides/integration-with-scheduler.md b/docs/guides/integration-with-scheduler.md
index 8ae1aaf..8d72159 100644
--- a/docs/guides/integration-with-scheduler.md
+++ b/docs/guides/integration-with-scheduler.md
@@ -6,53 +6,45 @@ description: You can learn about the integration with DHTMLX Scheduler in the do
 
 # Integration with DHTMLX Scheduler
 
-This guide will show how to integrate the DHTMLX Booking widget with [DHTMLX Scheduler](https://docs.dhtmlx.com/scheduler/). 
+This guide shows how to integrate the DHTMLX Booking widget with [DHTMLX Scheduler](https://docs.dhtmlx.com/scheduler/). The integration converts Scheduler events into Booking slots on the server side.
 
-## Main concepts
+## Understand the main concepts
 
-The integration primarily focuses on converting the Scheduler data into Booking slots.
+The integration centers on converting Scheduler events into Booking slots. Keep the following points in mind before you start.
 
-- **Scheduler events vs. Booking slots:**
-    - Scheduler handles events (e.g., single or recurring).
-    - Booking generates available time slots from those events.
+**Scheduler events vs. Booking slots.** Scheduler handles events, both single and recurring. Booking generates available time slots from those events. The [snippet below](#example) generates booking slots from a doctor's schedule by converting JSON data on the server side.
 
-So what you actually need is to generate booking slots from the schedule (the [snippet below](#example) shows how to generate booking slots from the doctor's schedule by converting JSON data on the server-side).
+**Recurring events limitation.** Booking supports only weekly recurring events, defined as `INTERVAL=1;FREQ=WEEKLY` in Scheduler. Scheduler handles any recurrence pattern, so limit the other recurrence options in the Scheduler config.
 
-- **Recurring events limitation:**
-    - Booking supports only weekly recurring events (defined as INTERVAL=1;FREQ=WEEKLY in Scheduler).
-    - Scheduler can handle any recurring pattern so you will need to limit creating other recurring events in Scheduler config
+**Timezone handling.** Booking interprets timestamps in the local timezone. If you use global timestamps, convert them to the local timezone before sending them to Booking, and back to UTC before saving. For conversion instructions, see [Convert UTC data to the local timezone](guides/saving-reservations.md#convert-utc-data-to-the-local-timezone).
 
-- **Timezone handling:**
-    - Booking interprets timestamps in the local timezone.
-    - If you use global timestamps, you need to convert them to local timezones before sending them to Booking (and vice versa before saving the data back).
-For conversion instructions, refer to [Working with UTC data](/guides/saving-reservations/#working-with-utc-data). 
+**Booking slot strategies.** Choose one of two approaches to build the schedule:
 
-- **Booking slot strategies:**
-    - Use `slots` and `usedSlots` to build the schedule, ensuring that used slots are excluded (we'll focus on this strategy)
-    - Use only `availableSlots`, which is suitable for events without recurrences.
+- [`slots`](api/config/booking-data.md) and [`usedSlots`](api/config/booking-data.md) — build the schedule and exclude booked slots (the strategy covered here)
+- [`availableSlots`](api/config/booking-data.md) — list bookable slots explicitly, suitable for events without recurrences
 
-## Example 
+## Example
 
-The snippet below demonstrates how to integrate Booking with the Scheduler widget by converting doctors' schedules into booking slots. Key data endpoints used for integration:
+The snippet below integrates Booking with Scheduler by converting doctors' schedules into booking slots. The integration uses four data endpoints:
 
-- `/doctors/worktime` - Scheduler data (doctor schedules) that includes recurring and single-time events. These events are used to create time slots for the Booking system.
-- `/units` - final Booking slots generated from the Scheduler `worktime` data. The slots are generated on the server-side. Please, also refer to [backend](https://github.com/DHTMLX/scheduler-booking-go).  
-- `/doctors/reservations` - an auxiliary collection used to visualize `usedSlots` in the timeline view. This data comes from the Booking form, containing information about already reserved slots for doctors.
-- `/doctors` - contains all doctors, including their names and IDs. It is used for displaying doctor information in both the Scheduler and Booking widgets.
+- `/doctors/worktime` — Scheduler data (doctor schedules) with recurring and single events; the source for Booking time slots
+- `/units` — final Booking slots generated from the `worktime` data on the server side; see the [backend example](https://github.com/DHTMLX/scheduler-booking-go)
+- `/doctors/reservations` — auxiliary collection that visualizes `usedSlots` in the timeline view; holds already reserved slots from the Booking form
+- `/doctors` — all doctors with their names and IDs; supplies doctor information to both the Scheduler and Booking widgets
 
-Converting Scheduler events to Booking slots is the major part of integration and the rules for handling the events and converting them to slots are described in the [section below](#rules-for-converting-scheduler-events-to-booking-slots). 
+Event-to-slot conversion is the core of the integration. The [next section](#convert-scheduler-events-to-booking-slots) describes the conversion rules.
 
 <iframe src="https://snippet.dhtmlx.com/d5zbq3g3?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="800"></iframe>
 
-## Rules for converting Scheduler events to Booking slots
+## Convert Scheduler events to Booking slots
 
-We will show how to generate booking slots from the doctor's schedule using JSON data. Data is converted on the server-side. In all example below the schedule for the next period is considered: from 2025-03-13 to 2027-03-13.
+The rules below generate booking slots from a doctor's schedule using JSON data, converted on the server side. Every example assumes the schedule for the next period, from 2025-03-13 to 2027-03-13.
 
-**Rule 1. Single event slot creation.**
+### Rule 1. Create a slot from a single event
 
-For each single event in the schedule, convert the start and end times to Booking slots by creating an entry in the slots array, including the corresponding date (dates).
+For each single event, convert the start and end times to a Booking slot. Add an entry to the `slots` array and include the event date in the `dates` array.
 
-Scheduler event:
+The following code snippet shows a single Scheduler event:
 
 ~~~json
 {
@@ -62,7 +54,7 @@ Scheduler event:
 }
 ~~~
 
-Booking slot:
+The following code snippet shows the resulting Booking slot:
 
 ~~~json
 {
@@ -81,11 +73,11 @@ Booking slot:
 }
 ~~~
 
-**Rule 2. Recurring events.** 
+### Rule 2. Convert a recurring event
 
-For recurring events, we use a weekly pattern. The start date and end date of each recurring event in Scheduler should be equal to Booking [start](/api/config/booking-start) and [end](/api/config/booking-end) dates, otherwise create placeholders for dates before and after the recurring event (see Rule 7).
+Map a recurring event to a weekly pattern. The start and end dates of the recurring event in Scheduler must equal the Booking [`start`](api/config/booking-start.md) and [`end`](api/config/booking-end.md) dates. Otherwise, create placeholders for the dates before and after the recurring event (see [Rule 7](#rule-7-handle-events-that-start-after-the-booking-start-date)).
 
-Scheduler event (weekly on weekdays): the recurrence rule (rrule) specifies that the event repeats weekly on Monday, Tuesday, Wednesday, Thursday, and Friday.
+The following code snippet shows a recurring Scheduler event that repeats weekly on weekdays (Monday through Friday):
 
 ~~~json
 {
@@ -97,7 +89,9 @@ Scheduler event (weekly on weekdays): the recurrence rule (rrule) specifies that
 }
 ~~~
 
-Booking slots: In Booking, the weekly schedule is represented as a single rule, with the same start and end times for all recurring events:
+Booking represents the weekly schedule as a single rule, with the same start and end times for every weekday.
+
+The following code snippet shows the resulting Booking slots:
 
 ~~~json
 {
@@ -114,13 +108,13 @@ Booking slots: In Booking, the weekly schedule is represented as a single rule,
 }
 ~~~
 
-**Rule 3. Scheduling an event that spans multiple days.**
+### Rule 3. Split an event that spans multiple days
 
-If an event spans across multiple days (e.g., starts at 8 PM and ends at 4 AM), it should be split into two slots — one for each day.
+Booking generates slots within a single day. If an event spans two days (for example, starts at 8 PM and ends at 4 AM), split it into two slots, one for each day.
 
-For example, when a doctor's shift starts on Saturday evening and lasts into Sunday morning, Booking can only generate slots within one day. In this case, we need to split the event into two separate rules: one for Saturday and another for Sunday.
+For example, a doctor's shift that starts on Saturday evening and lasts into Sunday morning splits into two rules: one for Saturday and one for Sunday.
 
-Scheduler event:
+The following code snippet shows the multi-day Scheduler event:
 
 ~~~json
 {
@@ -132,7 +126,7 @@ Scheduler event:
 }
 ~~~
 
-Booking slots:
+The following code snippet shows the two resulting Booking slots, one per day:
 
 ~~~json
 {
@@ -154,14 +148,16 @@ Booking slots:
 }
 ~~~
 
-**Rule 4. Additional single events added to recurring events.**
+### Rule 4. Add a single event to a recurring schedule
+
+When a single event extends a recurring schedule, generate slots for both. Add the single event dates to the recurring rule's `dates` array.
 
-In this case, a single event is added to a recurring schedule. The Booking slots are generated for both the recurring and the single events. The single event dates are added to the recurring event's dates array. 
+This example combines two Scheduler events:
 
-Scheduler events:
+- recurring event — a doctor's availability from 9:00 AM to 5:00 PM on weekdays
+- single event — extra availability from 2:00 AM to 6:00 AM on March 18 and 19
 
-- Recurring event: a doctor’s availability from 9:00 AM to 5:00 PM on weekdays.
-- Single event: a doctor is also available from 2:00 AM to 6:00 AM on March 18th and 19th.
+The following code snippet shows both Scheduler events:
 
 ~~~json
 [
@@ -188,10 +184,9 @@ Scheduler events:
 ]
 ~~~
 
-Booking slots:
+Booking merges the recurring event and the single events into one rule. The single event dates (March 18 and 19) carry higher priority and join the recurring rule's `dates` array. For the priority order, see [Define slot rules](guides/configuration.md#define-slot-rules).
 
-- Merging events: the recurring event and single events are combined into one Booking rule.
-- If a single event has priority, its specific dates (March 18th and 19th) are added to the recurring event's rule. Please, refer to [Defining the slot rules](/guides/configuration/#defining-slot-rules)
+The following code snippet shows the merged Booking slots:
 
 ~~~json
 {
@@ -220,11 +215,11 @@ Booking slots:
 }
 ~~~
 
-**Rule 5. Modifying a single instance of a recurring event.**
+### Rule 5. Modify a single instance of a recurring event
 
-If a single instance of a recurring event is edited (e.g., time change for a specific date), generate a new slot with the updated time and date in the dates array, overriding the days array.
+When a single instance of a recurring event changes (for example, a time shift on one date), generate a new slot with the updated time. Add the date to the `dates` array, which overrides the `days` array for that date.
 
-Scheduler event:
+The following code snippet shows the recurring event and its modified instance:
 
 ~~~json
 [
@@ -245,7 +240,7 @@ Scheduler event:
 ]
 ~~~
 
-Booking slots:
+The following code snippet shows the recurring rule plus the override for the modified date:
 
 ~~~json
 {
@@ -269,11 +264,11 @@ Booking slots:
 }
 ~~~
 
-**Rule 6. Deleting a single instance of a recurring event.**
+### Rule 6. Delete a single instance of a recurring event
 
-When a single occurrence is removed from a recurring event in Scheduler, we need to update Booking rules to reflect this removal. This is done by creating a special rule for the removed date, using an empty time interval and the dates property (which has higher priority than days).
+When you remove a single occurrence from a recurring event, reflect the removal in the Booking rules. Create a rule for the removed date with an empty time interval and the `dates` property, which carries higher priority than `days`.
 
-Scheduler events:
+The following code snippet shows the recurring event and its deleted occurrence:
 
 ~~~json
 [
@@ -295,7 +290,7 @@ Scheduler events:
 ]
 ~~~
 
-Booking slots:
+The following code snippet shows the recurring rule plus the empty interval that removes the deleted date:
 
 ~~~json
 {
@@ -319,11 +314,11 @@ Booking slots:
 }
 ~~~
 
-**Rule 7. Events starting later than Booking start date.**
+### Rule 7. Handle events that start after the Booking start date
 
-If a recurring event starts after the Booking start date (default is today which is 2025-03-13 in all examples), create rules with empty time intervals for the dates prior to the event's start date. This simulates the dates being "removed" from the recurrence.
+If a recurring event starts after the Booking start date (the default is today, 2025-03-13 in these examples), create rules with empty time intervals for the dates before the event's start. This removes those dates from the recurrence.
 
-Scheduler event:
+The following code snippet shows a recurring event that starts four days after the Booking start date:
 
 ~~~json
 {
@@ -335,7 +330,7 @@ Scheduler event:
 }
 ~~~
 
-Booking slots:
+The following code snippet shows the recurring rule plus empty intervals for the four dates before the event starts:
 
 ~~~json
 {
@@ -354,12 +349,3 @@ Booking slots:
 }
 ~~~
 
-
-
-
-
-
-
-
-
-
diff --git a/docs/guides/integration-with-svelte.md b/docs/guides/integration-with-svelte.md
index c3564b0..eebb790 100644
--- a/docs/guides/integration-with-svelte.md
+++ b/docs/guides/integration-with-svelte.md
@@ -6,69 +6,76 @@ description: You can learn about the integration with Svelte in the documentatio
 
 # Integration with Svelte
 
+DHTMLX Booking integrates with Svelte through a single-file component that mounts the widget inside a bound container. This guide walks you through scaffolding a Svelte project, installing Booking, and rendering the widget with data and events. For the complete reference implementation, see the [Svelte example on GitHub](https://github.com/DHTMLX/svelte-booking-demo).
+
 :::tip
-You should be familiar with the basic concepts and patterns of **Svelte** before reading this documentation. To refresh your knowledge, please refer to the [**Svelte documentation**](https://svelte.dev/).
+This guide assumes familiarity with Svelte core concepts. For an introduction, see the [Svelte documentation](https://svelte.dev/).
 :::
 
-DHTMLX Booking is compatible with **Svelte**. We have prepared code examples on how to use DHTMLX Booking with **Svelte**. For more information, refer to the corresponding [**Example on GitHub**](https://github.com/DHTMLX/svelte-booking-demo).
+## Create a project
 
-## Creating a project
+Scaffold a Svelte project before adding the Booking integration.
 
 :::info
-Before you start to create a new project, install [**Vite**](https://vite.dev/) (optional) and [**Node.js**](https://nodejs.org/en/).
+Install [Vite](https://vite.dev/) (optional) and [Node.js](https://nodejs.org/en/) before you start.
 :::
 
-To create a **Svelte** JS project, run the following command:
+The following command runs the Vite scaffolding tool:
 
 ~~~json
 npm create vite@latest
 ~~~
 
-Let's name the project as **my-svelte-booking-app**.
+Name the project *my-svelte-booking-app* when prompted.
+
+### Install dependencies
 
-### Installation of dependencies
+Switch to the project directory.
 
-Go to the app directory:
+The following command opens the newly created app folder:
 
 ~~~json
 cd my-svelte-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use a package manager:
+Install the dependencies and start the dev server with your package manager.
 
-- if you use [**yarn**](https://yarnpkg.com/), run the following commands:
+The following commands use [yarn](https://yarnpkg.com/):
 
 ~~~jsx
-yarn 
-yarn start // or yarn dev
+yarn
+yarn dev
 ~~~
 
-- if you use [**npm**](https://www.npmjs.com/), run the following commands:
+The following commands use [npm](https://www.npmjs.com/):
 
 ~~~json
 npm install
 npm run dev
 ~~~
 
-The app should run on a localhost (for instance `http://localhost:3000`).
+The app runs on a localhost, for example *http://localhost:3000*.
+
+## Add Booking to the app
 
-## Creating Booking
+Stop the dev server before installing the Booking package, then create a Svelte component that wraps the widget.
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+### Step 1. Install the package
 
-### Step 1. Package installation
+Download the [trial Booking package](how-to-start.md#installing-trial-booking-via-npm-or-yarn) and follow the steps in the package README. The trial version stays active for 30 days.
 
-Download the [**trial Booking package**](/how-to-start/#installing-trial-booking-via-npm-or-yarn) and follow steps mentioned in the README file. Note that trial Booking is available 30 days only.
+### Step 2. Create the Booking component
 
-### Step 2. Component creation
+Create a *Booking.svelte* file in the *src/* directory and complete the steps below to wire the widget.
 
-Now you need to create a Svelte component, to add Booking into the application. Let's create a new file in the ***src/*** directory and name it ***Booking.svelte***.
+#### Import the source files
 
-#### Import source files
+Import the Booking class and stylesheet with the path that matches your distribution:
 
-Open the ***Booking.svelte*** file and import Booking source files. Note that:
+- *dhx-booking-package* — PRO version installed from a local folder
+- *@dhx/trial-booking* — trial version
 
-- if you use PRO version and install the Booking package from a local folder, the import paths look like this:
+The following code snippet imports Booking from the PRO package:
 
 ~~~html title="Booking.svelte"
 <script>
@@ -77,9 +84,9 @@ import 'dhx-booking-package/dist/booking.css';
 </script>
 ~~~
 
-Note that depending on the used package, the source files can be minified. In this case make sure that you are importing the CSS file as ***booking.min.css***.
+If your PRO package ships minified assets, import the CSS file as *booking.min.css*.
 
-- if you use the trial version of Booking, specify the following paths:
+The following code snippet imports Booking from the trial package:
 
 ~~~html title="Booking.svelte"
 <script>
@@ -89,12 +96,14 @@ import '@dhx/trial-booking/dist/booking.css';
 ~~~
 
 :::info
-In this tutorial you can see how to configure the **trial** version of Booking.
+This tutorial uses the trial version of Booking.
 :::
 
-#### Setting the container and adding Booking
+#### Set the container and initialize Booking
 
-To display Booking on the page, you need to create the container for Booking, and initialize this component using the corresponding constructor:
+Bind the host container with `bind:this` and instantiate Booking inside `onMount()`. Call `destructor()` in `onDestroy()` to unmount the widget when Svelte removes the component.
+
+The following code snippet declares a Booking component with a bound container and lifecycle hooks:
 
 ~~~html {3,6,10-11,19} title="Booking.svelte"
 <script>
@@ -102,45 +111,51 @@ To display Booking on the page, you need to create the container for Booking, an
     import { Booking } from "@dhx/trial-booking";
     import "@dhx/trial-booking/dist/booking.css";
 
-    let container; // initialize container for Booking
+    let container; // host container for Booking
     let booking;
 
     onMount(() => {
-        // initialize the Booking component
+        // create the Booking instance
         booking = new Booking(container, {})
     });
 
     onDestroy(() => {
-        booking.destructor(); // destruct Booking
+        booking.destructor(); // unmount Booking
     });
 </script>
 
 <div bind:this={container} class="widget"></div>
 ~~~
 
-#### Adding styles
+#### Add the styles
+
+Booking requires both the widget stylesheet (imported above) and a sized container. Set full height for the page and the widget container in the main CSS file of the project.
 
-To display Booking correctly, you need to specify important styles for Booking and its container in the main css file of the project:
+The following code snippet sets full height for the page and the Booking container:
 
 ~~~css title="main.css"
-/* specify styles for initial page */
+/* page styles; use the #app root container */
 html,
 body,
-#app { /* make sure that you use the #app root container */
+#app {
     height: 100%;
     padding: 0;
     margin: 0;
 }
 
-/* specify styles for the Booking container */
+/* Booking container */
 .widget {
     height: 100%;
 }
 ~~~
 
-#### Loading data
+#### Load data
 
-To add data into the Booking, we need to provide a data set. You can create the ***data.js*** file in the ***src/*** directory and add some data into it:
+To load card data into Booking, prepare a dataset matching the [`data`](api/config/booking-data.md) property. For the full data format and loading scenarios, see the [Loading data](guides/loading-data.md) guide.
+
+Create a *data.js* file in the *src/* directory.
+
+The following code snippet defines a `getData()` helper that returns a sample dataset:
 
 ~~~jsx title="data.js"
 export function getData() {
@@ -223,7 +238,9 @@ export function getData() {
 }
 ~~~
 
-Then open the ***App.svelte*** file, import data, and pass it into the new created `<Booking/>` components as **props**:
+Open *App.svelte*, import the dataset, and pass the dataset to the `<Booking/>` component as a prop.
+
+The following code snippet renders the Booking component with a `data` prop:
 
 ~~~html {3,5,8} title="App.svelte"
 <script>
@@ -236,7 +253,9 @@ Then open the ***App.svelte*** file, import data, and pass it into the new creat
 <Booking data={dataset} />
 ~~~
 
-Go to the ***Booking.svelte*** file and apply the passed **props** to the Booking configuration object:
+Open *Booking.svelte* and forward the `data` prop to the Booking configuration.
+
+The following code snippet wires the prop into the Booking constructor:
 
 ~~~html {6,13} title="Booking.svelte"
 <script>
@@ -263,13 +282,15 @@ onDestroy(() => {
 <div bind:this={container} class="widget"></div>
 ~~~
 
-Now the Booking component is ready to use. When the element will be added to the page, it will initialize the Booking with data. You can provide necessary configuration settings as well. Visit our [Booking API docs](/api/overview/booking-properties-overview/) to check the full list of available properties.
+The Booking component now renders with the loaded data. To customize the widget further, pass extra configuration properties — see the full list in the [Properties overview](api/overview/booking-properties-overview.md).
+
+#### Handle events
 
-#### Handling events
+A user action in the widget triggers an event. Subscribe to an event with `booking.api.on(eventName, handler)` to react to the action. For the full list of events, see the [Events overview](api/overview/booking-events-overview.md).
 
-When a user makes some action in the Booking, it invokes an event. You can use these events to detect the action and run the desired code for it. See the [full list of events](/api/overview/booking-events-overview/).
+Open *Booking.svelte* and extend `onMount()` with an event subscription.
 
-Open ***Booking.svelte*** and complete the `onMount()` method in the following way:
+The following code snippet logs the slot ID when a user selects a slot:
 
 ~~~html {8-11} title="Booking.svelte"
 <script>
@@ -279,7 +300,7 @@ let booking;
 onMount(() => {
     booking = new Booking(container, {})
 
-    // output the id of the selected slot
+    // log the selected slot id
     booking.api.on("select-slot", (obj) => {
         console.log(obj.id);
     });
@@ -293,8 +314,8 @@ onDestroy(() => {
 // ...
 ~~~
 
-After that, you can start the app to see Booking loaded with data on a page.
+Start the app to see Booking loaded with data on the page.
 
 ![Booking initialization](../assets/trial-booking.png)
 
-Now you know how to integrate DHTMLX Booking with Svelte. You can customize the code according to your specific requirements. The final example you can find on [**GitHub**](https://github.com/DHTMLX/svelte-booking-demo).
+Customize the code to match your project requirements. The complete reference implementation is available on [GitHub](https://github.com/DHTMLX/svelte-booking-demo).
diff --git a/docs/guides/integration-with-vue.md b/docs/guides/integration-with-vue.md
index 67e2f3d..47a703d 100644
--- a/docs/guides/integration-with-vue.md
+++ b/docs/guides/integration-with-vue.md
@@ -6,71 +6,76 @@ description: You can learn about the integration with Vue in the documentation o
 
 # Integration with Vue
 
+DHTMLX Booking integrates with Vue 3 through a single-file component that mounts the widget inside a `ref`'d container. This guide walks you through scaffolding a Vue project, installing Booking, and rendering the widget with data and events. For the complete reference implementation, see the [Vue example on GitHub](https://github.com/DHTMLX/vue-booking-demo).
+
 :::tip
-You should be familiar with the basic concepts and patterns of [**Vue**](https://vuejs.org/) before reading this documentation. To refresh your knowledge, please refer to the [**Vue 3 documentation**](https://vuejs.org/guide/introduction.html#getting-started).
+This guide assumes familiarity with Vue 3 core concepts. For an introduction, see the [Vue 3 documentation](https://vuejs.org/guide/introduction.html#getting-started).
 :::
 
-DHTMLX Booking is compatible with **Vue**. We have prepared code examples on how to use DHTMLX Booking with **Vue 3**. For more information, refer to the corresponding [**Example on GitHub**](https://github.com/DHTMLX/vue-booking-demo).
+## Create a project
 
-## Creating a project
+Scaffold a Vue project before adding the Booking integration.
 
 :::info
-Before you start to create a new project, install [**Node.js**](https://nodejs.org/en/).
+Install [Node.js](https://nodejs.org/en/) before you start.
 :::
 
-To create a **Vue** project, run the following command:
+The following command runs the official Vue scaffolding tool:
 
 ~~~json
 npm create vue@latest
 ~~~
 
-This command installs and executes `create-vue`, the official **Vue** project scaffolding tool. Check the details in the [Vue.js Quick Start](https://vuejs.org/guide/quick-start.html#creating-a-vue-application).
+The command installs and executes `create-vue`. For the prompts and options, see the [Vue.js Quick Start](https://vuejs.org/guide/quick-start.html#creating-a-vue-application). Name the project *my-vue-booking-app* when prompted.
 
-Let's name the project as **my-vue-booking-app**.
+### Install dependencies
 
-### Installation of dependencies
+Switch to the project directory.
 
-Go to the app directory:
+The following command opens the newly created app folder:
 
 ~~~json
 cd my-vue-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use a package manager:
+Install the dependencies and start the dev server with your package manager.
 
-- if you use [**yarn**](https://yarnpkg.com/), run the following commands:
+The following commands use [yarn](https://yarnpkg.com/):
 
 ~~~jsx
 yarn
-yarn start // or yarn dev
+yarn dev
 ~~~
 
-- if you use [**npm**](https://www.npmjs.com/), run the following commands:
+The following commands use [npm](https://www.npmjs.com/):
 
 ~~~json
 npm install
 npm run dev
 ~~~
 
-The app should run on a localhost (for instance `http://localhost:3000`).
+The app runs on a localhost, for example *http://localhost:3000*.
+
+## Add Booking to the app
 
-## Creating Booking
+Stop the dev server before installing the Booking package, then create a Vue component that wraps the widget.
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+### Step 1. Install the package
 
-### Step 1. Package installation
+Download the [trial Booking package](how-to-start.md#installing-trial-booking-via-npm-or-yarn) and follow the steps in the package README. The trial version stays active for 30 days.
 
-Download the [**trial Booking package**](/how-to-start/#installing-trial-booking-via-npm-or-yarn) and follow steps mentioned in the README file. Note that trial Booking is available 30 days only.
+### Step 2. Create the Booking component
 
-### Step 2. Component creation
+Create a *Booking.vue* file in the *src/components/* directory and complete the steps below to wire the widget.
 
-Now you need to create a Vue component, to add Booking into the application. Create a new file in the ***src/components/*** directory and name it ***Booking.vue***.
+#### Import the source files
 
-#### Import source files
+Import the Booking class and stylesheet with the path that matches your distribution:
 
-Open the ***Booking.vue*** file and import Booking source files. Note that:
+- *dhx-booking-package* — PRO version installed from a local folder
+- *@dhx/trial-booking* — trial version
 
-- if you use PRO version and install the Booking package from a local folder, the import paths look like this:
+The following code snippet imports Booking from the PRO package:
 
 ~~~html title="Booking.vue"
 <script>
@@ -79,24 +84,26 @@ import 'dhx-booking-package/dist/booking.css';
 </script>
 ~~~
 
-Note that depending on the used package, the source files can be minified. In this case make sure that you are importing the CSS file as ***booking.min.css***.
+If your PRO package ships minified assets, import the CSS file as *booking.min.css*.
 
-- if you use the trial version of Booking, specify the following paths:
+The following code snippet imports Booking from the trial package:
 
 ~~~html title="Booking.vue"
 <script>
 import { Booking } from '@dhx/trial-booking';
 import '@dhx/trial-booking/dist/booking.css';
-<script>
+</script>
 ~~~
 
 :::info
-In this tutorial you can see how to configure the **trial** version of Booking.
+This tutorial uses the trial version of Booking.
 :::
 
-#### Setting the container and adding Booking
+#### Set the container and initialize Booking
+
+Declare the host container in the template and instantiate Booking in the `mounted()` hook. Call `destructor()` in `unmounted()` to unmount the widget when Vue removes the component.
 
-To display Booking on the page, you need to create the container for Booking, and initialize this component using the corresponding constructor:
+The following code snippet declares a Booking component with a ref'd container and lifecycle hooks:
 
 ~~~html {2,7-8,18} title="Booking.vue"
 <script>
@@ -105,12 +112,12 @@ import "@dhx/trial-booking/dist/booking.css";
 
 export default {
     mounted() {
-        // initialize the Booking component
+        // create the Booking instance
         this.booking = new Booking(this.$refs.container, {});
     },
 
     unmounted() {
-        this.booking.destructor(); // destruct Booking
+        this.booking.destructor(); // unmount Booking
     }
 };
 </script>
@@ -120,29 +127,35 @@ export default {
 </template>
 ~~~
 
-#### Adding styles
+#### Add the styles
+
+Booking requires both the widget stylesheet (imported above) and a sized container. Set full height for the page and the widget container in the main CSS file of the project.
 
-To display Booking correctly, you need to specify important styles for Booking and its container in the main css file of the project:
+The following code snippet sets full height for the page and the Booking container:
 
 ~~~css title="main.css"
-/* specify styles for initial page */
+/* page styles — use the #app root container */
 html,
 body,
-#app { /* make sure that you use the #app root container */
+#app {
     height: 100%;
     padding: 0;
     margin: 0;
 }
 
-/* specify styles for the Booking container */
+/* Booking container */
 .widget {
     height: 100%;
 }
 ~~~
 
-#### Loading data
+#### Load data
 
-To add data into the Booking, you need to provide a data set. You can create the ***data.js*** file in the ***src/*** directory and add some data into it:
+To load card data into Booking, prepare a dataset matching the [`data`](api/config/booking-data.md) property. For the full data format and loading scenarios, see the [Loading data](guides/loading-data.md) guide.
+
+Create a *data.js* file in the *src/* directory.
+
+The following code snippet defines a `getData()` helper that returns a sample dataset:
 
 ~~~jsx title="data.js"
 export function getData() {
@@ -225,7 +238,9 @@ export function getData() {
 }
 ~~~
 
-Then open the ***App.vue*** file, import data, and initialize it via the inner `data()` method. After this you can pass data into the new created `<Booking/>` component as **props**:
+Open *App.vue*, import the dataset, expose it through the `data()` option, and pass the dataset to the `<Booking/>` component as a prop.
+
+The following code snippet renders the Booking component with a `data` prop:
 
 ~~~html {3,7-10,15} title="App.vue"
 <script>
@@ -246,7 +261,9 @@ export default {
 </template>
 ~~~
 
-Go to the ***Booking.vue*** file and apply the passed **props** to the Booking configuration object:
+Open *Booking.vue* and forward the `data` prop to the Booking configuration.
+
+The following code snippet wires the prop into the Booking constructor:
 
 ~~~html {6,10} title="Booking.vue"
 <script>
@@ -257,7 +274,7 @@ export default {
     props: ["data"],
 
     mounted() {
-        this.booking = new Booking(this.$refs.container, {,
+        this.booking = new Booking(this.$refs.container, {
             data: this.data,
             // other configuration properties
         });
@@ -274,13 +291,15 @@ export default {
 </template>
 ~~~
 
-Now the Booking component is ready to use. When the element will be added to the page, it will initialize the Booking with data. You can provide necessary configuration settings as well. Visit our [Booking API docs](/api/overview/booking-properties-overview/) to check the full list of available properties.
+The Booking component now renders with the loaded data. To customize the widget further, pass extra configuration properties — see the full list in the [Properties overview](api/overview/booking-properties-overview.md).
+
+#### Handle events
 
-#### Handling events
+A user action in the widget triggers an event. Subscribe to an event with `booking.api.on(eventName, handler)` to react to the action. For the full list of events, see the [Events overview](api/overview/booking-events-overview.md).
 
-When a user makes some action in the Booking, it invokes an event. You can use these events to detect the action and run the desired code for it. See the [full list of events](/api/overview/booking-events-overview/).
+Open *Booking.vue* and extend `mounted()` with an event subscription.
 
-Open ***Booking.vue*** and complete the `mounted()` method:
+The following code snippet logs the slot ID when a user selects a slot:
 
 ~~~html {8-11} title="Booking.vue"
 <script>
@@ -290,8 +309,8 @@ export default {
     mounted() {
         this.booking = new Booking(this.$refs.container, {});
 
-        // output the id of the selected slot
-        booking.api.on("select-slot", (obj) => {
+        // log the selected slot id
+        this.booking.api.on("select-slot", (obj) => {
             console.log(obj.id);
         });
     }
@@ -302,8 +321,8 @@ export default {
 <!--...-->
 ~~~
 
-After that, you can start the app to see Booking loaded with data on a page.
+Start the app to see Booking loaded with data on the page.
 
 ![Booking initialization](../assets/trial-booking.png)
 
-Now you know how to integrate DHTMLX Booking with Vue. You can customize the code according to your specific requirements. The final example you can find on [**GitHub**](https://github.com/DHTMLX/vue-booking-demo).
+Customize the code to match your project requirements. The complete reference implementation is available on [GitHub](https://github.com/DHTMLX/vue-booking-demo).
diff --git a/docs/guides/loading-data.md b/docs/guides/loading-data.md
index 80ebb29..e0f858b 100644
--- a/docs/guides/loading-data.md
+++ b/docs/guides/loading-data.md
@@ -6,11 +6,19 @@ description: You can learn how to load data into Booking in the documentation of
 
 # Loading data
 
-The following information can be loaded into Booking:
+The Booking widget accepts a single dataset through the configuration object:
 
-- [`data`](/api/config/booking-data) - an array of objects containing cards data 
+- [`data`](api/config/booking-data.md) — array of card objects with slot rules
 
-You can prepare data in a separate file. Here is an example of an appropriate data set:
+:::tip
+For large datasets, enable lazy rendering with the [`renderType`](api/config/booking-rendertype.md) property so the widget renders only visible cards.
+:::
+
+## Prepare a sample dataset
+
+Keep card data in a separate file to share the dataset across pages and tests. Each card object includes identifying fields, display fields, and a `slots` array that defines availability rules.
+
+The following code snippet defines three card objects in a *data.js* module:
 
 ~~~jsx title="data.js"
 const data = [
@@ -91,11 +99,11 @@ const data = [
 ];
 ~~~
 
-You can load JSON data into Booking from an external file or the server-side script after the component has been initialized.
+## Load data from a local file
 
-To load local data from a separate file, first prepare the source file with data.
+Load card data from a separate JavaScript file by exposing the dataset through a helper function.
 
-Example:
+The following code snippet defines `getData()`, which returns both `data` and a `cardShape` config:
 
 ~~~jsx {}
 function getData() {
@@ -129,7 +137,7 @@ const data = [
             }
         ]
     },
-    //other data
+    // other cards
 ];
 
 const cardShape = {
@@ -143,7 +151,9 @@ const cardShape = {
 };
 ~~~
 
-Second, add the path to the source data file:
+Include the data file on the page after the Booking source files.
+
+The following code snippet wires the *data.js* module into *index.html*:
 
 ~~~html title="index.html"
 <script type="text/javascript" src="./dist/booking.js"></script>  
@@ -152,20 +162,37 @@ Second, add the path to the source data file:
 <script src="./common/data.js"></script>
 ~~~
 
-Create Booking and load data:
+Pass the dataset returned by `getData()` to the Booking constructor.
+
+The following code snippet creates a Booking instance with the loaded data:
 
 ~~~jsx {}
 const { data } = getData();
-const booking = new booking.Booking("#root", { data });
+const widget = new booking.Booking("#root", { data });
+~~~
+
+## Update data after initialization
+
+To replace the dataset after Booking is initialized, call the [`setConfig()`](api/methods/booking-setconfig-method.md) method with a new `data` array. The method re-initializes the widget with the merged configuration.
+
+The following code snippet fetches a fresh dataset from the server and applies it to the existing Booking instance:
+
+~~~jsx {}
+fetch("/api/cards")
+    .then(res => res.json())
+    .then(data => {
+        widget.setConfig({ data });
+    });
 ~~~
 
-About loading data from the server, refer to [Working with server](/guides/saving-reservations)
+For server-side persistence of bookings, see the [Saving reservations to the server](guides/saving-reservations.md) guide.
 
 ---
 
 **Related articles**:
-- [confirm-slot](/api/events/booking-confirmslot-event) event
-- [setConfig()](/api/methods/booking-setconfig-method) method
-- [setConfirmHandler()](/api/methods/booking-setconfirmhandler-method) method
-- [renderType](/api/config/booking-rendertype) property
-- [Saving slots reservations to the server](/guides/saving-reservations)
+
+- [`confirm-slot`](api/events/booking-confirmslot-event.md) — handle slot booking confirmation
+- [`setConfig()`](api/methods/booking-setconfig-method.md) — update the widget configuration after initialization
+- [`setConfirmHandler()`](api/methods/booking-setconfirmhandler-method.md) — define the slot confirmation handler
+- [`renderType`](api/config/booking-rendertype.md) — switch between default and lazy rendering
+- [Saving reservations to the server](guides/saving-reservations.md) — persist bookings server-side
diff --git a/docs/guides/localization.md b/docs/guides/localization.md
index 81482b8..030ff87 100644
--- a/docs/guides/localization.md
+++ b/docs/guides/localization.md
@@ -6,11 +6,13 @@ description: You can learn about the localization in the documentation of the DH
 
 # Localization
 
-You can localize labels in the interface of JavaScript Booking and present it in any necessary language. You just need to provide localized strings for labels and apply your locale to the component.
+Localize the Booking interface by providing translated strings for all labels and applying the locale to the widget. The Booking widget ships with three built-in locales and supports custom ones through the [`locale`](api/config/booking-locale.md) property and the [`setLocale()`](api/methods/booking-setlocale-method.md) method.
 
 ## Default locale
 
-The English locale is applied by default:
+Booking applies the English (`en`) locale by default.
+
+The following code snippet shows the full structure of the built-in `en` locale:
 
 ~~~jsx {}
 const en = {
@@ -128,12 +130,14 @@ const en = {
 ~~~
 
 :::info
-Besides the ***en*** locale, Booking also includes the built-in ***de*** and ***cn*** locales.
+Besides the `en` locale, Booking includes two more built-in locales — `de` (German) and `cn` (Chinese).
 :::
 
 <details>
 <summary><b>de</b> locale</summary>
 
+The following code snippet shows the full structure of the built-in `de` locale:
+
 ~~~jsx
 const de = {
     // calendar
@@ -255,6 +259,8 @@ const de = {
 <details>
 <summary><b>cn</b> locale</summary>
 
+The following code snippet shows the full structure of the built-in `cn` locale:
+
 ~~~jsx
 const cn = {
     // calendar
@@ -370,70 +376,84 @@ const cn = {
 ~~~
 </details>
 
-## Applying locales
+## Apply a built-in locale
 
-You can get access to the built-in locale via the *booking* object. Booking provides three built-in locales: en, cn, de.
+Access built-in locales through the `booking.locales` object. Booking provides three built-in locales: `en`, `cn`, and `de`.
 
-Example:
+The following code snippet applies the German locale at initialization through the [`locale`](api/config/booking-locale.md) property:
 
 ~~~jsx {4}
 const { data } = getData();
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data,
     locale: booking.locales.de
 });
 ~~~
 
-You can also apply the [`setLocale()`](/api/methods/booking-setlocale-method) method.
+To change the locale after initialization, call the [`setLocale()`](api/methods/booking-setlocale-method.md) method.
 
-To apply a custom locale, you need to:
+## Apply a custom locale
 
-- create a custom locale object (or modify the default one) and provide translations for all text labels (it can be any language you need)
-- apply the new locale via its [`locale`](/api/config/booking-locale) property or use the [`setLocale()`](/api/methods/booking-setlocale-method) method
+To use a language outside the built-in set, create a locale object with translations for every label and apply it through the [`locale`](api/config/booking-locale.md) property or the [`setLocale()`](api/methods/booking-setlocale-method.md) method.
+
+The following code snippet applies a custom Korean locale to an existing Booking instance:
 
 ~~~jsx {}
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
   data,
 });
 
-const ko = {...} // object with locale
-booking.setLocale(ko);
+const ko = {...} // custom locale object
+widget.setLocale(ko);
+~~~
+
+## Reset to the default locale
+
+To restore the default English locale, call [`setLocale()`](api/methods/booking-setlocale-method.md) without arguments or pass `null`.
+
+The following code snippet resets the active locale to English:
+
+~~~jsx {}
+widget.setLocale();     // reset to default English
+// or
+widget.setLocale(null); // same effect
 ~~~
 
-## Changing the time format
+## Change the time format
+
+Switch between 12-hour and 24-hour time by updating the `timeFormat` parameter inside the `formats` object of the active [`locale`](api/config/booking-locale.md).
 
-You can change the time format via the `timeFormat` parameter of the `formats` object of [locale](/api/config/booking-locale). 
+The following code snippet toggles the active locale between 12-hour and 24-hour formats:
 
 ~~~jsx {}
 let clockFormat = 12;
 const locale = booking.locales["en"];
 setTimeFormat(clockFormat);
 
-function setTimeFormat(clock){
+function setTimeFormat(clock) {
     locale.formats.timeFormat = clock === 12 ? "%g:%i %a" : "%H:%i";
 }
 
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     locale, 
     data: dataset,
 });
 
 function changeFormat() {
-    clockFormat = clockFormat === 12 ? 24  : 12;
+    clockFormat = clockFormat === 12 ? 24 : 12;
     setTimeFormat(clockFormat);
-    booking.setLocale(locale);
-       
+    widget.setLocale(locale);
 }
 ~~~
 
 :::info
-You can also see an example in the [snippet tool](https://snippet.dhtmlx.com/rxjnw54x)
+See an example in the [snippet tool](https://snippet.dhtmlx.com/rxjnw54x).
 :::
 
-## Date and time format specification 
+## Date and time format specification
 
-Booking uses the following characters for setting the date and time format:
+Booking uses the following characters to compose date and time format strings:
 
 | Character | Definition                                        |Example                  |
 | :-------- | :------------------------------------------------ |:------------------------|
@@ -452,22 +472,23 @@ Booking uses the following characters for setting the date and time format:
 | %g        | hours 12-format                                   | from 1 to 12            |
 | %H        | hours 24-format with leading zero                 | from 00 to 23           |
 | %G        | hours 24-format                                   | from 0 to 23            |
-| %i        | minutes with leading zero                         | from 01 to 59           |
-| %s        | seconds with leading zero                         | from 01 to 59           |
+| %i        | minutes with leading zero                         | from 00 to 59           |
+| %s        | seconds with leading zero                         | from 00 to 59           |
 | %S        | milliseconds                                      | 128                     |
 | %a        | am or pm                                          | am (for time from midnight until noon) and pm (for time from noon until midnight)|
 | %A        | AM or PM                                          | AM (for time from midnight until noon) and PM (for time from noon until midnight)|
 | %c        | displays date and time in the ISO 8601 date format| 2024-10-04T05:04:09     |
 
 
-To present the 20th of June, 2024 with the exact time as *2024-09-20 16:47:08.128*, specify "%Y-%m-%d-%H:%i:%s.%u".
+To render the 20th of September, 2024 with the exact time as *2024-09-20 16:47:08.128*, specify `"%Y-%m-%d %H:%i:%s.%S"`.
 
 ## Example
 
-In this snippet you can see how to switch between the *EN* and *DE* locales:
+The snippet below switches between the `en` and `de` locales:
 
 <iframe src="https://snippet.dhtmlx.com/7khy4ayf?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
 **Related articles**:
-- [locale](/api/config/booking-locale)
-- [setLocale()](/api/methods/booking-setlocale-method)
+
+- [`locale`](api/config/booking-locale.md) — set the active locale at initialization
+- [`setLocale()`](api/methods/booking-setlocale-method.md) — change or reset the active locale at runtime
diff --git a/docs/guides/saving-reservations.md b/docs/guides/saving-reservations.md
index 5ab7f1b..c6bdd42 100644
--- a/docs/guides/saving-reservations.md
+++ b/docs/guides/saving-reservations.md
@@ -6,40 +6,54 @@ description: You can learn about working with server in the documentation of the
 
 # Working with server
 
-## Loading data 
+The Booking widget integrates with a backend through two main operations: loading cards data from the server and posting slot reservations back to the server. This guide covers both flows and the UTC conversion needed when server data uses a different timezone.
 
-To get server data, you can send the request for data using the native **fetch** method (or any other way):
+## Load data from the server
+
+Fetch card data with the native `fetch` API (or any equivalent HTTP client) and pass the parsed JSON to the widget through the [`setConfig()`](api/methods/booking-setconfig-method.md) method.
+
+The following code snippet initializes an empty Booking instance and loads the dataset once the response arrives:
 
 ~~~jsx {}
-const booking = new booking.Booking("#booking", {data: []});
+const widget = new booking.Booking("#booking", { data: [] });
 const server = "https://some-backend-url";
 
-fetch(server + "/data").then((res) => res.json()).then((data) => { 
-    booking.setConfig({data});
-});
+fetch(server + "/data")
+    .then((res) => res.json())
+    .then((data) => {
+        widget.setConfig({ data });
+    });
 ~~~
 
-## Saving slots reservations to the server
+## Save slot reservations to the server
+
+To process slot reservations on the backend, register a confirmation handler with the [`setConfirmHandler()`](api/methods/booking-setconfirmhandler-method.md) method.
+
+The handler receives an event object with three fields:
+
+- `slot` — booked slot: `id` (card ID) and `time` (`[timestamp, duration]`)
+- `data` — form values keyed by [`formShape`](api/config/booking-formshape.md) field IDs (defaults: `name`, `email`, `description`)
+- `confirm` — server-response callbacks: `done()` on success, `error()` on failure
 
-To handle slots reservation, you should apply the [`setConfirmHandler`](/api/methods/booking-setconfirmhandler-method) method. 
+The following code snippet posts the reservation to the server and resolves the booking based on the response:
 
 ~~~jsx {}
-// create a function to handle the logic of reservation
+// handle the reservation logic
 const handleSlotReservation = (event) => {
     const { confirm, slot, data } = event;
 
-    // create the info object 
+    // build the payload
     const info = {
         item: slot.id,
         start: slot.time[0],
         data
     };
 
-    // send the POST request to the server with the info object in the request body
+    // post the payload to the server
     fetch("/server/url", {
         method: "POST",
         body: JSON.stringify(info),
-    // handle the response
+    // resolve or reject the booking based on the response
     }).then((response) => {
         if (response.ok) confirm.done();
         else confirm.error();
@@ -47,28 +61,36 @@ const handleSlotReservation = (event) => {
 };
 
 // create Booking
-const booking = new booking.Booking("#root", {
+const widget = new booking.Booking("#root", {
     data: [],
     // configuration parameters
 });
 
-// fetch available data from the server and convert it to JSON
+// fetch the dataset from the server
 fetch("/server/url")
     .then((res) => res.json())        
     .then((items) => {
-        // update Booking configuration with the fetched items, allowing the widget to display them
-        booking.setConfig({ data: items });
-        // assign the handleSlotReservation function to be called when a user confirms booking, 
-        // link user actions to the reservation logic
-        booking.setConfirmHandler(handleSlotReservation);
+        // load the fetched items into the widget
+        widget.setConfig({ data: items });
+        // register the reservation handler
+        widget.setConfirmHandler(handleSlotReservation);
     });
 ~~~
 
-## Working with UTC data
+:::info
+The [`setConfirmHandler()`](api/methods/booking-setconfirmhandler-method.md) method is a shortcut that internally subscribes to the [`confirm-slot`](api/events/booking-confirmslot-event.md) event via `widget.api.on("confirm-slot", handler)`. Both approaches register a handler with the same callback shape — call `widget.api.on("confirm-slot", handler)` directly when you need to add several subscribers.
+:::
+
+## Convert UTC data to the local timezone
+
+The widget operates in the local timezone. If the server returns UTC timestamps, convert each timestamp before passing it into the widget, and convert it back to UTC before posting reservations.
 
-The widget applies a local timezone but if you have UTC data it's necessary to convert data to a local timezone.
+The helpers below handle both directions:
 
-For example, if you have UTC timestamps, you can apply the functions provided in the example below to convert them. The **g2l** function converts a UTC timestamp into the local timezone. During the data loading process, this function is used to convert the times in *usedSlots* and *slots* from UTC to the local time. The **l2g** function converts a local time back to UTC. It's applied during slots reservation, namely, the **l2g** function is used to convert the local time (from slot.time[0]) to UTC before sending it to the server.
+- `g2l` — convert a UTC timestamp to the local timezone (apply on incoming `usedSlots` and `slots.dates`)
+- `l2g` — convert a local timestamp back to UTC (apply on `slot.time[0]` before sending to the server)
+
+The following code snippet combines both helpers in a complete load-and-reserve flow:
 
 ~~~jsx
 const serverURL = "https://some-backend-url";
@@ -153,9 +175,12 @@ fetch( serverURL + "/units")
 
 ## Example
 
+The snippet below demonstrates a full server-side booking flow:
+
 <iframe src="https://snippet.dhtmlx.com/dpbmyr8j?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
 
 **Related articles**:
-- [confirm-slot](/api/events/booking-confirmslot-event) event
-- [setConfig()](/api/methods/booking-setconfig-method) method
-- [setConfirmHandler()](/api/methods/booking-setconfirmhandler-method) method
+
+- [`confirm-slot`](api/events/booking-confirmslot-event.md) — event fired when a user confirms a slot
+- [`setConfig()`](api/methods/booking-setconfig-method.md) — update the widget configuration with fetched data
+- [`setConfirmHandler()`](api/methods/booking-setconfirmhandler-method.md) — register the slot reservation handler
diff --git a/docs/guides/styling.md b/docs/guides/styling.md
index 2bd37d8..f5b8ae5 100644
--- a/docs/guides/styling.md
+++ b/docs/guides/styling.md
@@ -6,44 +6,55 @@ description: You can learn about Styling in the documentation of the DHTMLX Java
 
 # Styling
 
+Customize the Booking widget through CSS custom properties. The widget exposes Booking-specific layout tokens under the `--wx-booking-*` namespace and shares generic design tokens (colors, borders, typography) under the `--wx-*` namespace.
+
 ## Default style
 
+The Booking widget uses CSS custom properties for layout dimensions and shared theme tokens. Override these variables in your own CSS to customize the appearance.
+
+The following code snippet shows a subset of Booking-specific variables exposed by the widget:
+
 ~~~css
-.wx-material-theme {
-    --wx-theme-name: material;
-    --wx-pivot-primary-hover: #194e9e;
-    --wx-pivot-border-color: var(--wx-color-font-disabled);
-    --wx-pivot-field-hover: linear-gradient(
-        rgba(0, 0, 0, 0.1) 0%,
-        rgba(0, 0, 0, 0.1) 100%
-    );
+.wx-booking {
+    --wx-booking-content-min-width: 984px;
+    --wx-booking-content-max-width: 1132px;
+    --wx-booking-content-padding: 0 74px 28px;
+    --wx-booking-slots-width: 602px;
+    --wx-booking-slots-padding: 0 30px 0 50px;
+    --wx-booking-separator: var(--wx-border);
 }
 ~~~
 
 :::tip Note
-Next versions of Booking can bring some changes for the variables and their names. Please, do not forget to check the names after updating to the newer versions and modify them in your code to avoid problems with display of the component.
+Next versions of Booking can bring changes for variable names. Check the names after updating to a newer version and adjust your code to avoid display issues.
 :::
 
-## Built-in theme
+## Apply the built-in theme
+
+The widget provides one built-in theme — the Material theme.
 
-The widget provides one built-in theme which is the **Material** theme. 
+Apply the theme by adding the corresponding CSS class to the widget container.
 
-You can apply the theme via adding the corresponding *CSS* classes to the widget container:
+The following code snippet attaches the Material theme to the Booking container:
 
 ~~~html {}
 <!-- Booking container -->
 <div id="root" class="wx-material-theme"></div>
 ~~~
 
-or just include the theme on the page from the skins folder:
+To load the theme stylesheet from the skins folder, add a link tag on the page.
+
+The following code snippet includes the Material theme stylesheet:
 
 ~~~html {}
-<link type="stylesheet" href="path/to/booking/skins/material.css"/>
+<link rel="stylesheet" href="path/to/booking/skins/material.css"/>
 ~~~
 
-## Customize built-in theme
+## Customize the built-in theme
+
+Override the Material theme variables under the `.wx-material-theme` selector.
 
-The example below demonstrates how to customize the **Material** theme that is applied to Booking:
+The following code snippet recolors the Material theme for a dark layout:
 
 ~~~html
 <style>
@@ -64,9 +75,11 @@ The example below demonstrates how to customize the **Material** theme that is a
 </style>
 ~~~
 
-## Custom styles
+## Apply custom styles
+
+To match your project design, scope the CSS variables under a custom class on the Booking container.
 
-To customize the appearance of Booking to your project needs, you need to apply the corresponding CSS variables. 
+The following code snippet defines a custom palette for the `.demo` container:
 
 ~~~html
 <div id="root" class="demo"></div>
@@ -83,7 +96,7 @@ To customize the appearance of Booking to your project needs, you need to apply
 </style>
 ~~~
 
-The next example shows how to change the background color for cards:
+The following code snippet changes the background color of cards and the date items:
 
 ~~~html
 <style>
@@ -93,7 +106,7 @@ The next example shows how to change the background color for cards:
             background-color: #e8f3f7;
         }
 
-        .wx-booking .wx-slot-dates > .wx-date-item.selected {
+        .wx-booking .wx-slot-dates > .wx-date-item.wx-selected {
             background-color: #bfdde7;
         }
     }
@@ -102,6 +115,6 @@ The next example shows how to change the background color for cards:
 
 ## Example
 
-In this snippet you can see how to apply a custom style to Booking:
+The snippet below demonstrates a custom Booking style:
 
 <iframe src="https://snippet.dhtmlx.com/d7w3jtqz?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
diff --git a/docs/how-to-start.md b/docs/how-to-start.md
index 46821d0..1baea11 100644
--- a/docs/how-to-start.md
+++ b/docs/how-to-start.md
@@ -84,8 +84,8 @@ Now you are ready to add booking to the page. First, let's create the DIV contai
 
 To start working with Booking, first you need to provide the initial data, and then you can add other configuration properties you want to be applied at the initialization. The example below creates Booking with two cards:
 
-- the [`data`](/api/config/booking-data) property allows adding data to each card, such as title, image, rating data, and booking slots
-- the [`cardShape`](/api/config/booking-cardshape) property helps to configure which cards' data fields to display
+- the [`data`](api/config/booking-data.md) property allows adding data to each card, such as title, image, rating data, and booking slots
+- the [`cardShape`](api/config/booking-cardshape.md) property helps to configure which cards' data fields to display
 
 ~~~jsx {}
 const data = [
@@ -156,4 +156,4 @@ new booking.Booking("#root", {
 That's all you need to create a simple Booking on a page. Now you are ready to embark on a journey with the Booking API:
 
 - [Guides](/category/guides) pages provide instructions about installation, loading data, styling, and other helpful tips to go smoothly with the Booking configuration
-- [API reference](/api/overview/booking-api-overview) gives description of the Booking functionality
+- [API reference](api/overview/booking-api-overview.md) gives description of the Booking functionality
diff --git a/docs/index.md b/docs/index.md
index 817e831..1b2febf 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -55,7 +55,7 @@ To filter cards by different text fields, date and time, a user should enter the
 - from: 12, to: 17 (Afternoon)
 - from: 17, to: 20 (Evening)
 
-It's possible to configure the filter settings via API: [Configuring the filter](/guides/configuration#configuring-the-filter)
+It's possible to configure the filter settings via API: [Configuring the filter](guides/configuration.md#configure-the-filter)
 
 ## Making an appointment
 
@@ -72,4 +72,4 @@ You can also make an appointment via the single card view:
 
 ## What's next
 
-Now you can [start with creating a simple Booking widget on your page](/how-to-start).
+Now you can [start with creating a simple Booking widget on your page](how-to-start.md).
diff --git a/docs/news/whats_new.md b/docs/news/whats_new.md
index d87df3e..4c1f44e 100644
--- a/docs/news/whats_new.md
+++ b/docs/news/whats_new.md
@@ -12,9 +12,9 @@ Released on March 12, 2025
 
 ### New functionality
 
-- Lazy rendering of cards via the [`renderType`](/api/config/booking-rendertype) property
-- Ability to embed templates via the [`cardTemplate`](/api/config/booking-cardtemplate) and [`infoTemplate`](/api/config/booking-infotemplate) properties
-- [Integration with frameworks](/category/backend-and-frameworks-integration/) and [DHTMLX Event Calendar](/guides/integration-with-eventcalendar)
+- Lazy rendering of cards via the [`renderType`](api/config/booking-rendertype.md) property
+- Ability to embed templates via the [`cardTemplate`](api/config/booking-cardtemplate.md) and [`infoTemplate`](api/config/booking-infotemplate.md) properties
+- [Integration with frameworks](/category/backend-and-frameworks-integration/) and [DHTMLX Event Calendar](guides/integration-with-eventcalendar.md)
 
 ## Version 1.0.1 
 
@@ -32,7 +32,7 @@ Released on November 6, 2024
 
 ### Initial functionality
 
-- [Various rules](/guides/configuration#defining-slot-rules) for defining item slots
+- [Various rules](guides/configuration.md#define-slot-rules) for defining item slots
 - Configurable cards to display data items
 - Configurable filtering by date, time and text
 - Configurable booking dialog
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 2772fd9..f100ff0 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -91,8 +91,16 @@ const readFile = (workingDir, filePath) => {
 const onEmptyLinkMatch = (data, { key, fullMatch, dir }) => {
 	const filePath = fullMatch.substring(fullMatch.indexOf('(') + 1, fullMatch.length - 1);
 	if (filePath.indexOf('.md') !== -1 || filePath.indexOf('.mdx') !== -1 || filePath.indexOf('.') === -1) {
-		const data = readFile(dir, filePath);
-		return data ? `[${/.*sidebar_label: (.+)/g.exec(data)[1]}]${fullMatch.match(/\(\D+\)/g)[0]}` : fullMatch;
+		// Links are written root-relative (e.g. api/config/booking-data.md), so resolve
+		// the target from the docs root rather than the page's own directory.
+		const fileContent = readFile(path.join(__dirname, 'docs'), filePath);
+		if (!fileContent) return fullMatch;
+		const labelMatch = /sidebar_label: (.+)/.exec(fileContent);
+		if (!labelMatch) return fullMatch;
+		// Emit a root-absolute href without the .md/.mdx extension, matching how
+		// normalizeMarkdownMdLinks rewrites ordinary links.
+		const href = '/' + filePath.replace(/^\.?\/+/, '').replace(/\.(md|mdx)(?=$|#)/, '');
+		return `[${labelMatch[1].trim()}](${href})`;
 	}
 	return fullMatch;
 };
@@ -206,6 +214,14 @@ const config = {
   	themeConfig:
     /** @type {import('@docusaurus/preset-classic').ThemeConfig} */
     ({
+		image: 'img/og-default-booking.png',
+		metadata: [
+			{ property: 'og:type', content: 'website' },
+			{ property: 'og:site_name', content: 'DHTMLX Booking Docs' },
+			{ property: 'og:locale', content: 'en_US' },
+			{ name: 'twitter:card', content: 'summary_large_image' },
+			{ name: 'twitter:site', content: '@dhtmlx' }
+		],
 		// hideableSidebar: true,
 		navbar: {
 			// hideOnScroll:true,
diff --git a/plugins/dhx-md-data-transformer-plugin.js b/plugins/dhx-md-data-transformer-plugin.js
index 789ab3b..31188d5 100644
--- a/plugins/dhx-md-data-transformer-plugin.js
+++ b/plugins/dhx-md-data-transformer-plugin.js
@@ -17,7 +17,7 @@ module.exports = (context, options) => {
         module: {
           rules: [
             {
-              include: [path.resolve(siteDir, 'docs')],
+              include: [path.resolve(siteDir, 'docs'), path.resolve(siteDir, 'i18n')],
               test: /(\.mdx?)$/,
               use: [
                 {
diff --git a/src/components/StructuredData/index.js b/src/components/StructuredData/index.js
new file mode 100644
index 0000000..ba665e0
--- /dev/null
+++ b/src/components/StructuredData/index.js
@@ -0,0 +1,102 @@
+import React from 'react';
+import Head from '@docusaurus/Head';
+import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
+import { useBaseUrlUtils } from '@docusaurus/useBaseUrl';
+
+const SITE_NAME = 'DHTMLX Booking Docs';
+const PRODUCT_NAME = 'DHTMLX Booking';
+const PRODUCT_URL = 'https://dhtmlx.com/docs/products/dhtmlxBooking/';
+
+function resolveType(pathname) {
+	const path = (pathname || '').replace(/\/+$/, '');
+	if (path === '' || path === '/booking') return 'SoftwareApplication';
+	if (/\/api(\/|$)/.test(path)) return 'APIReference';
+	return 'TechArticle';
+}
+
+function buildJsonLd({ type, title, description, url, image, siteUrl }) {
+	const base = {
+		'@context': 'https://schema.org',
+		headline: title,
+		name: title,
+		description,
+		url,
+		image,
+		inLanguage: 'en-US',
+		isPartOf: {
+			'@type': 'WebSite',
+			name: SITE_NAME,
+			url: siteUrl
+		}
+	};
+
+	if (type === 'SoftwareApplication') {
+		return {
+			'@context': 'https://schema.org',
+			'@type': 'SoftwareApplication',
+			name: PRODUCT_NAME,
+			description,
+			url,
+			image,
+			applicationCategory: 'DeveloperApplication',
+			operatingSystem: 'Cross-platform',
+			offers: {
+				'@type': 'Offer',
+				url: PRODUCT_URL,
+				priceCurrency: 'USD'
+			}
+		};
+	}
+
+	if (type === 'APIReference') {
+		return {
+			...base,
+			'@type': 'APIReference',
+			programmingModel: 'JavaScript',
+			about: {
+				'@type': 'SoftwareApplication',
+				name: PRODUCT_NAME,
+				applicationCategory: 'DeveloperApplication'
+			}
+		};
+	}
+
+	return {
+		...base,
+		'@type': 'TechArticle',
+		proficiencyLevel: 'Beginner',
+		dependencies: PRODUCT_NAME,
+		about: {
+			'@type': 'SoftwareApplication',
+			name: PRODUCT_NAME,
+			applicationCategory: 'DeveloperApplication'
+		}
+	};
+}
+
+export default function StructuredData({ title, description, pathname, image }) {
+	const { siteConfig } = useDocusaurusContext();
+	const { withBaseUrl } = useBaseUrlUtils();
+
+	const siteUrl = siteConfig.url + siteConfig.baseUrl.replace(/\/$/, '');
+	const url = siteConfig.url + withBaseUrl(pathname || '/');
+	const absoluteImage = image ? withBaseUrl(image, { absolute: true }) : undefined;
+
+	const type = resolveType(pathname);
+	const jsonLd = buildJsonLd({
+		type,
+		title,
+		description,
+		url,
+		image: absoluteImage,
+		siteUrl
+	});
+
+	return (
+		<Head>
+			<script type="application/ld+json">
+				{JSON.stringify(jsonLd)}
+			</script>
+		</Head>
+	);
+}
diff --git a/src/theme/DocItem/Metadata/index.js b/src/theme/DocItem/Metadata/index.js
new file mode 100644
index 0000000..9d771a6
--- /dev/null
+++ b/src/theme/DocItem/Metadata/index.js
@@ -0,0 +1,31 @@
+import React from 'react';
+import Head from '@docusaurus/Head';
+import { useLocation } from '@docusaurus/router';
+import DocItemMetadata from '@theme-original/DocItem/Metadata';
+import { useDoc } from '@docusaurus/plugin-content-docs/client';
+import StructuredData from '@site/src/components/StructuredData';
+
+export default function DocItemMetadataWrapper(props) {
+	const { metadata, frontMatter, assets } = useDoc();
+	const { pathname } = useLocation();
+
+	const title = metadata.title;
+	const description = metadata.description;
+	const image = assets.image ?? frontMatter.image;
+
+	return (
+		<>
+			<DocItemMetadata {...props} />
+			<Head>
+				{title && <meta name="twitter:title" content={title} />}
+				{description && <meta name="twitter:description" content={description} />}
+			</Head>
+			<StructuredData
+				title={title}
+				description={description}
+				pathname={pathname}
+				image={image}
+			/>
+		</>
+	);
+}
diff --git a/static/img/og-default-booking.png b/static/img/og-default-booking.png
new file mode 100644
index 0000000..f1add10
Binary files /dev/null and b/static/img/og-default-booking.png differ