diff --git a/docs/guides/configuration.md b/docs/guides/configuration.md
index fc17a37..d434d99 100644
--- a/docs/guides/configuration.md
+++ b/docs/guides/configuration.md
@@ -6,32 +6,34 @@ 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).
+Add data to the [`data`](/api/config/booking-data) array. For full instructions, see [`Loading data`](/guides/loading-data).
 
-## Defining the structure of cards 
+## Define card structure
 
-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.
+Use the [`cardShape`](/api/config/booking-cardshape) or [`cardTemplate`](/api/config/booking-cardtemplate) property to configure what information appears on the left side of each card.
 
 :::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.
+`cardTemplate` fully customizes the appearance of a card with custom HTML. It gives full control over the card's layout, design, and content.
+`cardShape` only modifies the default template by hiding or showing fields.
+If both are applied, `cardTemplate` overrides `cardShape`.
 :::
 
-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
+### Hide or show card fields
 
-To hide any information block from cards' display, set the appropriate parameter value of the [`cardShape`](/api/config/booking-cardshape) property to **false**.
+Use [`cardShape`](/api/config/booking-cardshape) to control which fields appear on the left side of each card without changing the default layout.
 
-Example:
+The following fields appear on the left side of each card by default:
+- `preview` — card image
+- `review` — rating information including the number of stars (out of five) and the number of reviews
+- `category` — category name (e.g., a specialist's job)
+- `title` — card title (e.g., a specialist's name)
+- `subtitle` — card subtitle (e.g., experience details); hidden by default
+- `price` — service price
+- `details` — additional card details
+
+To hide a field, set the corresponding `cardShape` parameter to `false`. The following code snippet hides the `details` field from all cards:
 
 ~~~jsx {24}
 const data = [
@@ -71,9 +73,11 @@ new booking.Booking("#root", {
 Please, 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
+
+Use [`cardTemplate`](/api/config/booking-cardtemplate) to apply a custom HTML template to the left side of each card.
 
-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). 
+Create a function that takes a card object and returns HTML. Arrange card item properties into HTML blocks with custom styles. The example below defines `cardPreviewTemplate`, which renders a preview image, category, title, and price:
 
 ~~~html {}
 <style>
@@ -118,7 +122,7 @@ 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.
+Also import the `template` helper and assign your function to `cardTemplate`:
 
 ~~~jsx
 const { Booking, template } = booking;
@@ -134,14 +138,13 @@ const widget = new Booking("#root", {
 Please, 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. Available slots appear for the next five days starting from the current date or from the start date set 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.
+Add an object to the `slots` array of the [`data`](/api/config/booking-data) property for each card. The example below adds slots for Tuesdays and Fridays from 12:00 to 18:00, with 30-minute duration and 10-minute gaps:
 
 ~~~jsx {15-22}
 const data = [
@@ -176,39 +179,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) property supports the following settings:
 
-- 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 (gap length in minutes)
+- days when slots are available
 
-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:  
+You can apply one common rule to all days of a card, or define different rules for specific days or exact 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
+- apply the same parameters to all days of a card — same slot duration, start time, and end time
+- apply different slot duration and gaps to specific days of the week or exact dates
 
-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
+To configure slot size and gap, use one of the following options (listed from highest to lowest priority):
+- `size` and `gap` in the `slots` array of [`data`](/api/config/booking-data) — set slot-specific values; override all other values
+- `slotSize` and `slotGap` in [`data`](/api/config/booking-data) — set card-level values; applied to all slots of a card if not overridden in `slots`
+- [`slotSize`](/api/config/booking-slotsize) and [`slotGap`](/api/config/booking-slotgap) — set widget-level values; applied to all cards if not overridden in `data`
 
 :::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.
+If you mix common slot parameters with day-specific ones, note the priority order:
+- 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 multiple slot objects cover the same day, ensure their time ranges (`from`–`to`) with different `size` and `gap` values do not overlap. Overlapping ranges cause all slot data for those days to be ignored.
 :::
 
-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.
+Use [`end`](/api/config/booking-end) and [`start`](/api/config/booking-start) to define the date range in which slots appear across all cards.
 
-#### Examples of defining slot rules
+#### Slot rule examples
 
-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. 
-
-Example:
+To add slots with identical parameters to all days of a card, add a single object to the `slots` array. The following code snippet applies the same slot parameters to all days of a card:
 
 ~~~jsx {}
 const data = [
@@ -226,11 +227,11 @@ const data = [
         },
         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
             }
         ]
     }
@@ -242,9 +243,7 @@ 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.  
-
-Example:
+To apply different parameters to specific days, add multiple objects to the `slots` array and specify `days` or `dates` for each. The following code snippet applies different slot parameters to specific days and exact dates:
 
 ~~~jsx {}
 const data = [
@@ -262,15 +261,15 @@ const data = [
         },
         slots: [
             {
-                //a common slot rule for all days except those specified for the days and dates below
+                // common rule for all days except those specified 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 days 2 and 5 (Tuesdays and Fridays) except
+                // the Friday from the slot object below
                 from: 12,
                 to: 17,
                 size: 50,
@@ -278,7 +277,7 @@ const data = [
                 days: [2, 5]
             },
             {
-                //this rule is applied to days 3 and 4 (Wednesdays and Thursdays) and exact date
+                // applies to days 3 and 4 (Wednesdays and Thursdays) and exact dates
                 from: 18,
                 to: 20,
                 size: 45,
@@ -298,11 +297,9 @@ 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).
 
-### Marking slots as used or available
+### Mark slots as used or available
 
-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.
-
-Example:
+Use the `usedSlots` parameter in the [`data`](/api/config/booking-data) property to mark slots as booked and hide them from users. The following code snippet marks a specific slot as used:
 
 ~~~jsx {}
 const data = [
@@ -320,15 +317,16 @@ const data = [
         },
         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,
@@ -338,9 +336,7 @@ new booking.Booking("#root", {
 
 To mark available slots, use the `availableSlots` parameter of the [`data`](/api/config/booking-data) property.
 
-If available slots are specified here, all slots from the `slots` array are ignored (i.e., become unavailable).
-
-Example:
+If `availableSlots` is specified, the `slots` array is ignored and those slots become unavailable. The following code snippet marks specific timestamps as the only available slots for a card:
 
 ~~~jsx {}
 const data = [
@@ -358,14 +354,14 @@ const data = [
         },
         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,11 +371,15 @@ new booking.Booking("#root", {
 });
 ~~~
 
-## Configuring the Booking dialog
+## Configure the Booking dialog
+
+The Booking dialog has two configurable areas: the form fields and the information block on the left side.
+
+### Configure form fields
 
-To configure the fields that should be displayed in the Booking dialog, use the [`formShape`](/api/config/booking-formshape) property.
+Use the [`formShape`](/api/config/booking-formshape) property to configure the fields in the Booking dialog.
 
-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*. 
+Add a new object to the array to include a new field. Set `required` to `true` to make a field mandatory. The following code snippet defines three fields, with the second one required:
 
 ~~~jsx {}
 const formShape = [
@@ -411,7 +411,9 @@ new booking.Booking("#root", {
 Please, 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*.
+### Configure the info block
+
+Use the [`infoShape`](/api/config/booking-infoshape) property to manage information on the left side of the Booking dialog. Set individual fields to `false` to hide them.
 
 ~~~jsx {1-7,11}
 const infoShape = {
@@ -433,9 +435,9 @@ new booking.Booking("#root", {
 Please, 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.
+Use the [`infoTemplate`](/api/config/booking-infotemplate) property to fully customize the appearance and content of the information block — `infoShape` only shows or hides fields from the default template. If both properties are applied, `infoTemplate` overrides `infoShape`.
 
-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.
+Define a function that generates custom HTML for the information block. The function receives `item` (card object) and `slot` (slot timestamp) as parameters. Arrange card item properties into HTML blocks with custom styles:
 
 ~~~html
 <style>
@@ -485,7 +487,7 @@ 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:
+Also import the `template` helper and pass your function to `infoTemplate`:
 
 ~~~jsx
 const { Booking, template } = booking;
@@ -502,9 +504,9 @@ Please, see an example in the [snippet tool](https://snippet.dhtmlx.com/byb94ipu
 :::
 
 
-## Configuring the filter
+## Configure 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) property to configure filter settings. The default configuration is:
 
 ~~~jsx {}
 const defaultTimeRanges = [
@@ -525,11 +527,9 @@ const defaultFilterShape = {
 };
 ~~~
 
-### Hiding 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**.
+### Hide filter input fields
 
-Example:
+All input fields (text, time, and date) appear by default. Use the [`filterShape`](/api/config/booking-filtershape) property and set the corresponding parameters to `false` to hide them. The following code snippet hides the date field from the filter:
 
 ~~~jsx {}
 const filterShape = {
@@ -543,11 +543,9 @@ new booking.Booking("#root", {
 });
 ~~~
 
-### Configuring 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. 
+### Configure filter fields
 
-Example:
+Set `suggest` to `true` to enable autocomplete — values from [`data`](/api/config/booking-data) that match user input appear in the **text** field. Use the `label` parameter to add labels to these fields. The following code snippet enables autocomplete for all text filter fields:
 
 ~~~jsx {}
 const filterShape = {
@@ -565,14 +563,12 @@ new booking.Booking("#root", {
 });
 ~~~
 
-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:
+To define time filtering options, configure the `time` parameter with start and end slot time values:
 
-- `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")
+- `from` — start time for a slot; number from 0 to 24 (e.g., `9` means 9:00, `8.5` means 8:30) or string in `"h:m"` format (e.g., `"8:30"`)
+- `to` — end time for a slot; number from 0 to 24 or string in `"h:m"` format
 
-And you can also add a placeholder to each time range.
-
-Example:
+You can also add a label to each time range. The following code snippet defines custom time ranges for the filter:
 
 ~~~jsx {}
 const filterShape = {
@@ -591,11 +587,9 @@ new booking.Booking("#root", {
 });
 ~~~
 
-### Enabling the autoApply mode for the filter
-
-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**.
+### Enable autoApply mode
 
-Example:
+Set the `autoApply` parameter of [`filterShape`](/api/config/booking-filtershape) to `true` to hide the **Search** button and apply filter criteria immediately. The following code snippet enables autoApply mode:
 
 ~~~jsx {}
 const filterShape = {
@@ -611,6 +605,20 @@ new booking.Booking("#root", {
 
 ### Example
 
-The snippet below demonstrates how to configure the filter:
+The snippet below configures the filter with all available options:
 
 <iframe src="https://snippet.dhtmlx.com/b5uj78bs?mode=result" frameborder="0" class="snippet_iframe" width="100%" height="600"></iframe>
+
+## Configure card rendering
+
+Use the [`renderType`](/api/config/booking-rendertype) property to control how cards are rendered. Set it to `"lazy"` to render only visible cards and improve performance with large data sets.
+
+The following code snippet enables lazy rendering:
+
+~~~jsx {}
+new booking.Booking("#root", {
+    data,
+    renderType: "lazy",
+    // other parameters
+});
+~~~
diff --git a/docs/guides/initialization.md b/docs/guides/initialization.md
index 8aef4a1..514b65d 100644
--- a/docs/guides/initialization.md
+++ b/docs/guides/initialization.md
@@ -6,42 +6,42 @@ 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:
+Follow these steps to add Booking to your page:
 
-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 on a page](#include-source-files).
+2. [Create a container for Booking](#create-a-container).
+3. [Initialize Booking with a 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.
 
-To create Booking, you need to include 2 source files on your page:
+Include two source files on your page:
 
-- *booking.js*
-- *booking.css*
+- `booking.js`
+- `booking.css`
 
-Make sure that you set correct relative paths to the source files:
+Set the correct relative paths to the source files:
 
 ~~~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 a container for Booking and give it an ID, for example *"root"*:
+Add a container for Booking and give it an ID, for example `"root"`:
 
 ~~~jsx title="index.html"
 <div id="root"></div>
 ~~~
 
-## Initializing Booking
+## Initialize Booking
 
-Initialize Booking using the **booking.Booking** constructor. It takes two parameters:
+Initialize Booking with the `booking.Booking` constructor. It takes two parameters:
 
-- an HTML container (the ID of the HTML container)
-- an object with configuration properties. [See the full list here](#configuration-properties)
+- an HTML container ID
+- an object with configuration properties — see [Configuration properties](#configuration-properties)
 
 ~~~jsx title="index.html"
 // create Booking
@@ -53,11 +53,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).
+See the [full list of configuration properties](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 sample data and configuration:
 
 <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..94b79ed 100644
--- a/docs/guides/integration-with-angular.md
+++ b/docs/guides/integration-with-angular.md
@@ -7,63 +7,63 @@ description: You can learn about the integration with Angular in the documentati
 # Integration with Angular
 
 :::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).
+Familiarize yourself with the basic concepts of **Angular** before reading this guide. To refresh your knowledge, 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).
+DHTMLX Booking is compatible with **Angular**. For code examples, see the [**Example on GitHub**](https://github.com/DHTMLX/angular-booking-demo).
 
-## Creating a project
+## Create a project
 
 :::info
-Before you start to create a new project, install [**Angular CLI**](https://v17.angular.io/cli) and [**Node.js**](https://nodejs.org/en/).
+Before creating a new project, install [**Angular CLI**](https://v17.angular.io/cli) and [**Node.js**](https://nodejs.org/en/).
 :::
 
-Create a new **my-angular-booking-app** project using Angular CLI. Run the following command for this purpose:
+Create a new **my-angular-booking-app** project using Angular CLI:
 
 ~~~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 creating the Angular app.
 :::
 
-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.
 
-### Installation of dependencies
+### Install dependencies
 
-Go to the new created app directory:
+Go to the app directory:
 
 ~~~json
 cd my-angular-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use the [**yarn**](https://yarnpkg.com/) package manager:
+Install dependencies and start the dev server using the [**yarn**](https://yarnpkg.com/) package manager:
 
 ~~~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`.
 
-## Creating Booking
+## Create Booking
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+Get the DHTMLX Booking source code. Stop the app and install the Booking package.
 
-### Step 1. Package installation
+### Step 1. Install the package
 
 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
 
-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.
+### Step 2. Create the component
+
+Create an Angular component to add Booking to the application. Create the `booking` folder in the `src/app/` directory, add a new file into it, and name it `booking.component.ts`.
 
 #### Import source files
 
-Open the file and import Booking source files. Note that:
+Open the file and import Booking source files:
 
-- if you use PRO version and install the Booking package from a local folder, the imported path looks like this:
+- if you use PRO version and install the Booking package from a local folder, use the following import path:
 
 ~~~jsx
 import { Booking } from 'dhx-booking-package';
@@ -76,12 +76,12 @@ 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:
+Create the container and initialize Booking with the constructor. The following code snippet sets up the component:
 
 ~~~jsx {1,8,12-13,18-19} title="booking.component.ts"
 import { Booking } from '@dhx/trial-booking';
@@ -95,7 +95,7 @@ import { Component, ElementRef, OnInit, ViewChild, OnDestroy, ViewEncapsulation
 })
 
 export class BookingComponent implements OnInit, OnDestroy {
-    // initialize container for Booking
+    // Booking container
     @ViewChild('container', { static: true }) booking_container!: ElementRef;
 
     private _booking!: Booking;
@@ -111,9 +111,9 @@ export class BookingComponent implements OnInit, OnDestroy {
 }
 ~~~
 
-#### Adding styles
+#### Add styles
 
-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 the `booking.component.css` file in the `src/app/booking/` directory and add the following styles:
 
 ~~~css title="booking.component.css"
 /* import Booking styles */
@@ -133,15 +133,15 @@ body {
 }
 ~~~
 
-#### Loading data
+#### Load data
 
-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 and add sample data:
 
 ~~~jsx title="data.ts"
 export function getData() : any {
     function getDate(addDays : any, hoursValue = 0, minutesValue = 0) {
         const date = new Date();
-        const secondsValue = 0; // round to minutes
+        const secondsValue = 0; // rounded to minutes
         const msValue = 0;
     
         date.setDate(date.getDate() + addDays);
@@ -218,7 +218,7 @@ 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 data file, and pass data to the Booking configuration in `ngOnInit()`:
 
 ~~~jsx {2,18,20} title="booking.component.ts"
 import { Booking } from '@dhx/trial-booking';
@@ -250,13 +250,13 @@ 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 is ready to use. When added to the page, it initializes with data. Provide additional configuration settings as needed. See the [Booking API docs](/api/overview/booking-properties-overview/) for the full list of available properties.
 
-#### 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/).
+Booking fires an event when a user performs an action. Use these events to detect actions and run custom code. See the [full list of events](/api/overview/booking-events-overview/).
 
-Open the ***booking.component.ts*** file and complete the `ngOnInit()` method as in:
+Open `booking.component.ts` and update the `ngOnInit()` method to listen for events:
 
 ~~~jsx {7-10} title="booking.component.ts"
 // ...
@@ -265,7 +265,7 @@ ngOnInit() {
         date: new Date(2024, 5, 10),
     });
 
-    // output the id of the selected slot
+    // log the id of the selected slot
     this._booking.api.on("select-slot", (obj) => {
         console.log(obj.id);
     });
@@ -276,9 +276,9 @@ ngOnDestroy(): void {
 }
 ~~~
 
-### Step 3. Adding Booking into the app
+### Step 3. Add Booking to the app
 
-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:
+To add `BookingComponent` to the app, open `src/app/app.component.ts` and replace the default code with the following:
 
 ~~~jsx {5} title="app.component.ts"
 import { Component } from "@angular/core";
@@ -292,7 +292,7 @@ export class AppComponent {
 }
 ~~~
 
-Then create the ***app.module.ts*** file in the ***src/app/*** directory and specify the *BookingComponent* as shown below:
+Create the `app.module.ts` file in the `src/app/` directory and specify `BookingComponent`:
 
 ~~~jsx {4-5,8} title="app.module.ts"
 import { NgModule } from "@angular/core";
@@ -309,7 +309,7 @@ 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 replace the existing code with the following:
 
 ~~~jsx title="main.ts"
 import { platformBrowserDynamic } from "@angular/platform-browser-dynamic";
@@ -319,8 +319,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.
 
 ![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 meet your project requirements. The complete example 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..380642b 100644
--- a/docs/guides/integration-with-eventcalendar.md
+++ b/docs/guides/integration-with-eventcalendar.md
@@ -6,52 +6,48 @@ 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 describes how to integrate the DHTMLX Booking widget with [DHTMLX Event Calendar](https://docs.dhtmlx.com/eventcalendar/).
 
 ## Main concepts
 
-The integration primarily focuses on converting the Event Calendar data into Booking slots.
+The integration focuses on converting Event Calendar data into Booking slots.
 
 - **Event Calendar events vs. Booking slots:**
     - Event Calendar handles events (e.g., single or recurring).
     - Booking generates available time slots from those events.
 
-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).
+Generate booking slots from events. The [snippet below](#example) converts doctor schedule data on the server side.
 
 - **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
+    - Booking supports only weekly recurring events (defined as `INTERVAL=1;FREQ=WEEKLY` in Event Calendar).
+    - Event Calendar supports any recurring pattern. Hide other recurring options from the Event Calendar form to ensure compatibility.
 
 - **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).
+    - If you use UTC timestamps, convert them to the local timezone before sending to Booking, and back to UTC before saving. See [Work with UTC data](/guides/saving-reservations/#work-with-utc-data).
 
 - **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` and `usedSlots` — build the schedule and exclude booked slots (this guide focuses on this strategy)
+    - `availableSlots` — 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 the following 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-time events; used to generate time slots for Booking
+- `/units` — final Booking slots generated from the Event Calendar `events` data on the server side; see also [backend](https://github.com/DHTMLX/event-calendar-booking-go)
+- `/calendars` — doctors' calendars with names and IDs; used in both Event Calendar and Booking widgets
+- `/reservations` — auxiliary collection that visualizes `usedSlots` in the timeline view; populated 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).
+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](#convert-events-to-booking-slots).
 
 <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 examples below use JSON data converted on the server side. All examples cover the 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).
 
@@ -84,9 +80,9 @@ Booking slot:
 }
 ~~~
 
-**Rule 2. Recurring events.**
+**Rule 2. Handle recurring events.**
 
-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).
+Use a weekly pattern for recurring events. The start and end dates of each recurring event in Event Calendar must match the Booking [`start`](/api/config/booking-start) and [`end`](/api/config/booking-end) dates. If they do not match, create placeholder rules for the dates before and after the event (see Rule 7).
 
 Event Calendar event (weekly on weekdays): the recurrence rule (rrule) specifies that the event repeats weekly on Monday, Tuesday, Wednesday, Thursday, and Friday.
 
@@ -119,11 +115,11 @@ Booking slots: In Booking, the weekly schedule is represented as a single rule,
 }
 ~~~
 
-**Rule 3. Scheduling an event that spans multiple days.**
+**Rule 3. Handle events that span 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.
+If an event spans multiple days (e.g., 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.
+When a doctor's shift starts on Saturday evening and continues into Sunday morning, split the event into two separate rules: one for Saturday and one for Sunday.
 
 Event Calendar event:
 
@@ -161,14 +157,14 @@ Booking slots:
 }
 ~~~
 
-**Rule 4. Additional single events added to recurring events.**
+**Rule 4. Add single events 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. 
+A single event is added to a recurring schedule. Booking generates slots for both the recurring and single events. Add single event dates to the recurring event's `dates` array.
 
 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: a doctor is also available from 2:00 AM to 6:00 AM on March 18 and 19.
 
 ~~~json
 [
@@ -198,8 +194,8 @@ Event Calendar events:
 
 Booking slots:
 
-- 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)
+- Merging events: combine the recurring and single events into one Booking rule.
+- Add specific dates (March 18 and 19) to the recurring event's rule to give them priority. See [Define slot rules](/guides/configuration/#define-slot-rules).
 
 ~~~json
 {
@@ -228,9 +224,9 @@ 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.
+If a single instance of a recurring event is edited (e.g., the time changes for a specific date), create a new slot with the updated time in the `dates` array. The `dates` array takes priority over `days`.
 
 Event Calendar event:
 
@@ -252,7 +248,7 @@ Event Calendar event:
     "recurring": false,
     "recurringEventId": 1,
     "originalStartTime": "2025-03-14T09:00:00Z"
-  },
+  }
 ]
 ~~~
 
@@ -280,9 +276,9 @@ 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 a single occurrence is removed from a recurring event in Event Calendar, update the Booking rules to reflect the removal. Create a rule for the removed date with an empty time interval and the `dates` property. The `dates` property takes priority over `days`.
 
 Event Calendar events:
 
@@ -331,9 +327,9 @@ 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 (2025-03-13 in these examples), create rules with empty time intervals for all dates before the event's start date. This effectively removes those dates from the recurrence.
 
 Event Calendar event:
 
@@ -347,7 +343,6 @@ Event Calendar event:
   "STDATE": "2025-03-17T09:00:00Z",
   "DTEND": "2027-03-13T00:00:00Z"
 }
-
 ~~~
 
 Booking slots:
@@ -368,13 +363,3 @@ Booking slots:
     ]
 }
 ~~~
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/guides/integration-with-react.md b/docs/guides/integration-with-react.md
index 9276a6c..ce784af 100644
--- a/docs/guides/integration-with-react.md
+++ b/docs/guides/integration-with-react.md
@@ -7,32 +7,32 @@ description: You can learn about the integration with React in the documentation
 # Integration with React
 
 :::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).
+Familiarize yourself with the basic concepts of [**React**](https://react.dev) before reading this guide. To refresh your knowledge, 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).
+DHTMLX Booking is compatible with **React**. For code examples, see the [**Example on GitHub**](https://github.com/DHTMLX/react-booking-demo).
 
-## Creating a project
+## Create a project
 
 :::info
-Before you start to create a new project, install [**Vite**](https://vite.dev/) (optional) and [**Node.js**](https://nodejs.org/en/).
+Before creating a new project, install [**Node.js**](https://nodejs.org/en/) and optionally [**Vite**](https://vite.dev/).
 :::
 
-You can create a basic **React** project or use **React with Vite**. Let's name the project as **my-react-booking-app**:
+Create a basic **React** project or use **React with Vite**. Name the project **my-react-booking-app**:
 
 ~~~json
 npx create-react-app my-react-booking-app
 ~~~
 
-### Installation of dependencies
+### Install dependencies
 
-Go to the new created app directory:
+Go to the app directory:
 
 ~~~json
 cd my-react-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use a package manager:
+Install dependencies and start the dev server using one of the following package managers:
 
 - if you use [**yarn**](https://yarnpkg.com/), run the following commands:
 
@@ -48,32 +48,32 @@ 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`.
 
-## Creating Booking
+## Create Booking
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+Get the DHTMLX Booking source code. Stop the app and install the Booking package.
 
-### Step 1. Package installation
+### Step 1. Install the package
 
 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 component
 
-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***.
+Create a React component to add Booking to the application. Add a new file in the `src/` directory and name it `Booking.jsx`.
 
 #### Import source files
 
-Open the ***Booking.jsx*** file and import Booking source files. Note that:
+Open `Booking.jsx` and import Booking source files:
 
-- if you use PRO version and install the Booking package from a local folder, the import paths look like this:
+- if you use PRO version and install the Booking package from a local folder, use the following import paths:
 
 ~~~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***.
+Depending on the package, the source files may be minified. In that case, import `booking.min.css` instead.
 
 - if you use the trial version of Booking, specify the following paths:
 
@@ -83,12 +83,12 @@ 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 up the container and add Booking
 
-To display Booking on the page, you need to create the container for Booking, and initialize this component using the corresponding constructor:
+Create the container and initialize Booking with the constructor. The following code snippet sets up the component:
 
 ~~~jsx {2,6,9-10,17} title="Booking.jsx"
 import { useEffect, useRef } from "react";
@@ -96,7 +96,7 @@ import { Booking } from "@dhx/trial-booking";
 import "@dhx/trial-booking/dist/booking.css"; // include Booking styles
 
 export default function BookingComponent(props) {
-    let container = useRef(); // initialize container for Booking
+    let container = useRef(); // Booking container
 
     useEffect(() => {
         // initialize the Booking component
@@ -111,9 +111,9 @@ export default function BookingComponent(props) {
 }
 ~~~
 
-#### Adding styles
+#### Add styles
 
-To display Booking correctly, you need to specify important styles for Booking and its container in the main css file of the project:
+Add the following styles to the main CSS file of your project:
 
 ~~~css title="index.css"
 /* specify styles for initial page */
@@ -131,15 +131,15 @@ body,
 }
 ~~~
 
-#### 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:
+Create a `data.js` file in the `src/` directory and add sample data:
 
 ~~~jsx title="data.js"
 export function getData() {
     function getDate(addDays, hoursValue = 0, minutesValue = 0) {
         const date = new Date();
-        const secondsValue = 0; // round to minutes
+        const secondsValue = 0; // rounded to minutes
         const msValue = 0;
     
         date.setDate(date.getDate() + addDays);
@@ -216,7 +216,7 @@ 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 data, and pass it to the `<Booking/>` component as `props`:
 
 ~~~jsx {2,5-6} title="App.js"
 import Booking from "./Booking";
@@ -230,7 +230,7 @@ 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 apply the props to the Booking configuration:
 
 ~~~jsx {5,10} title="Booking.jsx"
 import { useEffect, useRef } from "react";
@@ -255,20 +255,20 @@ 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 is ready to use. When added to the page, it initializes with data. Provide additional configuration settings as needed. See the [Booking API docs](/api/overview/booking-properties-overview/) for the full list of available properties.
 
-#### 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/).
+Booking fires an event when a user performs an action. Use these events to detect actions and run custom code. See the [full list of events](/api/overview/booking-events-overview/).
 
-Open ***Booking.jsx*** and complete the `useEffect()` method in the following way:
+Open `Booking.jsx` and update the `useEffect()` method to listen for events:
 
 ~~~jsx {5-8} title="Booking.jsx"
 // ...
 useEffect(() => {
     const booking = new Booking(container.current, {});
 
-    // output the id of the selected slot
+    // log the id of the selected slot
     booking.api.on("select-slot", (obj) => {
         console.log(obj.id);
     });
@@ -280,8 +280,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.
 
 ![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 meet your project requirements. The complete example 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..809f862 100644
--- a/docs/guides/integration-with-scheduler.md
+++ b/docs/guides/integration-with-scheduler.md
@@ -6,49 +6,48 @@ 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 describes how to integrate the DHTMLX Booking widget with [DHTMLX Scheduler](https://docs.dhtmlx.com/scheduler/).
 
 ## Main concepts
 
-The integration primarily focuses on converting the Scheduler data into Booking slots.
+The integration focuses on converting Scheduler data into Booking slots.
 
 - **Scheduler events vs. Booking slots:**
     - Scheduler handles events (e.g., single or recurring).
     - Booking generates available time slots from those events.
 
-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).
+Generate booking slots from the schedule. The [snippet below](#example) converts doctor schedule data on the server side.
 
 - **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
+    - Booking supports only weekly recurring events (defined as `INTERVAL=1;FREQ=WEEKLY` in Scheduler).
+    - Scheduler supports any recurring pattern. Limit other patterns in the Scheduler config to ensure compatibility.
 
 - **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). 
+    - If you use UTC timestamps, convert them to the local timezone before sending to Booking, and back to UTC before saving. See [Work with UTC data](/guides/saving-reservations/#work-with-utc-data).
 
 - **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` and `usedSlots` — build the schedule and exclude booked slots (this guide focuses on this strategy)
+    - `availableSlots` — 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 the following 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-time events; used to generate time slots for Booking
+- `/units` — final Booking slots generated from `worktime` data on the server side; see also [backend](https://github.com/DHTMLX/scheduler-booking-go)
+- `/doctors/reservations` — auxiliary collection that visualizes `usedSlots` in the timeline view; populated from the Booking form
+- `/doctors` — list of all doctors with names and IDs; used in both 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). 
+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](#convert-scheduler-events-to-booking-slots).
 
 <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 examples below use JSON data converted on the server side. All examples cover the 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).
 
@@ -81,9 +80,9 @@ Booking slot:
 }
 ~~~
 
-**Rule 2. Recurring events.** 
+**Rule 2. Handle recurring events.**
 
-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).
+Use a weekly pattern for recurring events. The start and end dates of each recurring event in Scheduler must match the Booking [`start`](/api/config/booking-start) and [`end`](/api/config/booking-end) dates. If they do not match, create placeholder rules for the dates before and after the event (see Rule 7).
 
 Scheduler event (weekly on weekdays): the recurrence rule (rrule) specifies that the event repeats weekly on Monday, Tuesday, Wednesday, Thursday, and Friday.
 
@@ -114,11 +113,11 @@ Booking slots: In Booking, the weekly schedule is represented as a single rule,
 }
 ~~~
 
-**Rule 3. Scheduling an event that spans multiple days.**
+**Rule 3. Handle events that span 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.
+If an event spans multiple days (e.g., 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.
+When a doctor's shift starts on Saturday evening and continues into Sunday morning, split the event into two separate rules: one for Saturday and one for Sunday.
 
 Scheduler event:
 
@@ -154,14 +153,14 @@ Booking slots:
 }
 ~~~
 
-**Rule 4. Additional single events added to recurring events.**
+**Rule 4. Add single events 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. 
+A single event is added to a recurring schedule. Booking generates slots for both the recurring and single events. Add single event dates to the recurring event's `dates` array.
 
 Scheduler 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: a doctor is also available from 2:00 AM to 6:00 AM on March 18 and 19.
 
 ~~~json
 [
@@ -190,8 +189,8 @@ Scheduler events:
 
 Booking slots:
 
-- 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)
+- Merging events: combine the recurring and single events into one Booking rule.
+- Add specific dates (March 18 and 19) to the recurring event's rule to give them priority. See [Define slot rules](/guides/configuration/#define-slot-rules).
 
 ~~~json
 {
@@ -220,9 +219,9 @@ 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.
+If a single instance of a recurring event is edited (e.g., the time changes for a specific date), create a new slot with the updated time in the `dates` array. The `dates` array takes priority over `days`.
 
 Scheduler event:
 
@@ -269,9 +268,9 @@ 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 a single occurrence is removed from a recurring event in Scheduler, update the Booking rules to reflect the removal. Create a rule for the removed date with an empty time interval and the `dates` property. The `dates` property takes priority over `days`.
 
 Scheduler events:
 
@@ -319,9 +318,9 @@ 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 (2025-03-13 in these examples), create rules with empty time intervals for all dates before the event's start date. This effectively removes those dates from the recurrence.
 
 Scheduler event:
 
@@ -353,13 +352,3 @@ Booking slots:
     ]
 }
 ~~~
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/guides/integration-with-svelte.md b/docs/guides/integration-with-svelte.md
index c3564b0..9ed3949 100644
--- a/docs/guides/integration-with-svelte.md
+++ b/docs/guides/integration-with-svelte.md
@@ -7,15 +7,15 @@ description: You can learn about the integration with Svelte in the documentatio
 # Integration with Svelte
 
 :::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/).
+Familiarize yourself with the basic concepts of [**Svelte**](https://svelte.dev/) before reading this guide. To refresh your knowledge, 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).
+DHTMLX Booking is compatible with **Svelte**. For code examples, see the [**Example on GitHub**](https://github.com/DHTMLX/svelte-booking-demo).
 
-## Creating a project
+## Create a project
 
 :::info
-Before you start to create a new project, install [**Vite**](https://vite.dev/) (optional) and [**Node.js**](https://nodejs.org/en/).
+Before creating a new project, install [**Node.js**](https://nodejs.org/en/) and optionally [**Vite**](https://vite.dev/).
 :::
 
 To create a **Svelte** JS project, run the following command:
@@ -24,9 +24,9 @@ To create a **Svelte** JS project, run the following command:
 npm create vite@latest
 ~~~
 
-Let's name the project as **my-svelte-booking-app**.
+Name the project **my-svelte-booking-app**.
 
-### Installation of dependencies
+### Install dependencies
 
 Go to the app directory:
 
@@ -34,7 +34,7 @@ Go to the app directory:
 cd my-svelte-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use a package manager:
+Install dependencies and start the dev server using one of the following package managers:
 
 - if you use [**yarn**](https://yarnpkg.com/), run the following commands:
 
@@ -50,25 +50,25 @@ 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`.
 
-## Creating Booking
+## Create Booking
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+Get the DHTMLX Booking source code. Stop the app and install the Booking package.
 
-### Step 1. Package installation
+### Step 1. Install the package
 
 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 component
 
-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***.
+Create a Svelte component to add Booking to the application. Add a new file in the `src/` directory and name it `Booking.svelte`.
 
 #### Import source files
 
-Open the ***Booking.svelte*** file and import Booking source files. Note that:
+Open `Booking.svelte` and import Booking source files:
 
-- if you use PRO version and install the Booking package from a local folder, the import paths look like this:
+- if you use PRO version and install the Booking package from a local folder, use the following import paths:
 
 ~~~html title="Booking.svelte"
 <script>
@@ -77,7 +77,7 @@ 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***.
+Depending on the package, the source files may be minified. In that case, import `booking.min.css` instead.
 
 - if you use the trial version of Booking, specify the following paths:
 
@@ -89,12 +89,12 @@ 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 up the container and add Booking
 
-To display Booking on the page, you need to create the container for Booking, and initialize this component using the corresponding constructor:
+Create the container and initialize Booking with the constructor. The following code snippet sets up the component:
 
 ~~~html {3,6,10-11,19} title="Booking.svelte"
 <script>
@@ -102,7 +102,7 @@ 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; // Booking container
     let booking;
 
     onMount(() => {
@@ -118,9 +118,9 @@ To display Booking on the page, you need to create the container for Booking, an
 <div bind:this={container} class="widget"></div>
 ~~~
 
-#### Adding styles
+#### Add styles
 
-To display Booking correctly, you need to specify important styles for Booking and its container in the main css file of the project:
+Add the following styles to the main CSS file of your project:
 
 ~~~css title="main.css"
 /* specify styles for initial page */
@@ -138,15 +138,15 @@ body,
 }
 ~~~
 
-#### 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:
+Create a `data.js` file in the `src/` directory and add sample data:
 
 ~~~jsx title="data.js"
 export function getData() {
     function getDate(addDays, hoursValue = 0, minutesValue = 0) {
         const date = new Date();
-        const secondsValue = 0; // round to minutes
+        const secondsValue = 0; // rounded to minutes
         const msValue = 0;
     
         date.setDate(date.getDate() + addDays);
@@ -223,7 +223,7 @@ 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 data, and pass it to the `<Booking/>` component as `props`:
 
 ~~~html {3,5,8} title="App.svelte"
 <script>
@@ -236,7 +236,7 @@ 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 apply the props to the Booking configuration:
 
 ~~~html {6,13} title="Booking.svelte"
 <script>
@@ -263,13 +263,13 @@ 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 is ready to use. When added to the page, it initializes with data. Provide additional configuration settings as needed. See the [Booking API docs](/api/overview/booking-properties-overview/) for the full list of available properties.
 
-#### 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/).
+Booking fires an event when a user performs an action. Use these events to detect actions and run custom code. See the [full list of events](/api/overview/booking-events-overview/).
 
-Open ***Booking.svelte*** and complete the `onMount()` method in the following way:
+Open `Booking.svelte` and update the `onMount()` method to listen for events:
 
 ~~~html {8-11} title="Booking.svelte"
 <script>
@@ -279,7 +279,7 @@ let booking;
 onMount(() => {
     booking = new Booking(container, {})
 
-    // output the id of the selected slot
+    // log the id of the selected slot
     booking.api.on("select-slot", (obj) => {
         console.log(obj.id);
     });
@@ -293,8 +293,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.
 
 ![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 meet your project requirements. The complete example 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..5513b20 100644
--- a/docs/guides/integration-with-vue.md
+++ b/docs/guides/integration-with-vue.md
@@ -7,15 +7,15 @@ description: You can learn about the integration with Vue in the documentation o
 # Integration with Vue
 
 :::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).
+Familiarize yourself with the basic concepts of [**Vue**](https://vuejs.org/) before reading this guide. To refresh your knowledge, 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).
+DHTMLX Booking is compatible with **Vue**. For code examples with **Vue 3**, see the [**Example on GitHub**](https://github.com/DHTMLX/vue-booking-demo).
 
-## Creating a project
+## Create a project
 
 :::info
-Before you start to create a new project, install [**Node.js**](https://nodejs.org/en/).
+Before creating a new project, install [**Node.js**](https://nodejs.org/en/).
 :::
 
 To create a **Vue** project, run the following command:
@@ -26,9 +26,9 @@ 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).
 
-Let's name the project as **my-vue-booking-app**.
+Name the project **my-vue-booking-app**.
 
-### Installation of dependencies
+### Install dependencies
 
 Go to the app directory:
 
@@ -36,7 +36,7 @@ Go to the app directory:
 cd my-vue-booking-app
 ~~~
 
-Install dependencies and start the dev server. For this, use a package manager:
+Install dependencies and start the dev server using one of the following package managers:
 
 - if you use [**yarn**](https://yarnpkg.com/), run the following commands:
 
@@ -52,25 +52,25 @@ 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`.
 
-## Creating Booking
+## Create Booking
 
-Now you should get the DHTMLX Booking source code. First of all, stop the app and proceed with installing the Booking package.
+Get the DHTMLX Booking source code. Stop the app and install the Booking package.
 
-### Step 1. Package installation
+### Step 1. Install the package
 
 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 component
 
-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***.
+Create a Vue component to add Booking to the application. Add a new file in the `src/components/` directory and name it `Booking.vue`.
 
 #### Import source files
 
-Open the ***Booking.vue*** file and import Booking source files. Note that:
+Open `Booking.vue` and import Booking source files:
 
-- if you use PRO version and install the Booking package from a local folder, the import paths look like this:
+- if you use PRO version and install the Booking package from a local folder, use the following import paths:
 
 ~~~html title="Booking.vue"
 <script>
@@ -79,7 +79,7 @@ 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***.
+Depending on the package, the source files may be minified. In that case, import `booking.min.css` instead.
 
 - if you use the trial version of Booking, specify the following paths:
 
@@ -91,12 +91,12 @@ 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 up the container and add Booking
 
-To display Booking on the page, you need to create the container for Booking, and initialize this component using the corresponding constructor:
+Create the container and initialize Booking with the constructor. The following code snippet sets up the component:
 
 ~~~html {2,7-8,18} title="Booking.vue"
 <script>
@@ -120,9 +120,9 @@ export default {
 </template>
 ~~~
 
-#### Adding styles
+#### Add styles
 
-To display Booking correctly, you need to specify important styles for Booking and its container in the main css file of the project:
+Add the following styles to the main CSS file of your project:
 
 ~~~css title="main.css"
 /* specify styles for initial page */
@@ -140,15 +140,15 @@ body,
 }
 ~~~
 
-#### 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:
+Create a `data.js` file in the `src/` directory and add sample data:
 
 ~~~jsx title="data.js"
 export function getData() {
     function getDate(addDays, hoursValue = 0, minutesValue = 0) {
         const date = new Date();
-        const secondsValue = 0; // round to minutes
+        const secondsValue = 0; // rounded to minutes
         const msValue = 0;
     
         date.setDate(date.getDate() + addDays);
@@ -225,7 +225,7 @@ 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 data, and pass it to the `<Booking/>` component as `props`:
 
 ~~~html {3,7-10,15} title="App.vue"
 <script>
@@ -246,7 +246,7 @@ export default {
 </template>
 ~~~
 
-Go to the ***Booking.vue*** file and apply the passed **props** to the Booking configuration object:
+Open `Booking.vue` and apply the props to the Booking configuration:
 
 ~~~html {6,10} title="Booking.vue"
 <script>
@@ -274,13 +274,13 @@ 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 is ready to use. When added to the page, it initializes with data. Provide additional configuration settings as needed. See the [Booking API docs](/api/overview/booking-properties-overview/) for the full list of available properties.
 
-#### 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/).
+Booking fires an event when a user performs an action. Use these events to detect actions and run custom code. See the [full list of events](/api/overview/booking-events-overview/).
 
-Open ***Booking.vue*** and complete the `mounted()` method:
+Open `Booking.vue` and update the `mounted()` method to listen for events:
 
 ~~~html {8-11} title="Booking.vue"
 <script>
@@ -290,7 +290,7 @@ export default {
     mounted() {
         this.booking = new Booking(this.$refs.container, {});
 
-        // output the id of the selected slot
+        // log the id of the selected slot
         booking.api.on("select-slot", (obj) => {
             console.log(obj.id);
         });
@@ -302,8 +302,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.
 
 ![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 meet your project requirements. The complete example 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..0a632cf 100644
--- a/docs/guides/loading-data.md
+++ b/docs/guides/loading-data.md
@@ -4,13 +4,13 @@ title: Loading data
 description: You can learn how to load data into Booking in the documentation of the DHTMLX JavaScript Booking library. Browse developer guides and API reference, try out code examples and live demos, and download a free 30-day evaluation version of DHTMLX Booking.
 ---
 
-# Loading data
+# Load data
 
-The following information can be loaded into Booking:
+Booking loads data through the following property:
 
-- [`data`](/api/config/booking-data) - an array of objects containing cards data 
+- [`data`](/api/config/booking-data) — an array of objects containing card data
 
-You can prepare data in a separate file. Here is an example of an appropriate data set:
+Prepare data in a separate file. The example below shows a sample data file with three cards:
 
 ~~~jsx title="data.js"
 const data = [
@@ -91,11 +91,13 @@ 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 JSON data into Booking from a local file or a server-side script after initializing the component.
 
-To load local data from a separate file, first prepare the source file with data.
+## Load data from a local file
 
-Example:
+To load local data from a file, prepare the source file first.
+
+The following code snippet defines a `getData` function that returns card data and card shape configuration:
 
 ~~~jsx {}
 function getData() {
@@ -143,7 +145,7 @@ const cardShape = {
 };
 ~~~
 
-Second, add the path to the source data file:
+Add the path to the data file in your HTML:
 
 ~~~html title="index.html"
 <script type="text/javascript" src="./dist/booking.js"></script>  
@@ -152,20 +154,23 @@ Second, add the path to the source data file:
 <script src="./common/data.js"></script>
 ~~~
 
-Create Booking and load data:
+Initialize Booking and pass data from the file:
 
 ~~~jsx {}
 const { data } = getData();
 const booking = new booking.Booking("#root", { data });
 ~~~
 
-About loading data from the server, refer to [Working with server](/guides/saving-reservations)
+## Load data from a server
+
+To load data from the server, see [Saving slot reservations to the server](/guides/saving-reservations).
 
 ---
 
 **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)
+
+- [`confirmSlot`](/api/events/booking-confirmslot-event) — fires when a user confirms a booking slot
+- [`setConfig()`](/api/methods/booking-setconfig-method) — updates Booking configuration at runtime
+- [`setConfirmHandler()`](/api/methods/booking-setconfirmhandler-method) — sets a custom handler for booking confirmation
+- [`renderType`](/api/config/booking-rendertype) — controls how cards are rendered
+- [Saving slot reservations to the server](/guides/saving-reservations)
diff --git a/docs/guides/localization.md b/docs/guides/localization.md
index 81482b8..92eb989 100644
--- a/docs/guides/localization.md
+++ b/docs/guides/localization.md
@@ -6,15 +6,15 @@ 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 to display labels in any language. Provide translated strings for all labels and apply the locale to the component.
 
 ## Default locale
 
-The English locale is applied by default:
+Booking uses the English locale by default:
 
 ~~~jsx {}
 const en = {
-    //calendar
+    // calendar
     calendar: {
         monthFull: [
             "January",
@@ -64,21 +64,22 @@ const en = {
         weekStart: 7,
         clockFormat: 24
     },
-    //core
+    // core
     core: {
         ok:"OK",
         cancel:"Cancel",
         select: "Select",
         "No data": "No data"
     },
-    //formats
+    // formats
     formats: {
         dateFormat: "%d.%m.%Y",
         timeFormat: "%H:%i"
     },
     lang: "en-US",
+    // booking
     booking: {
-        //Filter bar
+        // Filter bar
         "What date would be best?": "What date would be best?",
         "What time would be best?": "What time would be best?",
         Search: "Search",
@@ -128,7 +129,7 @@ const en = {
 ~~~
 
 :::info
-Besides the ***en*** locale, Booking also includes the built-in ***de*** and ***cn*** locales.
+Besides `en`, Booking also includes the built-in `de` and `cn` locales.
 :::
 
 <details>
@@ -199,7 +200,7 @@ const de = {
     lang: "de-DE",
     // booking
     booking: {
-        //Filter bar
+        // Filter bar
         "What date would be best?":
             "Welches Datum würde Ihnen am besten passen?",
         "What time would be best?": "Welche Zeit würde Ihnen am besten passen?",
@@ -320,9 +321,9 @@ const cn = {
         dateFormat: "%Y-%m-%d",
     }, 
     lang: "zh-CN",
-    //booking
+    // booking
     booking: {
-        //Filter bar
+        // Filter bar
         "What date would be best?": "什么日期最好?",
         "What time would be best?": "什么时间最好?",
         Search: "搜索",
@@ -370,11 +371,11 @@ const cn = {
 ~~~
 </details>
 
-## Applying locales
+## Apply a locale
 
-You can get access to the built-in locale via the *booking* object. Booking provides three built-in locales: en, cn, de.
+### Use a built-in locale
 
-Example:
+Access the built-in locale through the `booking` object. Booking provides three built-in locales: `en`, `cn`, and `de`. The following code snippet applies the built-in German locale:
 
 ~~~jsx {4}
 const { data } = getData();
@@ -384,12 +385,14 @@ const booking = new booking.Booking("#root", {
 });
 ~~~
 
-You can also apply the [`setLocale()`](/api/methods/booking-setlocale-method) method.
+### Apply a custom locale
+
+To apply a custom locale:
 
-To apply a custom locale, you need to:
+- create a locale object with translated strings for all labels
+- pass it to the [`locale`](/api/config/booking-locale) property or apply it at runtime with [`setLocale()`](/api/methods/booking-setlocale-method)
 
-- 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
+The following code snippet applies a custom Korean locale using `setLocale()`:
 
 ~~~jsx {}
 // create Booking
@@ -397,13 +400,13 @@ const booking = new booking.Booking("#root", {
   data,
 });
 
-const ko = {...} // object with locale
+const ko = {...} // custom locale object
 booking.setLocale(ko);
 ~~~
 
-## Changing the time format
+## Change the time format
 
-You can change the time format via the `timeFormat` parameter of the `formats` object of [locale](/api/config/booking-locale). 
+Change the time format with the `timeFormat` parameter of the `formats` object in the [`locale`](/api/config/booking-locale) property. The following code snippet switches between 12-hour and 24-hour formats:
 
 ~~~jsx {}
 let clockFormat = 12;
@@ -431,9 +434,9 @@ function changeFormat() {
 You can also see an example in the [snippet tool](https://snippet.dhtmlx.com/rxjnw54x)
 :::
 
-## Date and time format specification 
+## Date and time formats
 
-Booking uses the following characters for setting the date and time format:
+Booking uses the following characters to define date and time formats:
 
 | Character | Definition                                        |Example                  |
 | :-------- | :------------------------------------------------ |:------------------------|
@@ -460,14 +463,15 @@ Booking uses the following characters for setting the date and time format:
 | %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 display the date June 20, 2024 with the exact time as `2024-06-20 16:47:08.128`, use `"%Y-%m-%d-%H:%i:%s.%u"`.
 
 ## 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) — sets the locale for the Booking interface
+- [`setLocale()`](/api/methods/booking-setlocale-method) — changes the locale at runtime
diff --git a/docs/guides/saving-reservations.md b/docs/guides/saving-reservations.md
index 5ab7f1b..3da40ff 100644
--- a/docs/guides/saving-reservations.md
+++ b/docs/guides/saving-reservations.md
@@ -4,11 +4,11 @@ title:  Working with server
 description: You can learn about working with server in the documentation of the DHTMLX JavaScript Booking library. Browse developer guides and API reference, try out code examples and live demos, and download a free 30-day evaluation version of DHTMLX Booking.
 ---
 
-# Working with server
+# Work with the server
 
-## Loading data 
+## Load data
 
-To get server data, you can send the request for data using the native **fetch** method (or any other way):
+Use the native `fetch` method to request data from the server:
 
 ~~~jsx {}
 const booking = new booking.Booking("#booking", {data: []});
@@ -19,27 +19,27 @@ fetch(server + "/data").then((res) => res.json()).then((data) => {
 });
 ~~~
 
-## Saving slots reservations to the server
+## Save slot reservations
 
-To handle slots reservation, you should apply the [`setConfirmHandler`](/api/methods/booking-setconfirmhandler-method) method. 
+Use the [`setConfirmHandler()`](/api/methods/booking-setconfirmhandler-method) method to handle slot reservations. The following code snippet fetches data, updates the widget configuration, and sends a POST request when a user confirms a slot:
 
 ~~~jsx {}
-// create a function to handle the logic of reservation
+// handle slot reservation logic
 const handleSlotReservation = (event) => {
     const { confirm, slot, data } = event;
 
-    // create the info object 
+    // build the info object
     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
+    // send reservation data to the server
     fetch("/server/url", {
         method: "POST",
         body: JSON.stringify(info),
-    // handle the response
+    // handle the server response
     }).then((response) => {
         if (response.ok) confirm.done();
         else confirm.error();
@@ -52,23 +52,27 @@ const booking = new booking.Booking("#root", {
     // configuration parameters
 });
 
-// fetch available data from the server and convert it to JSON
+// fetch data 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
+        // update Booking with fetched data
         booking.setConfig({ data: items });
-        // assign the handleSlotReservation function to be called when a user confirms booking, 
-        // link user actions to the reservation logic
+        // set the reservation handler
         booking.setConfirmHandler(handleSlotReservation);
     });
 ~~~
 
-## Working with UTC data
+## Work with UTC data
 
-The widget applies a local timezone but if you have UTC data it's necessary to convert data to a local timezone.
+The widget uses the local timezone. If your data is in UTC, convert it to the local timezone before loading.
 
-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.
+The example below uses two helper functions to handle this conversion:
+
+- `g2l` converts a UTC timestamp to the local timezone. Use it during data loading to convert `usedSlots` and `slots` timestamps from UTC to local time.
+- `l2g` converts a local timestamp back to UTC. Use it when saving a reservation to convert the local time from `slot.time[0]` to UTC before sending it to the server.
+
+The following code snippet converts UTC timestamps to local time during data loading, and back to UTC when sending a reservation:
 
 ~~~jsx
 const serverURL = "https://some-backend-url";
@@ -150,12 +154,14 @@ fetch( serverURL + "/units")
     });
 ~~~
 
-
 ## Example
 
+The snippet below loads data from a server and handles slot reservations:
+
 <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
+
+- [`confirmSlot`](/api/events/booking-confirmslot-event) — fires when a user confirms a booking slot
+- [`setConfig()`](/api/methods/booking-setconfig-method) — updates Booking configuration at runtime
+- [`setConfirmHandler()`](/api/methods/booking-setconfirmhandler-method) — sets a custom handler for booking confirmation
diff --git a/docs/guides/styling.md b/docs/guides/styling.md
index 2bd37d8..228bc33 100644
--- a/docs/guides/styling.md
+++ b/docs/guides/styling.md
@@ -8,6 +8,8 @@ description: You can learn about Styling in the documentation of the DHTMLX Java
 
 ## Default style
 
+The following CSS variables define the default appearance of Booking:
+
 ~~~css
 .wx-material-theme {
     --wx-theme-name: material;
@@ -21,29 +23,29 @@ description: You can learn about Styling in the documentation of the DHTMLX Java
 ~~~
 
 :::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.
+Future versions of Booking may rename CSS variables. Check variable names after each update and adjust your code accordingly.
 :::
 
 ## Built-in theme
 
-The widget provides one built-in theme which is the **Material** theme. 
+Booking provides one built-in theme: the **Material** theme.
 
-You can apply the theme via adding the corresponding *CSS* classes to the widget container:
+Add the `wx-material-theme` CSS class to the widget container:
 
 ~~~html {}
 <!-- Booking container -->
 <div id="root" class="wx-material-theme"></div>
 ~~~
 
-or just include the theme on the page from the skins folder:
+You can also include the theme directly from the skins folder:
 
 ~~~html {}
 <link type="stylesheet" href="path/to/booking/skins/material.css"/>
 ~~~
 
-## Customize built-in theme
+## Customize the built-in theme
 
-The example below demonstrates how to customize the **Material** theme that is applied to Booking:
+The example below customizes the **Material** theme with a dark color scheme:
 
 ~~~html
 <style>
@@ -66,7 +68,7 @@ The example below demonstrates how to customize the **Material** theme that is a
 
 ## Custom styles
 
-To customize the appearance of Booking to your project needs, you need to apply the corresponding CSS variables. 
+Apply CSS variables to customize Booking's appearance for your project. The following code snippet overrides the default color scheme:
 
 ~~~html
 <div id="root" class="demo"></div>
@@ -83,7 +85,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 for cards and selected date items:
 
 ~~~html
 <style>
@@ -102,6 +104,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 applies a custom style to Booking:
 
 <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..34b8975 100644
--- a/docs/how-to-start.md
+++ b/docs/how-to-start.md
@@ -6,36 +6,34 @@ description: You can explore how to start working with DHTMLX Booking in the doc
 
 # How to start
 
-This clear and comprehensive tutorial will guide your through the steps you need to take in order to get a full-functional Booking application on a page.
+Follow these steps to add a functional Booking application to your page.
 
 ![main](assets/main.png)
 
-## Step 1. Downloading and installing packages
+## Step 1. Download and install packages
 
-[Download the package](https://dhtmlx.com/docs/products/dhtmlxBooking/) and unpack it into a folder of your project.
+[Download the package](https://dhtmlx.com/docs/products/dhtmlxBooking/) and unpack it into your project folder.
 
-You can import JavaScript Booking into your project using `yarn` or `npm` package manager.
+Import Booking using `yarn` or `npm`:
 
-#### Installing trial Booking via npm or yarn
+### Install trial Booking via npm or yarn
 
 :::info
 If you want to use the trial version of Booking, download the trial [booking package](https://dhtmlx.com/docs/products/dhtmlxBooking/) and follow the steps mentioned in the *README* file. Note that trial booking is available for 30 days only.
 :::
 
-#### Installing PRO Booking via npm or yarn
+### Install PRO Booking via npm or yarn
 
 :::info
 You can access the DHTMLX private **npm** directly in the [Client's Area](https://dhtmlx.com/clients/) by generating your login and password for **npm**. A detailed installation guide is also available there. Please note that access to the private **npm** is available only while your proprietary Booking license is active.
 :::
 
-## Step 2. Including source files
+## Step 2. Include source files
 
-Start from creating an HTML file and call it *index.html*. Then proceed to include Booking source files into the created file.
+Create an HTML file named `index.html` and include the Booking source files:
 
-There are two necessary files:
-
-- the JS file of booking
-- the CSS file of booking
+- `booking.js`
+- `booking.css`
 
 ~~~html {5-6} title="index.html"
 <!DOCTYPE html>
@@ -54,12 +52,12 @@ There are two necessary files:
 ~~~
 
 :::tip
-If you want to integrate JavaScript Booking into React, Angular or Vue projects, refer to the corresponding [**Examples on CodeSandbox**](https://codesandbox.io/u/DHTMLX) for more information.
+To integrate Booking into React, Angular, or Vue projects, see the [**Examples on CodeSandbox**](https://codesandbox.io/u/DHTMLX).
 :::
 
-## Step 3. Creating booking
+## Step 3. Create Booking
 
-Now you are ready to add booking to the page. First, let's create the DIV container for Booking. 
+Add a container element and initialize Booking with the constructor:
 
 ~~~html {} title="index.html"
 <!DOCTYPE html>
@@ -80,12 +78,12 @@ Now you are ready to add booking to the page. First, let's create the DIV contai
 </html>
 ~~~
 
-## Step 4. Configuring Booking
+## Step 4. Configure Booking
 
-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:
+Provide the initial data and any additional configuration properties. The following code snippet creates Booking with two cards using these properties:
 
-- 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
+- [`data`](/api/config/booking-data) — adds card data, including title, image, rating, and booking slots
+- [`cardShape`](/api/config/booking-cardshape) — configures which data fields to display on cards
 
 ~~~jsx {}
 const data = [
@@ -153,7 +151,7 @@ new booking.Booking("#root", {
 
 ## What's next
 
-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:
+Booking is ready. Explore the following resources to continue:
 
-- [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
+- [Guides](/category/guides) — instructions for installation, loading data, styling, and other configuration topics
+- [API reference](/api/overview/booking-api-overview) — full description of the Booking functionality
diff --git a/docs/index.md b/docs/index.md
index 817e831..34dd5dd 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -7,69 +7,67 @@ description: You can have an overview of DHTMLX JavaScript Booking library in th
 
 # DHTMLX Booking overview
 
-## Overview
-
-JavaScript Booking library is a ready-made component designed to be easily incorporated into your application. It provides end-users with functionality for scheduling appointments online and wide filtering options. The widget is made responsive and optimised for mobile devices.
+JavaScript Booking is a ready-made component for scheduling appointments online. It provides filtering options and is optimized for mobile devices.
 
 ## Booking structure
 
-The Booking UI includes the two main parts: the filter area and the list of cards with slots. Each card's view consists of the card's information block and slots available for booking.
+The Booking UI has two main areas: the filter bar and the list of cards with slots. Each card includes an information block and available booking slots.
 
 ![main](assets/main.png)
 
 ### Cards list
 
-All cards are displayed as a list. The left side of each card in the list shows the following information items:
+Cards appear as a list. The left side of each card shows the following fields:
 
-- 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 (for example, 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
+- `preview` — card image
+- `review` — rating information including the number of stars (out of five) and the number of reviews
+- `category` — category name (e.g., a specialist's job)
+- `title` — card title (e.g., a specialist's name)
+- `subtitle` — card subtitle (e.g., experience details)
+- `price` — service price
+- `details` — additional card details
 
 ### Slots
 
-The right side of each card has clickable slots available for booking. Slots are displayed for the current month starting from the current date.
+The right side of each card shows clickable slots available for booking, starting from the current date.
 
-### A single card view
+### Single card view
 
-To open the view of a single card, click inside the left area of a card. The single card dialog shows the card's title, calendar and available slots for the date selected in the calendar.
+Click the left area of a card to open the single card view. It shows the card title, a calendar, and available slots for the selected date.
 
 ![single-card](assets/single-card.png)
 
 ### Booking dialog
 
-The booking dialog allows booking a slot of the selected card. To open it, click the time slot button. 
+The Booking dialog opens when you click a time slot button. Use it to book a slot for the selected card.
 
 ![booking](assets/bookingd.png)
 
-For the instruction about booking, please, refer to [Making an appointment](#making-an-appointment)
+See [Make an appointment](#make-an-appointment) for step-by-step instructions.
 
-## Filtering data
+## Filter data
 
-To filter cards by different text fields, date and time, a user should enter the required values in the input fields and click the **Search** button. A user can filter  cards by category and title by default. The next default time ranges are available for filtering:
+Enter values in the filter fields and click **Search** to filter cards by text, date, and time. By default, cards are filterable by category and title. The following time ranges are available by default:
 
-- from: 8, to: 12 (Morning)
-- from: 12, to: 17 (Afternoon)
-- from: 17, to: 20 (Evening)
+- `from: 8, to: 12` — Morning
+- `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)
+Configure the filter settings with the API: [Configure the filter](/guides/configuration#configure-the-filter).
 
-## Making an appointment
+## Make an appointment
 
-To schedule an appointment, click the time slot button for the required card, and in the **Booking** dialog, fill in the fields, and then click **Make an appointment**.
+Click a time slot button for a card, fill in the fields in the **Booking** dialog, and click **Make an appointment**.
 
-You can also make an appointment via the single card view:
+You can also book through the single card view:
 
-1. Click inside the left area of a card.
-2. In the single card view that opens, select the required date and time.
+1. Click the left area of a card.
+2. In the single card view, select the required date and time.
 3. Next to the selected time, click **Confirm**.
-4. In the **Booking** dialog that appears, fill in the fields, and then click **Make an appointment**.
+4. In the **Booking** dialog, fill in the fields, and click **Make an appointment**.
 
 ![booking-2](assets/booking-2.png)
 
 ## What's next
 
-Now you can [start with creating a simple Booking widget on your page](/how-to-start).
+[Start creating a Booking widget on your page](/how-to-start).