[docs] some fixes for en/core/dev/example-app/ (#8648)

Author: blinkov

ydb/docs/en/core/dev/example-app/_includes/auxilary/addition.md

@@ -1,6 +1,6 @@
 {% note info %}
 
-The article is being updated.
+The article is currently being updated.
 
 {% endnote %}
 

ydb/docs/en/core/dev/example-app/_includes/auxilary/pragmatablepathprefix.md

@@ -1,9 +1,8 @@
-`PRAGMA TablePathPrefix` adds a specified prefix to the database table paths. It uses standard file system path concatenation: i.e., it supports parent folder referencing and requires no trailing slash. For example:
+`PRAGMA TablePathPrefix` adds a specified prefix to the table paths. It uses standard filesystem path concatenation, meaning it supports parent folder referencing and does not require a trailing slash. For example:
 
 ```sql
 PRAGMA TablePathPrefix = "/cluster/database";
 SELECT * FROM episodes;
 ```
 
-For more information about PRAGMA in YQL, see the [YQL documentation](../../../../yql/reference/index.md).
-
+For more information about `PRAGMA` in YQL, refer to the [YQL documentation](../../../../yql/reference/index.md).

ydb/docs/en/core/dev/example-app/_includes/index.md

@@ -1,6 +1,6 @@
 # Example applications working with {{ ydb-short-name }}
 
-This section describes the code of same-type test apps implemented using {{ ydb-short-name }} SDKs in different programming languages:
+This section outlines the implementation of example applications, all designed to perform similar functions, using the {{ ydb-short-name }} SDKs across various programming languages. Each app is developed to demonstrate how a respective SDK can be utilized in a specific language.
 
 {% if oss %}
 
@@ -14,7 +14,7 @@ This section describes the code of same-type test apps implemented using {{ ydb-
 
 {% node info %}
 
-Additional information on how these example applications work is available in [{{ ydb-short-name }} SDK reference documentation](../../../reference/ydb-sdk/index.md).
+Refer to [{{ ydb-short-name }} SDK reference documentation](../../../reference/ydb-sdk/index.md) for more details.
 
 {% endnote %}
 

ydb/docs/en/core/dev/example-app/_includes/steps/01_init.md

@@ -1,8 +1,7 @@
 ## Initializing a database connection {#init}
 
-To interact with {{ ydb-short-name }}, create an instance of the driver, client, and session:
-
-* The {{ ydb-short-name }} driver lets the app and {{ ydb-short-name }} interact at the transport layer. The driver must exist throughout the {{ ydb-short-name }} access lifecycle and be initialized before creating a client or session.
-* The {{ ydb-short-name }} client runs on top of the {{ ydb-short-name }} driver and enables the handling of entities and transactions.
-* The {{ ydb-short-name }} session contains information about executed transactions and prepared queries, and is part of the {{ ydb-short-name }} client context.
+To interact with {{ ydb-short-name }}, create instances of the driver, client, and session:
 
+* The {{ ydb-short-name }} driver facilitates interaction between the app and {{ ydb-short-name }} nodes at the transport layer. It must be initialized before creating a client or session and must persist throughout the {{ ydb-short-name }} access lifecycle.
+* The {{ ydb-short-name }} client operates on top of the {{ ydb-short-name }} driver and enables the handling of entities and transactions.
+* The {{ ydb-short-name }} session, which is part of the {{ ydb-short-name }} client context, contains information about executed transactions and prepared queries.

ydb/docs/en/core/dev/example-app/_includes/steps/02_create_table.md

@@ -1,10 +1,9 @@
 ## Creating tables {#create-table}
 
-Creating tables to be used in operations on a test app. This step results in the creation of DB tables of the series directory data model:
+Create tables to be used in operations on a test app. This step results in the creation of database tables for the series directory data model:
 
 - `Series`
 - `Seasons`
 - `Episodes`
 
-Once the tables are created, the method for getting information about data schema objects is called and the result of its execution is output.
-
+After the tables are created, a method for retrieving information about data schema objects is called, and the result of its execution is displayed.

ydb/docs/en/core/dev/example-app/_includes/steps/03_write_queries.md

@@ -1,4 +1,3 @@
 ## Adding data {#write-queries}
 
-Adding data to the created tables using an [`UPSERT`](../../../../yql/reference/syntax/upsert_into.md) statement of [YQL](../../../../yql/reference/index.md). A data update request is sent within a single request to the server with transaction auto-commit mode enabled.
-
+Add data to the created tables using the [`UPSERT`](../../../../yql/reference/syntax/upsert_into.md) statement in [YQL](../../../../yql/reference/index.md). A data update request is sent to the server as a single request with transaction auto-commit mode enabled.

ydb/docs/en/core/dev/example-app/_includes/steps/04_query_processing.md

@@ -1,4 +1,3 @@
-## Retrieving data with a Select {#query-processing}
-
-Retrieving data using a [`SELECT`](../../../../yql/reference/syntax/select/index.md) statement in [YQL](../../../../yql/reference/index.md). Handling the retrieved data selection in the app.
+## Retrieving data {#query-processing}
 
+Retrieve data using a [`SELECT`](../../../../yql/reference/syntax/select/index.md) statement in [YQL](../../../../yql/reference/index.md). Handle the retrieved data selection in the app.

ydb/docs/en/core/dev/example-app/_includes/steps/06_param_queries.md

@@ -1,4 +1,3 @@
 ## Parameterized queries {#param-queries}
 
-Querying data using parameters. This query execution option is preferable as it allows the server to reuse the query execution plan for subsequent calls and also protects from such vulnerabilities as [SQL Injection](https://en.wikipedia.org/wiki/SQL_injection).
-
+Query data using parameters. This query execution method is preferable because it allows the server to reuse the query execution plan for subsequent calls and protects against vulnerabilities such as [SQL injection](https://en.wikipedia.org/wiki/SQL_injection).

ydb/docs/en/core/dev/example-app/_includes/steps/07_param_prep_queries.md

@@ -1,6 +1,5 @@
 ## Parameterized prepared queries {#param-prepared-queries}
 
-Parameterized prepared queries are saved as templates where specially formatted names are replaced by relevant parameter values each time you execute the query. Use parameterized queries to improve performance by reducing how often queries that only differ in parameter values are compiled and recompiled. The prepared query is stored in the session context.
-
-Code snippet for parameterized prepared queries:
+Parameterized prepared queries are saved as templates, where specially formatted placeholders are replaced with relevant parameter values each time the query is executed. Use parameterized queries to improve performance by reducing the need for frequent compilation and recompilation of queries that differ only in parameter values. The prepared query is stored in the session context.
 
+Code snippet for parameterized prepared queries:

ydb/docs/en/core/dev/example-app/_includes/steps/08_scan_query.md

@@ -1,4 +1,3 @@
 ## Scan queries {#scan-query}
 
-Making a [scan query](../../../../concepts/scan_query.md) that results in a data stream. Streaming lets you read an unlimited number of rows and amount of data.
-
+Execute a [scan query](../../../../concepts/scan_query.md) to produce a data stream. Streaming allows to read an unlimited number of rows and an unlimited amount of data.